← SOC 2 · CC7 — System Operations
CC7.5 — Recovery from identified incidents
high
incident-responserecovery
Requirement
The entity identifies, develops and implements activities to recover from identified security incidents.
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
recoveryrestorerollbackfailover
Supporting terms — specificity signals
rtorpobackuplessons learnedcorrective action
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| GDPR | Art.33 | Notification of a breach to the supervisory authority | incident-response |
| ISO 27001 | A.5.24 | Information security incident management planning and preparation | incident-response |
| ISO 27001 | A.5.29 | Information security during disruption | recovery |
| ISO 27001 | A.6.8 | Information security event reporting | incident-response |
| ISO 27001 | A.8.13 | Information backup | recovery |
| PCI DSS 4.0.1 | 10.7 | Failures of critical security controls are detected and addressed | incident-response |
| PCI DSS 4.0.1 | 12.10 | Incident response plan for suspected compromise of account data | incident-response |
| HIPAA | 164.308(a)(6)(ii) | Response and reporting (R) | incident-response |