Requirement
Backup copies of information, software and systems shall be maintained and regularly tested in accordance with the agreed topic-specific policy on backup.
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
backupbacked up
Required element 2 — any one of
testrestoreverifiedschedulefrequency
Supporting terms — specificity signals
dailyencryptedoffsiteimmutableretentionrpocross-regionencrypt
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no backups
backups are never tested
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC9.1 | Risk mitigation for business disruption | recovery backup |
| SOC 2 | A1.2 | Backup, recovery and environmental protection | backup recovery |
| NIST CSF 2.0 | PR.DS-11 | Backups of data are created, protected and tested | backup recovery |
| SOC 2 | CC7.5 | Recovery from identified incidents | recovery |
| HIPAA | 164.308(a)(7)(ii)(A) | Data backup plan (R) | backup |
| HIPAA | 164.308(a)(7)(ii)(B) | Disaster recovery plan (R) | recovery |
| NIST CSF 2.0 | RC.RP-01 | The recovery portion of the incident response plan is executed | recovery |
| NIST CSF 2.0 | RC.RP-05 | Integrity of restored assets is verified | recovery |