BCD-16: Inability to Return to Primary Site
Mechanisms exist to plan and prepare for both natural and manmade circumstances that would prevent return to the primary site.
Renumbered: Formerly BCD-09.5 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, BCD-16 was AI & Autonomous Technologies Incidents. That control is now IRO-23.
Control Question: Does the organization plan and prepare for both natural and manmade circumstances that preclude returning to the primary site?
General (3)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R4 | CP-7(6) |
| NIST 800-53 R5.2 | CP-07(06) |
| NIST 800-82 R3 | CP-07(06) |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA EU DORA RTS 2024 | Article 26.3 Article 39.2(h) |
| EMEA LUX CCSF 20/750 2020 | 3.7.3-85 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Business Continuity & Disaster Recovery (BCD) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Business Continuity / Disaster Recovery (BC/DR)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ BC/DR may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Business Continuity & Disaster Recovery (BCD) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are well-documented and kept current by process owners. ▪ A Business Continuity & Disaster Recovery (BC/DR) team, or similar function, is appropriately staffed and supported to implement and maintain BCD domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of BC/DR operations (e.g., BC/DR planning software, Disaster Recovery as a Service (DRaaS), Orchestration and Automation Tools). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to plan and prepare for both natural and manmade circumstances that preclude returning to the primary site.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- BCD-16_A01 circumstances that preclude returning to the primary processing site are planned for.
- BCD-16_A02 circumstances that preclude returning to the primary processing site are prepared for.
Evidence Requirements
- E-BCD-18 Alternate Processing / Storage Site Agreements
-
Documented evidence of alternate processing site, alternate storage site and alternate telecommunications service agreements, including separation from primary sites.
Business Continuity
Technology Recommendations
Micro/Small
- Continuity of Operations Plan (COOP)
Small
- Continuity of Operations Plan (COOP)
Medium
- Continuity of Operations Plan (COOP)
Large
- Continuity of Operations Plan (COOP)
Enterprise
- Continuity of Operations Plan (COOP)