Skip to main content

BCD-21: Redundant Secondary System

BCD 5 — Medium Protect

Mechanisms exist to maintain a failover capability, which is not collocated with the primary Technology Asset, Application and/or Service (TAAS), which can be activated with little-to-no loss of information or disruption to operations.

Renumbered: Formerly BCD-11.7 in SCF 2025.4.

Control Question: Does the organization maintain a failover capability, which is not collocated with the primary Technology Asset, Application and/or Service (TAAS), which can be activated with little-to-no loss of information or disruption to operations?

General (8)
Framework Mapping Values
CSA CCM 4.1.0 BCR-03 BCR-11
ISO 27002 2022 8.14
ISO 27017 2015 17.2.1
ISO 27018 2025 8.14
NIST 800-53 R4 CP-9(6)
NIST 800-53 R5.2 CP-09(06)
NIST 800-82 R3 CP-09(06)
NIST 800-160 Vol2 R1 CP-09(06)
US (1)
Framework Mapping Values
USA Federal DoW BaTB OT 2026 8
EMEA (6)
Framework Mapping Values
EMEA Spain CCN-STIC 825 op.cont.4
EMEA EU DORA 2023 Article 12.4
EMEA EU DORA RTS 2024 Article 26.2(a)
EMEA EU NIS2 Annex 2024 4.1.2(g) 4.2.1 4.2.4(a) 4.2.4(b) 4.2.4(d) 13.1.2(b)
EMEA LUX CCSF 20/750 2020 3.7.1-79
EMEA Saudi Arabia OTCC-1 2022 3-1-1-2
APAC (2)
Framework Mapping Values
APAC Malaysia RMiT 2025 10.25 A10-B5(d)(i)
APAC Singapore MAS TRM 2021 8.1.2 8.5.2(c)

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 maintain a failover capability, which is not collocated with the primary Technology Asset, Application and/or Service (TAAS), which can be activated with little-to-no loss of information or disruption to operations.

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

  1. BCD-21_A01 system backup is conducted by maintaining a redundant secondary system that can be activated without loss of information or disruption to operations.
  2. BCD-21_A02 system backup is conducted by maintaining a redundant secondary system that is not collocated with the primary system.

Evidence Requirements

E-BCD-19 Isolated Recovery Environment & Reserve Hardware

Documented evidence of an isolated recovery environment, reserve hardware, redundant secondary systems and/or failover capability.

Business Continuity

Technology Recommendations

Micro/Small

  • Continuity of Operations Plan (COOP)
  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

Small

  • Continuity of Operations Plan (COOP)
  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

Medium

  • Continuity of Operations Plan (COOP)
  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

Large

  • Continuity of Operations Plan (COOP)
  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

Enterprise

  • Continuity of Operations Plan (COOP)
  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.