# SOC 2 Business Continuity Plan and Disaster Recovery

> What a SOC 2 business continuity plan and disaster recovery must show, how the answer changes when Availability is in scope, and the evidence needed.

- Canonical: https://auditsuisse.com/soc-2-business-continuity-disaster-recovery
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-14
- Updated: 2026-11-14
- Alternates: fr → https://auditsuisse.com/fr/continuite-d-activite-et-reprise-apres-sinistre-soc-2, es → https://auditsuisse.com/es/continuidad-del-negocio-y-recuperacion-ante-desastres-soc-2

SOC 2

 The short answer

A business continuity plan sets out how the company keeps operating through a disruption. A disaster recovery plan sets out how systems and data are restored. In [SOC 2](https://auditsuisse.com/soc-2), tested recovery plans and backups are assessed mainly under the Availability category (A1.2 and A1.3). In a Security-only report, the related criteria are narrower: recovery from security incidents (CC7.5) and mitigation of business disruption risk (CC9.1).

## Key takeaways

- Decide early whether Availability is in scope. It determines how much continuity evidence the audit needs.
- A plan that has never been tested carries little weight.
- Backups are only evidence when restoration has been demonstrated.
- Do not describe availability controls in a Security-only report unless you want them read as part of your system description.

## What applies when

| Criterion | Category | Expectation |
| --- | --- | --- |
| CC7.5 | Security | Recover from identified security incidents |
| CC9.1 | Security | Identify and mitigate risks from business disruptions |
| A1.1 | Availability | Monitor and manage capacity |
| A1.2 | Availability | Environmental protections, backups and recovery infrastructure |
| A1.3 | Availability | Test recovery plan procedures |

## What a usable plan contains

1. Scope and critical services, with recovery time and recovery point objectives.
2. Roles, contact details and decision authority.
3. Scenarios: region outage, data corruption, loss of a key vendor, loss of key staff, ransomware.
4. Recovery procedures per system, with dependencies.
5. Communication plan for customers and staff.
6. Test schedule and record of results.

## Evidence auditors ask for

- The approved plan and its review date.
- Backup configuration and job success reports for the period.
- A restoration test: what was restored, when, by whom, and the outcome.
- A continuity or recovery exercise with lessons learned and follow-up.
- For cloud-hosted services, how multi-zone or multi-region design supports the objectives.

## Common gaps

- The plan exists but was not reviewed in the period.
- Backups run, but nobody has restored from them.
- A tabletop was held with no record.
- Recovery objectives promised to customers do not match what the architecture can deliver.

## Frequently asked questions

### Is a BCP required for a Security-only SOC 2?

Auditors expect business disruption risk to be considered under CC9.1. Full recovery testing is an Availability matter.

### How often should we test?

At least annually, and after major architecture changes.

### Does our cloud provider’s resilience cover us?

It covers their infrastructure. Your configuration, data and procedures remain yours. See [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure).

## Sources & further reading

AICPA 2017 Trust Services Criteria, CC7.5, CC9.1 and A1.

**Related:** [SOC 2 Trust Services Criteria explained](https://auditsuisse.com/soc-2-trust-services-criteria), [How to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2), [HIPAA incident response requirements](https://auditsuisse.com/hipaa-incident-response-requirements).

---
Source: https://auditsuisse.com/soc-2-business-continuity-disaster-recovery · This Markdown edition is generated from the same content as the HTML page.
