Skip to main content

BCD-12: Alternate Storage Site

BCD 9 — Critical Protect

Mechanisms exist to establish an alternate storage site that stores both the assets and necessary agreements needed for the recovery of Technology Assets, Applications, Services and/or Data (TAASD).

Renumbered: Formerly BCD-08 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, BCD-12 was Technology Assets, Applications and/or Services (TAAS) Recovery & Reconstitution. That control is now BCD-18.

Control Question: Does the organization establish an alternate storage site that stores both the assets and necessary agreements needed for the recovery of Technology Assets, Applications, Services and/or Data (TAASD)?

General (21)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.2 A1.2-POF9
GovRAMP CP-06 CP-06(02)
GovRAMP Low+ CP-06
GovRAMP Moderate CP-06
GovRAMP High CP-06 CP-06(02)
ISO 27002 2022 8.14
ISO 27017 2015 17.2.1
ISO 27018 2025 8.14
MITRE ATT&CK 16 T1070 T1070.001 T1070.002 T1070.008 T1119 T1486 T1565 T1565.001
MPA Content Security Program 5.3.1 OP-2.1
NIST 800-53 R4 CP-6
NIST 800-53 R5.2 CP-06 CP-06(02) PE-23
NIST 800-53B R5 (moderate) (source) CP-06
NIST 800-53B R5 (high) (source) CP-06 CP-06(02)
NIST 800-82 R3 CP-06 CP-06(02) PE-23
NIST 800-82 R3 MODERATE OT Overlay CP-06
NIST 800-82 R3 HIGH OT Overlay CP-06 CP-06(02)
NIST 800-161 R1 CP-6 PE-23
NIST 800-161 R1 Flow Down PE-23
NIST 800-161 R1 Level 2 CP-6 PE-23
NIST 800-161 R1 Level 3 CP-6 PE-23
US (6)
EMEA (4)
Framework Mapping Values
EMEA Germany BAIT 2017 10.5
EMEA Germany C5 2026 OPS-09.05B
EMEA Spain CCN-STIC 825 op.cont.4
EMEA LUX CCSF 20/750 2020 3.5-58
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 10.44(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 establish an alternate storage site that includes both the assets and necessary agreements to permit the storage and recovery of system backup information.

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-12_A01 an alternate storage site is established.
  2. BCD-12_A02 the alternate storage site stores the necessary agreements needed for the recovery of Technology Assets, Applications, Services and/or Data (TAASD).
  3. BCD-12_A03 the alternate storage site provides controls equivalent to that of the primary site.
  4. BCD-12_A04 the location or site of the facility where the system resides is planned considering physical and environmental hazards.
  5. BCD-12_A05 the alternate storage site stores the assets needed for the recovery of Technology Assets, Applications, Services and/or Data (TAASD).

Evidence Requirements

E-BCD-12 Data Backups - Remote

Documented evidence of event logs for the off-site / remote data backup solution.

Business Continuity
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

  • Cloud-based backup storage: AWS S3, Azure Blob Storage, or Backblaze B2
  • Off-site backup media storage (e.g., Iron Mountain)

Small

  • Cloud-based backup storage: AWS S3, Azure Blob Storage, or Backblaze B2
  • Off-site backup media storage (e.g., Iron Mountain)

Medium

  • AWS S3 / Azure Blob / Google Cloud Storage
  • Managed backup service (e.g., Veeam Cloud Connect, Acronis Cloud Backup)
  • Geographically separated alternate storage site

Large

  • AWS / Azure / Google Cloud alternate storage region
  • Enterprise backup solution with cloud tiering (e.g., Veeam, Commvault)
  • Geographically separated alternate storage site with tested recovery

Enterprise

  • Multi-region cloud storage (AWS, Azure, or Google Cloud)
  • Enterprise backup and DR platform (e.g., Commvault, Veeam Enterprise, Zerto)
  • Alternate storage site with defined SLAs and tested failover
  • NIST SP 800-34 contingency planning alignment

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.