Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
BCR - Business Continuity Management & Operational Resilience

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-BCR-04: Business Continuity Planning

Write a business continuity plan that implements the chosen resilience strategies, and keep it approved, communicated and maintained.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 43 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-46 Ongoing Risk Management of Each Material Arrangement
  • CPS230-8 Board Oversight, Approval of the BCP, Tolerance Levels and Service Provider Policy
  • CPS230-P40 Required Content of the Business Continuity Plan
  • CPS230-P41 BCP Execution Capability and Tolerance Breach Reporting

ISO 22301:2019 · 4 controls

  • 8.1 Operational planning and control
  • 8.4 Business continuity plans and procedures
  • 8.4.1 General
  • 8.4.4 Business continuity plans

FedRAMP High · 3 controls

  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • IR-3 Incident Response Testing

FedRAMP Moderate · 3 controls

  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • IR-3 Incident Response Testing
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

DORA · 2 controls

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

ISO 27002:2022 · 2 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • E8-BACKUP-ML1 Regular Backups (ML1)
  • CPS220-P35 Required Content of Risk Management Policies and Procedures
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • ASBv3-GS-8 Define and implement backup and recovery strategy

C5 (Germany) · 1 control

CIS Controls v8 · 1 control

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • BCR-04 Business Continuity Planning

ISO 27701:2019 · 1 control

  • 6.14.1 Information security continuity

NIS2 Directive · 1 control

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in BCR - Business Continuity Management & Operational Resilience

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-BCR-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 43 it maps to, and the evidence behind each claim, over MCP and REST.