Requirement
The entity tests recovery plan procedures supporting system recovery to meet its availability objectives.
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
testexercisedrillsimulation
Required element 2 — any one of
recoverycontinuityfailoverrestore
Supporting terms — specificity signals
annualtabletopgame daychaosresultslessons learned
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.5.29 | Information security during disruption | business-continuity |
| HIPAA | 164.308(a)(7)(ii)(B) | Disaster recovery plan (R) | business-continuity |
| HIPAA | 164.308(a)(7)(ii)(C) | Emergency mode operation plan (R) | business-continuity |
| HIPAA | 164.308(a)(7)(ii)(D) | Testing and revision procedures (A) | dr-testing |
| NIST CSF 2.0 | RC.RP-01 | The recovery portion of the incident response plan is executed | business-continuity |
| NIST CSF 2.0 | PR.DS-11 | Backups of data are created, protected and tested | dr-testing |