ASOM-Fedv6.1Open the explorer
M11.09 · M11 Reconstitution · 9 of 11

Alternate Facility Activation

What It Does

Be able to run the mission from somewhere else, and prove it by doing so rather than by documenting it.

Observable indicator. The alternate facility has carried the mission within its stated period.

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 layerT8 FacilitiesThe physical boundary. Key terrain: Data center and wiring closet boundaries, public-access areas, maintenance routes.
  • Position in the form9 of 11M11 carries 11 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 IVStabilizeEradicate, verify, and preserve availability through the recovery.
  • 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.

  • FC-4 Environmental ContinuityFacilities Terrain — To know how long the physical ground holds without support, so that recovery objectives are not contradicted by the buildings the services sit in.
  • RC-1 Recovery ObjectivesReconstitution and Recovery — To establish what recovery must achieve, so that restoration can succeed or fail rather than simply take however long it takes.
  • RC-5 Reconstitution ExerciseReconstitution and Recovery — To convert declared recovery capability into demonstrated capability, so that objectives are proven before they are needed.

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