C5 (Germany)
C5: Business Continuity Management

C5 (Germany) C5-BCM-03: Planning business continuity

Implement a single documented continuity and contingency planning framework derived from the impact analysis and anchored to standards in a statement of applicability, covering scope, plan accessibility, named owners, communication and customer notification, recovery and interim procedures, activation, improvement and incident management interfaces.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 55 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.

FedRAMP High · 5 controls

  • CP-1 Policy and Procedures
  • CP-10 System Recovery and Reconstitution
  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • CP-2(3) Resume Mission and Business Functions

FedRAMP Moderate · 5 controls

  • CP-1 Policy and Procedures
  • CP-10 System Recovery and Reconstitution
  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • CP-2(3) Resume Mission and Business Functions

ISO 22301:2019 · 5 controls

  • 6.2.1 Establishing business continuity objectives
  • 8.1 Operational planning and control
  • 8.3.2 Identification of strategies and solutions
  • 8.4.1 General
  • 8.4.4 Business continuity plans
  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-P40 Required Content of the Business Continuity Plan
  • CPS230-P41 BCP Execution Capability and Tolerance Breach Reporting
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
  • NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-27 Coordination of the Recovery Plan with Members and Market Participants
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

HIPAA Security Rule · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

NIST SP 800-66 Rev 2 · 3 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
  • CPS220-P35 Required Content of Risk Management Policies and Procedures

APRA CPS 234 · 1 control

  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • BR-1 Ensure regular automated backups

CIS Controls v8 · 1 control

  • CIS-11.1 Establish and Maintain a Data Recovery Process

CMMC 2.0 · 1 control

DORA · 1 control

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

SOC 2 · 1 control

  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

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 C5: Business Continuity Management

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-BCM-03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) 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. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

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