ASOM-Fedv6.1Open the explorer
RC-5 · Reconstitution and Recovery

Reconstitution Exercise

Control Statement

The organization shall exercise reconstitution against a stated failure scenario on a defined cadence, and every declared recovery objective shall have been demonstrated within its stated period.

Purpose. To convert declared recovery capability into demonstrated capability, so that objectives are proven before they are needed.

Discussion

This is the control that makes the rest of the family real, and it is the one the framework's own analysis identifies as most often asserted rather than demonstrated. The scenario is where exercises usually fall short: an exercise that restores a single application from a clean environment demonstrates a procedure, not a reconstitution. The scenarios that test what RC-2 and RC-3 actually claim are the uncomfortable ones — loss of the identity plane, loss of the management plane, recovery under an assumption that production credentials are held by the adversary. An exercise program that has never run those has not tested the family's central dependency.

Goals and Metrics

A metric that cannot come out badly is not a metric. Each of these is capable of reporting that the control is not working.

Every declared objective has been demonstrated within its stated period.
  • Percentage of recovery objectives demonstrated within their stated period
  • Elapsed time since the last reconstitution exercise
Exercises are honest.
  • Number of exercises in which a declared objective was not met, and the resulting actions

Accountability

Exactly one role is accountable, and every other role carries at least Informed — no control in the published catalog leaves a role with zero relationship to it. That is a stated property of how these were authored, not a coincidence, and not a claim that every role's work is worth equal attention here.

AOCTISOCHUNTPLATISSO
Authorizing Official / CISO: AccountableCyber Threat Intelligence cell: InformedSOC / Defensive Operations: ResponsibleHunt team: ConsultedPlatform and product owners: ConsultedGovernance / RMF / ISSO: Consulted

AO Authorizing Official / CISOCTI Cyber Threat Intelligence cellSOC SOC / Defensive OperationsHUNT Hunt teamPLAT Platform and product ownersISSO Governance / RMF / ISSO

  • AccountableAuthorizing Official / CISO
  • InformedCyber Threat Intelligence cell
  • ResponsibleSOC / Defensive Operations
  • ConsultedHunt team
  • ConsultedPlatform and product owners
  • ConsultedGovernance / RMF / ISSO

Inputs and Outputs

Consumes

Produces

Activities

  1. L2Exercise reconstitution against a stated failure scenario.
  2. L2Record the scenario, participants, measured elapsed times and findings raised.
  3. L2Compare measured times against declared objectives.
  4. L3Define the exercise cadence with provenance per GA4, and flag objectives overdue for demonstration.
  5. L3Include at least one scenario per period in which the identity plane is unavailable and production credentials are assumed adversary-held.
  6. L3Exercise the dependency sequence across services (RC-3) rather than single services in isolation.
  7. L3Disposition findings raised by exercise through CG-4 rather than closing them with the exercise report.
  8. L4Measure the proportion of declared objectives demonstrated within their stated period, and treat a shortfall as a reportable condition.
  9. L4Trend measured recovery times across exercises, since drift upward indicates decay in procedures that still pass.
  10. L5Derive scenarios from observed adversary tradecraft and from engagements under M10, rather than repeating a scenario library that the estate has learned to pass.

Measurement

Outcome

Percentage of declared objectives demonstrated within their stated period.

Performance

Trend in measured recovery times across successive exercises.

Evidence and Assessment

Evidence expected

Exercise record: scenario, participants, measured recovery times, findings raised and their disposition.

Assessment procedure

Examine the exercise records for cadence and scenario realism; compare measured times against declared objectives; test that findings were dispositioned; examine whether any scenario has assumed loss of the identity plane.

Related Guidance

Inherits
  • CP-4
  • CP-4(1)
  • IR-3
Satisfies
  • RC.RP-06
  • ID.IM-02

Position in the Chain

Derived from the other controls’ own declarations, so the two directions cannot disagree.

Where This Control Is Used

Derived, in every case, from the declaration at the other end: the forms whose techniques name this control, the artifacts whose producing and consuming controls include it, the layers whose control lists name it, and the roles its own accountability chart puts to work. Nothing here is authored on this page, so the sheet cannot claim an edge the other end does not.

Forms of Maneuver It Assesses

  • M11ReconstitutionRestore the mission on evidence, not on hope — and prove it before you need it.4 of 11 techniques — M11.06, M11.07, M11.08, M11.09

Terrain It Is Named On

  • TXCross-CuttingThe reconstitution exercise is the rehearsal that converts an automation claim into a demonstrated one.

Artifacts It Stands On

  • producesReconstitution exercise reportWhat was rebuilt, from what media, in what time, verified how — and which recovery objectives were missed. Includes supplier severance scenarios.
  • consumesTrusted rebuild pathA documented, walked path to rebuild each decisive point inside its recovery time budget, from media held outside the production identity plane — including a path for the identity plane itself.
  • consumesRecovery objectives registerA declared recovery time and recovery point objective per mission service, agreed with the service owner and constrained by statutory deadlines rather than by what is currently achievable.
  • consumesRecovery integrity verification recordRestored data verified against an independently held integrity record, so that recovery is a demonstrated claim rather than an assumption that the backup was clean.

Roles It Puts to Work