ISO 22301:2019 6.2.1: Establishing business continuity objectives

What else in your programme already covers this

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

NIST Cybersecurity Framework 2.0 · 5 controls

NIST-CSF-GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
NIST-CSF-GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained
NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated

NIST SP 800-53 Rev 5 · 5 controls

NIST800-CP-2 CP-2 Contingency Plan
NIST800-PL-1 PL-1 Policy and Procedures
NIST800-SA-24 SA-24 Design For Cyber Resiliency
SP800-53-PL Planning Family
SP800-53-PM Program Management Family

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-BCR-02 Risk Assessment and Impact Analysis
CCM-BCR-03 Business Continuity Strategy

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

SOC 2 · 2 controls

SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)

APRA CPS 230 Operational Risk Management · 1 control

CPS230-19 Tolerance Levels for Each Critical Operation

Azure Security Benchmark · 1 control

ASBv3-GS-8 Define and implement backup and recovery strategy

C5 (Germany) · 1 control

C5-BCM-03 Planning business continuity

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-9 Next Business Day Recovery Time Objective

COBIT 2019 · 1 control

DSS04.01 DSS04.01 Define the business continuity policy, objectives and scope

FedRAMP High · 1 control

CP-2 Contingency Plan

ISO 28002:2011 · 1 control

A.4.5 A.4.5 Resilience objectives and targets

ISO/IEC 42001:2023 · 1 control

6.2 AI objectives and planning to achieve them

NIST SP 800-161 Rev 1 · 1 control

161R1-PM-28 Risk Framing

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.

You are reading one control. How much of ISO 22301:2019 have you already done?

ISO 22301:2019 6.2.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 22301:2019 your existing evidence covers. Hold APRA CPS 230 Operational Risk Management and 28 of 57 ISO 22301:2019 controls already carry evidence.

If you hold APRA CPS 230 Operational Risk Management49.1% covered · 29 gaps If you hold NIST Cybersecurity Framework 2.047.4% covered · 30 gaps If you hold C5 (Germany)42.1% covered · 33 gaps If you hold CFTC System Safeguards (17 CFR 37, 38, 39, 49)38.6% covered · 35 gaps If you hold NIST SP 800-161 Rev 136.8% covered · 36 gaps If you hold SOC 235.1% covered · 37 gaps

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 APRA CPS 230 Operational Risk Management pair alone.

See the released pairs, $299 each Browse the graph free