What It Does
Reconstruct how long the adversary held the ground, so temporal advantage is computed rather than estimated.
Observable indicator. Dwell is measured from evidence for every engagement.
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 form12 of 17M7 carries 17 cataloged techniques; this is the 12th 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.
- TA-2 Adversary Dwell EstimationTempo and Temporal Advantage — To establish the denominator of temporal advantage with an explicit, challengeable basis, so the comparison the framework rests on can be argued with.
- CE-6 Cycle Record and TrendCycle Execution and Assurance — To answer whether the program is improving — a question no point-in-time assessment can address.
- EN-2 Engagement ReconstructionEngagement and Pursuit — To establish what actually happened, since every consolidation activity depends on a reconstruction and none of them can be performed without one.
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-RTSD Remote Terminal Session DetectionDetect tactic
- D3-FAPA File Access Pattern AnalysisDetect tactic
- D3-PSA Process Spawn AnalysisDetect tactic
- D3-PLA Process Lineage AnalysisDetect tactic
- D3-SCA System Call AnalysisDetect tactic
- D3-FCA File Creation 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 6 that share at least one control.
- 2 shared controlsM10.04 Intelligence Requirement RevisionM10 Exploitation & Pursuit · TX Cross-Cutting
- CE-6
- EN-2
- 1 shared controlM7.13 Hunt Coverage AccountingM7 Counterattack · TX Cross-Cutting
- CE-6
- 1 shared controlM10.02 Avenue Closure VerificationM10 Exploitation & Pursuit · TX Cross-Cutting
- EN-2
- 1 shared controlM10.03 Terrain Overlay UpdateM10 Exploitation & Pursuit · TX Cross-Cutting
- EN-2
- 1 shared controlM8.09 Contained Forensic PreservationM8 Isolation / Retrograde · T5 Data
- CE-6
- 1 shared controlM2.14 Control Failure DetectionM2 Defense in Depth · TX Cross-Cutting
- CE-6