What It Does
Convert every hunt finding into a durable detection with an owner and a test.
Observable indicator. No hunt finding is left as tribal knowledge.
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 maneuverM7 CounterattackSeize the initiative and evict before the adversary reaches the objective.
- Terrain layerTX Cross-CuttingThe enablers of movement. Key terrain: The telemetry pipeline, the orchestration layer, the rules of engagement.
- Position in the form9 of 17M7 carries 17 cataloged techniques; this is the 9th 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.
- Phase IIIDominateHunt, contain, evict.
- Phase VEnable / RestoreRecover, harden, and update the doctrine and the intelligence requirements.
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.
- SM-6 Maneuver Effectiveness ValidationScheme of Maneuver — To replace assumed effectiveness with demonstrated effectiveness, so the coverage figure reflects what controls do rather than what was assumed of them.
- 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.
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-FCR File Content RulesDetect tactic
- D3-NTSA Network Traffic Signature AnalysisDetect 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 12 that share at least one control.
- 2 shared controlsM10.01 Indicator-to-Detection ConversionM10 Exploitation & Pursuit · TX Cross-Cutting
- CE-5
- SM-6
- 1 shared controlM4.12 Denied-Path Register EnforcementM4 Obstacle / Canalization · T3 Networks
- SM-6
- 1 shared controlM7.06 Build Pipeline Integrity HuntM7 Counterattack · T4 Applications and Workloads
- SM-6
- 1 shared controlM7.10 Purple-Team ValidationM7 Counterattack · TX Cross-Cutting
- SM-6
- 1 shared controlM8.12 Degradation RehearsalM8 Isolation / Retrograde · TX Cross-Cutting
- SM-6
- 1 shared controlM9.02 Targeted Emergency PatchingM9 Spoiling Attack · T4 Applications and Workloads
- CE-5