ISO 27001:2022 · Organizational controls
ISO 27001:2022 5.30: ICT readiness for business continuity
ISO 27001:2022 5.30 covers ICT readiness for business continuity. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.5.30, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is RTOs and RPOs are set by IT without a business impact analysis.
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.
What evidence supports 5.30?
- Annex A organizational controlStatement of Applicability entry for control A.5.30, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A organizational controlThe business impact analysis with prioritized activities, supporting ICT services and their RTOs, and RPOs for required information
- Annex A organizational controlSelected ICT continuity strategies covering before, during and after disruption
- Annex A organizational controlManagement-approved ICT continuity plans with response and recovery procedures, capacity specifications, RTOs and RPOs
- Annex A organizational controlExercise and test reports showing recovery achieved within RTO and RPO, with remediation of shortfalls
Where this requirement comes from
This is our own statement of ISO 27001:2022 5.30, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- RTOs and RPOs are set by IT without a business impact analysis
- Plans are approved but recovery has never been tested end to end
- Recovery capacity specifications do not match what prioritized activities actually need
- Cloud and third-party ICT services are left out of the continuity plans
How it maps to SOC 2
- A1.3 high ICT readiness for continuity requires recovery plans be exercised.
- CC7.5 high ICT readiness for business continuity covers recovery after an incident.
- CC9.1 high ICT readiness for continuity is the technical disruption mitigation.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.