ASOM-Fedv6.1Open the explorer
M11.04 · M11 Reconstitution · 4 of 11

Identity Plane Reconstitution

What It Does

Rehearse rebuilding the identity plane itself, the one system every other recovery depends on.

Observable indicator. The identity plane can be re-established without trusting the compromised one.

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 layerT1 IdentityThe high ground. Key terrain: The ICAM policy decision point, privileged accounts, external-user and mission-staff identities.
  • Position in the form4 of 11M11 carries 11 cataloged techniques; this is the 4th in catalog order.

Phases It Is Employed In

Employed in one phase of the campaign. 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 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-3 Trusted Rebuild PathReconstitution and RecoveryTo ensure that what must not be lost can be rebuilt, from a source the adversary did not touch, inside the time the mission requires.
  • KT-1 Decisive Point IdentificationKey Terrain and Decisive PointsTo concentrate defensive effort on the small number of elements whose loss is decisive, so that priority is a stated judgment rather than an emergent property of the asset register.
  • ID-1 Identity Plane DefinitionIdentity TerrainTo make identity positional, so that the plane controlling movement everywhere else is itself defensible ground rather than an assumed service.

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