What It Does
Patch out of cycle when intelligence — not the calendar — says a specific weakness is being used now.
Observable indicator. Actively exploited weaknesses are closed ahead of the routine cycle.
Where It Sits
A technique is chosen from inside a form and emplaced on one layer. Both are the catalog’s own declarations; the position is counted in catalog order.
- Form of maneuverM9 Spoiling AttackDisrupt adversary staging before the attack is launched.
- Terrain layerT4 Applications and WorkloadsThe urban terrain. Key terrain: The public service portal, the case processing system, public APIs.
- Position in the form2 of 9M9 carries 9 cataloged techniques; this is the 2nd in catalog order.
Phases It Is Employed In
Employed in 2 of the campaign’s six phases. A phase named here means at least this technique is live in it — not that the form it belongs to is the main effort.
Controls That Assess It
The controls the catalog names against this technique. They are what an assessor would test to establish that it is emplaced and working — the indicator above is what shows it is working, which is a different question.
- CE-5 Remediation Backlog PrioritizationCycle Execution and Assurance — To make the backlog answer where the next hour of work goes, rather than enumerate everything wrong.
- CG-4 Findings DispositionCommand and Governance — To ensure every finding reaches a decision, so that the open set reflects work in progress rather than accumulated neglect.
In MITRE D3FEND
What this technique is called in MITRE’s countermeasure ontology. The join runs technique-to-technique: D3FEND catalogs countermeasures, and the thing with a countermeasure’s shape here is the technique, not the control.
- D3-AVE Asset Vulnerability EnumerationModel tactic
- D3-SU Software UpdateHarden tactic
- D3-FBA Firmware Behavior AnalysisDetect tactic
- D3-FEMC Firmware Embedded Monitoring CodeDetect tactic
- D3-FV Firmware VerificationDetect tactic
- D3-PFV Peripheral Firmware VerificationDetect tactic
- D3-SFV System Firmware VerificationDetect tactic
That a technique reaches a D3FEND countermeasure says the two describe the same defensive act. It does not say the countermeasure is deployed, configured, or working — that is an assessment finding about your estate, not a property of the framework.
Related Techniques
The catalog declares no relation for this entry, and no other entry names it — the inverse is derived here, so an incoming edge would show up even though this one never declared it. The techniques below share its assessment surface, which is the nearest adjacency the data supports.
Assessed Alongside
Not a declared relation: these are the techniques whose assessing controls overlap this one’s, ranked by how much of the two assessment surfaces coincide. Showing 6 of 10 that share at least one control.
- 2 shared controlsM9.07 Exploited-Vulnerability Catalog EnforcementM9 Spoiling Attack · T4 Applications and Workloads
- CE-5
- CG-4
- 1 shared controlM1.07 Partner and Advisory IntakeM1 Screen / Guard · TX Cross-Cutting
- CG-4
- 1 shared controlM10.01 Indicator-to-Detection ConversionM10 Exploitation & Pursuit · TX Cross-Cutting
- CE-5
- 1 shared controlM3.14 Entitlement RecertificationM3 Envelopment · T1 Identity
- CG-4
- 1 shared controlM7.09 Detection Engineering from HuntM7 Counterattack · TX Cross-Cutting
- CE-5
- 1 shared controlM7.15 Insider Risk InvestigationM7 Counterattack · T7 Workforce
- CG-4