SOC 2 · A - Availability
SOC 2 A1.3: A1.3 Testing recovery plan procedures
SOC 2 A1.3 covers A1.3 Testing recovery plan procedures. The held text names 4 evidence records for it, the first being Disaster recovery or continuity test plan and results in the period. The common gap an assessor flags is No recovery test performed in the period.
Procedures in the recovery plan that support system recovery are tested to confirm objectives can be met. Points of focus: business continuity plan testing is performed periodically, with scenarios weighted by how likely and how severe threats are, components across the organisation and its vendors that can impair availability, and unavailability of key people or vendors (vendors added in 2022), and plans are revised from the results; and backup data is tested periodically for integrity and completeness.
What evidence supports A1.3?
- Disaster recovery testingDisaster recovery or continuity test plan and results in the period
- Disaster recovery testingBackup restore test records with verification of completeness
- Disaster recovery testingPlan updates made after test findings
- Disaster recovery testingTest scenarios covering failure of a critical vendor
Where this requirement comes from
This is our own statement of SOC 2 A1.3, read from the copy we hold (issuer free complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- No recovery test performed in the period
- Restore tests confirm a file exists but not that data is complete
- Test findings never fed back into the plan
- Continuity tests assume key vendors remain available
How it maps to ISO 27001:2022
- 5.30 high Testing recovery plan procedures is the ICT readiness verification this control demands.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.