ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.30: ICT readiness for business continuity

ICT readiness is to be planned, put in place, kept current and tested so that it meets the continuity objectives of the business and the requirements for ICT continuity. Purpose (stated in ISO/IEC 27002:2022): ensures information and associated assets remain available during disruption. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.30.

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

What else in your programme already covers this

This control maps to 127 controls across 29 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 · 16 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • CP-2(3) Resume Mission and Business Functions
  • CP-4 Contingency Plan Testing
  • CP-4(1) Coordinate with Related Plans
  • CP-6 Alternate Storage Site
  • CP-6(1) Alternate Storage Site | Separation from Primary Site (CP-6(1))
  • CP-6(3) Alternate Storage Site | Accessibility (CP-6(3))
  • CP-7 Alternate Processing Site
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • CP-7(3) Alternate Processing Site | Priority of Service (CP-7(3))
  • CP-8 Telecommunications Services
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • IR-3 Incident Response Testing

FedRAMP Moderate · 16 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-2 Contingency Plan
  • CP-2(1) Coordinate with Related Plans
  • CP-2(3) Resume Mission and Business Functions
  • CP-4 Contingency Plan Testing
  • CP-4(1) Coordinate with Related Plans
  • CP-6 Alternate Storage Site
  • CP-6(1) Alternate Storage Site | Separation from Primary Site (CP-6(1))
  • CP-6(3) Alternate Storage Site | Accessibility (CP-6(3))
  • CP-7 Alternate Processing Site
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • CP-7(3) Alternate Processing Site | Priority of Service (CP-7(3))
  • CP-8 Telecommunications Services
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • IR-3 Incident Response Testing

ISO 22301:2019 · 14 controls

  • 6.2.1 Establishing business continuity objectives
  • 8.1 Operational planning and control
  • 8.2 Business impact analysis and risk assessment
  • 8.2.2 Business impact analysis
  • 8.3 Business continuity strategies and solutions
  • 8.3.2 Identification of strategies and solutions
  • 8.3.3 Selection of strategies and solutions
  • 8.3.5 Implementation of solutions
  • 8.4 Business continuity plans and procedures
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery
  • 8.5 Exercise programme
  • 8.6 Evaluation of business continuity documentation and capabilities
  • 9.2.1 General

NIST SP 800-53 Rev 5 · 8 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-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.DS-11 Backups of data are created, protected, maintained, and tested
  • 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-02 Recovery actions are selected, scoped, prioritized, and performed
  • NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • CPS230-19 Tolerance Levels for Each Critical Operation
  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-33 Systematic BCP Testing Program
  • CPS230-34 Tailoring of the Testing Program
  • CPS230-P25 Information and Technology Capability and Asset Health
  • CPS230-P41 BCP Execution Capability and Tolerance Breach Reporting

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.2 Perform Automated Backups
  • CIS-11.4 Establish and Maintain an Isolated Instance of Recovery Data
  • CIS-11.5 Test Data Recovery

SOC 2 · 4 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • ASD37-34 Regular backups (Essential)
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • ASD37-36 System recovery capabilities (Very Good)

C5 (Germany) · 3 controls

  • C5-BCM-02 Business impact analysis policies and instructions
  • C5-BCM-03 Planning business continuity
  • C5-BCM-04 Verification, updating and testing of the business continuity
  • CFTC-SS-11 Testing and Review of Business Continuity and Disaster Recovery Capabilities
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • CFTC-SS-9 Next Business Day Recovery Time Objective

DORA · 3 controls

  • DORA-Art.11 Response and recovery
  • DORA-Art.16 Simplified ICT risk management framework
  • DORA-Art.24 General requirements for the performance of digital operational resilience testing

COBIT 2019 · 2 controls

  • DSS04.03 DSS04.03 Develop and implement a business continuity response
  • DSS04.04 DSS04.04 Exercise, test and review the business continuity plan (BCP) and disaster response plan (DRP)

ISO 27001:2013 · 2 controls

  • A.17.1.2 Implementing information security continuity
  • A.17.1.3 Verify, review and evaluate information security continuity

ISO 27002:2022 · 2 controls

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

ISO 27701:2019 · 2 controls

  • 6.14 Information security aspects of business continuity management
  • 6.14.1 Information security continuity

NIST SP 800-161 Rev 1 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • E8-BACKUP-ML1 Regular Backups (ML1)
  • ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components

APRA CPS 234 · 1 control

  • CPS234-32 Annual Review and Testing of Response Plans
  • AEO-12 Crisis Management and Incident Recovery

GDPR · 1 control

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 Organizational controls – ISO 27001:2022

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

ISO 27001:2022 5.30 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 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. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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