← NIST CSF 2.0 · RECOVER — Incident Recovery Plan Execution
RC.RP-01 — The recovery portion of the incident response plan is executed
high
recoverybusiness-continuity
Requirement
The recovery portion of the incident response plan is executed once initiated from the incident response process.
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
recoveryrestorerecover
Required element 2 — any one of
planprocedurerunbookexecuted
Supporting terms — specificity signals
rtorpopriority orderverificationfailoverrebuild
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 recovery |
| HIPAA | 164.308(a)(7)(ii)(B) | Disaster recovery plan (R) | 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 |
| ISO 27001 | A.8.13 | Information backup | recovery |
| HIPAA | 164.308(a)(7)(ii)(C) | Emergency mode operation plan (R) | business-continuity |
| SOC 2 | A1.2 | Backup, recovery and environmental protection | recovery |