ASOM-Fedv6.1Open the explorer
M11.02 · M11 Reconstitution · 2 of 11

Isolated Recovery Environment

What It Does

Hold the means of recovery outside the blast radius of the production identity plane, so compromise cannot reach what rebuilds you.

Observable indicator. Recovery is possible after total compromise of production identity.

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 maneuverM11 ReconstitutionRestore the mission on evidence, not on hope — and prove it before you need it.
  • Terrain layerT5 DataThe objective. Key terrain: Sensitive mission records, PII stores, fee and financial data.
  • Position in the form2 of 11M11 carries 11 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.

  • Phase 0ShapeContinuous terrain preparation, zero-trust hardening, partnerships, threat intelligence.
  • Phase IVStabilizeEradicate, verify, and preserve availability through the recovery.

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.

  • RC-2 Isolated Recovery CapabilityReconstitution and Recovery — To ensure the recovery capability survives the compromise it exists to recover from.
  • 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.

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.

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 27 that share at least one control.