ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.29: Information security during disruption

The organization is to plan how it will keep information security at a suitable level while operations are disrupted. Purpose (stated in ISO/IEC 27002:2022): protects information and associated assets 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.29.

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

What else in your programme already covers this

This control maps to 131 controls across 26 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 · 20 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(1) Telecommunications Services | Priority of Service Provisions (CP-8(1))
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))

FedRAMP Moderate · 20 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(1) Telecommunications Services | Priority of Service Provisions (CP-8(1))
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))

ISO 22301:2019 · 19 controls

  • 6.2.1 Establishing business continuity objectives
  • 7.4 Communication
  • 7.5.1 General
  • 8.1 Operational planning and control
  • 8.2 Business impact analysis and risk assessment
  • 8.2.1 General
  • 8.2.2 Business impact analysis
  • 8.3 Business continuity strategies and solutions
  • 8.3.1 General
  • 8.3.2 Identification of strategies and solutions
  • 8.3.3 Selection of strategies and solutions
  • 8.4 Business continuity plans and procedures
  • 8.4.1 General
  • 8.4.3 Warning and communication
  • 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 · 12 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.OC-05 Outcomes, capabilities, and services that the organization depends on 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-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • 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

CIS Controls v8 · 5 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.3 Protect Recovery Data
  • CIS-11.4 Establish and Maintain an Isolated Instance of Recovery Data
  • CIS-11.5 Test Data Recovery
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

SOC 2 · 5 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-P12 Key Principles for Operational Risk, Resilience and Service Providers
  • CPS230-P40 Required Content of the Business Continuity Plan

ISO 27001:2013 · 3 controls

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

ISO 27701:2019 · 3 controls

  • 6.14 Information security aspects of business continuity management
  • 6.14.1 Information security continuity
  • 6.14.2 Redundancies
  • CFTC-SS-3 Information Security Category
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

ISO/IEC 29100:2024 · 2 controls

  • 29100-6.10 Information security
  • ISO29100-5.10.10 Information Security

NIS2 Directive · 2 controls

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management
  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications
  • E8-BACKUP-ML1 Regular Backups (ML1)

APRA CPS 234 · 1 control

  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • AEO-12 Crisis Management and Incident Recovery

C5 (Germany) · 1 control

DORA · 1 control

ISO 27002:2022 · 1 control

  • 5.29 Information security during disruption

PCI DSS 4.0 · 1 control

  • 12.3.1 12.3.1 Targeted risk analysis for flexible-frequency requirements

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.29 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 131 it maps to, and the evidence behind each claim, over MCP and REST.