Control Statement
For each facility carrying a mission service, the environmental conditions the service depends on shall be identified, and the period the facility can sustain the service without them shall be stated.
Purpose. To know how long the physical ground holds without support, so that recovery objectives are not contradicted by the buildings the services sit in.
Discussion
This control's value is almost entirely in a comparison that two separate documents make impossible: the environmental sustain period of a facility against the recovery time objectives of the services housed in it. A four-hour uninterruptible supply under a twenty-four-hour recovery objective is a contradiction that is obvious once the two figures are placed side by side and invisible while they live in a facilities record and a continuity plan respectively. Putting facilities on the overlay is what makes the comparison routine.
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.
- Number of facilities with a stated endurance period
- Endurance period compared against the recovery time objectives of the services housed there
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.
| AO | CTI | SOC | HUNT | PLAT | ISSO |
|---|---|---|---|---|---|
| Authorizing Official / CISO: Accountable | Cyber Threat Intelligence cell: Informed | SOC / Defensive Operations: Consulted | Hunt team: Informed | Platform and product owners: Responsible | Governance / 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
- ConsultedSOC / Defensive Operations
- InformedHunt team
- ResponsiblePlatform and product owners
- ConsultedGovernance / RMF / ISSO
Inputs and Outputs
Consumes
- FC-1 Facility Terrain IdentificationFacilities carrying mission services
- RC-1 Recovery ObjectivesRecovery objectives of the services housed
Produces
- RC-1 Recovery ObjectivesEndurance constraint on achievable recovery objectives
- CE-5 Remediation Backlog PrioritizationFacilities whose endurance is shorter than the objectives they must support
Activities
- L2Identify the environmental conditions each mission-carrying facility depends on — power, cooling, water, connectivity, physical access.
- L2State the period the facility can sustain the service without each.
- L2Record both against the facility on the overlay.
- L3Test the stated sustain periods rather than taking them from design specification or vendor rating.
- L3Compare each sustain period against the recovery objectives (RC-1) of the services housed there, and raise a finding on every contradiction.
- L3Include dependencies on external providers and on other facilities, since a sustain period assuming resupply is contingent on the resupply arriving.
- L3Record the degradation sequence — which services lose availability first as a condition is lost — so the loss is a plan rather than a discovery.
- L4Trend tested sustain periods, since capacity degrades with equipment age while the recorded figure does not.
- L4Measure the interval since each sustain period was last tested rather than last recorded.
- L5Feed persistent contradictions between sustain period and recovery objective into siting, investment or objective revision, rather than carrying the finding indefinitely.
Measurement
Percentage of mission-carrying facilities whose tested sustain period satisfies the recovery objectives of services housed there.
Median age of the most recent sustain period test.
Evidence and Assessment
Environmental dependency record; ride-through test results; comparison against recovery objectives; degradation sequence.
Examine the stated periods against test evidence; compare against the recovery objectives of the services housed there; test whether periods derive from measurement or from design specification.
Related Guidance
- PE-11
- PE-13
- CP-2
- PR.IR-04
- RC.RP-01
Position in the Chain
Derived from the other controls’ own declarations, so the two directions cannot disagree.
Feeds
Nothing downstream — this control terminates a chain.
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
- M8Isolation / RetrogradeGive ground deliberately to preserve the force. Degrade gracefully; never fail open.1 of 17 techniques — M8.15
- M11ReconstitutionRestore the mission on evidence, not on hope — and prove it before you need it.1 of 11 techniques — M11.09
Terrain It Is Named On
- T6Operational TechnologyEnvironmental continuity and building control are the same systems seen from the facilities side; scoring them twice is a modeling error, ignoring the overlap is worse.
- T8FacilitiesEnvironmental continuity, and its dependency on the availability floor rather than on a building specification.
Artifacts It Stands On
- producesEnvironmental continuity recordHow long each facility can carry the mission services housed in it — power, cooling, connectivity — measured against the recovery objectives those services must meet.
- 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.
- consumesFacility terrain registerWhere elements physically are, which personnel populations are associated with each site, and which facilities carry mission services.
Roles It Puts to Work
- AccountableAuthorizing Official / CISOIntent, risk acceptance, and the scheme itself.
- ResponsiblePlatform and product ownersTheir own terrain. Obstacles get emplaced on their ground, so they site them.
- ConsultedSOC / Defensive OperationsManeuver. Executes fires and emplaces obstacles inside the standing rules of engagement.
- ConsultedGovernance / RMF / ISSOTranslating cycle outputs into FISMA and RMF artifacts, and owning the rules of engagement.
- InformedCyber Threat Intelligence cellFrame, Map and Fuse. The intelligence requirements, the threat courses of action, and the confidence levels.
- InformedHunt teamCounterattack. Works the hypotheses that Fuse raises.