Requirement
Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information.
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
retrievableexact copyrestoreprocedureschedule
Supporting terms — specificity signals
dailyencryptedoffsiteretentiontestedverifiedencrypt
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no backups
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.8.13 | Information backup | backup |
| SOC 2 | CC9.1 | Risk mitigation for business disruption | backup |
| SOC 2 | A1.2 | Backup, recovery and environmental protection | backup |
| NIST CSF 2.0 | PR.DS-11 | Backups of data are created, protected and tested | backup |
| GDPR | Art.32 | Security of processing | backup |
| NDPA 2023 | s.39 | Security, integrity and confidentiality | backup |