ISO 27002: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: keep the organization's information and associated assets available during disruption. Guidance: ICT readiness is a key part of both continuity and security management, keeping objectives achievable during disruption. ICT continuity requirements come out of the business impact analysis, which uses impact types and criteria to judge how disruption to activities delivering products and services causes harm over time; the size and duration of impact identify prioritized activities, each given a recovery time objective (RTO), and then the resources those activities need, which also get RTOs and include ICT services. The analysis can be extended to set performance and capacity requirements for ICT systems and, for the information needed, recovery point objectives (RPO) for the information needed. From the impact analysis and risk assessment, the organization chooses ICT continuity strategies covering before, during and after disruption, possibly combining solutions, and builds, implements and tests plans that deliver the required ICT availability in the required time. It should ensure a suitable structure of people with the responsibility, authority and competence to get ready for disruption, limit it and react to it; ICT continuity plans with response and recovery procedures that are regularly exercised and tested and approved by management; and plans that state performance and capacity specifications from the impact analysis, the RTO of each prioritized ICT service with restoration procedures, and the RPO of prioritized information with its restoration procedures. Other information: ICT continuity lets the organization respond to and recover from ICT disruption whatever the cause, keep prioritized activities supplied with ICT, and act before disruption and once an incident that could cause one is detected; ISO/IEC 27031, ISO 22301, ISO 22313 and ISO/TS 22317 give more.
This control maps to 145 controls across 36 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-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-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
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.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
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
You are reading one control. How much of ISO 27002:2022 have you already done?
ISO 27002:2022 5.30 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002: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. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.