ISO 27001:2022 · Organizational controls
ISO 27001:2022 5.29: Information security during disruption
ISO 27001:2022 5.29 covers Information security during disruption. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.5.29, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Continuity plans restore services but omit security controls such as logging, access control or....
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.
What evidence supports 5.29?
- Annex A organizational controlStatement of Applicability entry for control A.5.29, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A organizational controlBusiness continuity plans that contain information security requirements and the controls, systems and tools needed during disruption
- Annex A organizational controlA documented analysis of which security controls must be adapted during disruption and how
- Annex A organizational controlCompensating controls defined for security controls that cannot be maintained in disruption
- Annex A organizational controlContinuity test or exercise results that include restoration of security to the required level and within the required time
Where this requirement comes from
This is our own statement of ISO 27001:2022 5.29, 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
- Continuity plans restore services but omit security controls such as logging, access control or monitoring
- Emergency workarounds bypass security with no compensating measure
- Exercises test only availability, never the security state after recovery
- The impact analysis ignores confidentiality and integrity
How it maps to SOC 2
- CC9.1 high Information security during disruption is mitigation for business disruption risk.
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.