← SOC 2 · A1 — Availability

A1.2 — Backup, recovery and environmental protection

high backuprecoverydr-testing

Requirement

The entity authorises, designs, develops, implements, operates, approves, maintains and monitors environmental protections, software, data backup processes and recovery infrastructure.

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
restorerecoverytested
Supporting terms — specificity signals
dailyretentionoffsitecross-regionencrypted backuprportoimmutable
Contradiction markers

Finding any of these outranks coverage — a policy that admits the gap is worse than silence.

no backups backups are not tested

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
NIST CSF 2.0 PR.DS-11 Backups of data are created, protected and tested backup recovery dr-testing
ISO 27001 A.8.13 Information backup backup recovery
ISO 27001 A.5.29 Information security during disruption 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
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 recovery
NIST CSF 2.0 RC.RP-05 Integrity of restored assets is verified recovery