← ISO 27001 · A.5 — Organisational
A.5.29 — Information security during disruption
high
business-continuityrecovery
Requirement
The organisation shall plan how to maintain information security at an appropriate level during disruption.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
business continuitydisruptiondisaster recoveryresilience
Required element 2 — any one of
planmaintainsecurity
Supporting terms — specificity signals
rtorpodegraded modebreak glassemergency accesstested
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| HIPAA | 164.308(a)(7)(ii)(B) | Disaster recovery plan (R) | recovery business-continuity |
| NIST CSF 2.0 | RC.RP-01 | The recovery portion of the incident response plan is executed | recovery business-continuity |
| SOC 2 | CC9.1 | Risk mitigation for business disruption | business-continuity recovery |
| SOC 2 | CC7.5 | Recovery from identified incidents | recovery |
| SOC 2 | A1.3 | Recovery plan testing | business-continuity |
| HIPAA | 164.308(a)(7)(ii)(C) | Emergency mode operation plan (R) | business-continuity |
| NIST CSF 2.0 | RC.RP-05 | Integrity of restored assets is verified | recovery |
| SOC 2 | A1.2 | Backup, recovery and environmental protection | recovery |