What It Does
Preserve evidence in a way that survives containment and recovery, on storage the adversary could not reach.
Observable indicator. Evidence survives the response intact and admissible.
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 maneuverM8 Isolation / RetrogradeGive ground deliberately to preserve the force. Degrade gracefully; never fail open.
- Terrain layerT5 DataThe objective. Key terrain: Sensitive mission records, PII stores, fee and financial data.
- Position in the form9 of 17M8 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.
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.
- KT-2 Decisive Point Protection FloorKey Terrain and Decisive Points — To ensure designation produces protection, so that identifying a decisive point is an act with consequences rather than an annotation.
- 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-3 Evidence PreservationEngagement and Pursuit — To ensure the material an engagement depends on still exists when it is needed, and is admissible where that matters.
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-FH File HashingDetect tactic
- D3-FC File CarvingDetect 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 31 that share at least one control.
- 1 shared controlM11.02 Isolated Recovery EnvironmentM11 Reconstitution · T5 Data
- KT-2
- 1 shared controlM2.03 Crown-Jewel EnclaveM2 Defense in Depth · T5 Data
- KT-2
- 1 shared controlM2.04 Independent Control RedundancyM2 Defense in Depth · TX Cross-Cutting
- KT-2
- 1 shared controlM2.07 Web Application ProtectionM2 Defense in Depth · T4 Applications and Workloads
- KT-2
- 1 shared controlM2.08 API Authorization EnforcementM2 Defense in Depth · T4 Applications and Workloads
- KT-2
- 1 shared controlM2.10 Egress Data Loss PreventionM2 Defense in Depth · T5 Data
- KT-2