SOC 2May 19, 202610 min read

SOC 2 CC9.1: Business Disruption Risk, Continuity Plans, and Cyber Insurance

SOC 2 CC9.1 explained by an auditor: whether you need a BCP, a DR test, or cyber insurance, how CC9.1 differs from Availability, and the evidence to prepare.

On this page · 13 sections
Key takeaways
  • SOC 2 CC9.1 requires a service organization to identify, select, and develop risk mitigation activities for risks arising from potential business disruptions. It applies to every SOC 2, not only reports that include Availability.
  • The 2022 points of focus name two considerations: planning to respond to, mitigate, and recover from disruptive events, and considering insurance to offset the financial impact of loss events.
  • Neither a business continuity plan nor cyber insurance is a named requirement. Both are how almost every organization meets the criterion in practice, and the auditor will expect a documented basis if you choose otherwise.
  • Disaster recovery testing is tested most directly under A1.3 when Availability is in scope. A Security-only report still needs a credible, current continuity plan under CC9.1.

What is SOC 2 CC9.1?

SOC 2 CC9.1 is the first of two criteria in the CC9 Risk Mitigation series of the AICPA 2017 Trust Services Criteria. It requires the service organization to identify, select, and develop risk mitigation activities for risks arising from potential business disruptions. In plain terms, CC9.1 asks: if something seriously disrupts your operations, have you planned how you will keep serving customers and absorb the loss?

CC9.1 is a common criterion, so it applies to every SOC 2 examination, including Security-only reports. Its companion, CC9.2, covers risks from vendors and business partners.

CC9.1 is often confused with two other parts of the framework:

Criterion What it addresses In every SOC 2?
CC3.1 to CC3.4 Specifying objectives and identifying and assessing risks, including fraud risk and the impact of significant changes Yes
CC9.1 Selecting and developing mitigation activities for business disruption risks Yes
CC7.5 Recovering from identified security incidents Yes
A1.2 Environmental protections, backup, and recovery infrastructure Only if Availability is in scope
A1.3 Testing recovery plan procedures Only if Availability is in scope

CC3 is where disruption risks are identified and assessed. CC9.1 is where you show what you decided to do about them. The two work best when the risk register links each disruption risk to the mitigation that addresses it.

What are the CC9.1 points of focus?

The 2017 Trust Services Criteria (With Revised Points of Focus, 2022) list two points of focus under CC9.1. They illustrate how the criterion can be met and are not mandatory.

Point of focus What it means in practice Example controls
Considers Mitigation of Risks of Business Disruption Risk management includes planned policies, procedures, communications, and alternative processing solutions to respond to, mitigate, and recover from security events that disrupt operations, along with the monitoring and information needed to do so Business continuity plan, business impact analysis, incident communication plan, multi-region or backup processing design
Considers the Use of Insurance to Mitigate Financial Impact Risks Risk management considers insurance to offset the financial impact of loss events that could otherwise impair the organization's ability to meet its objectives Annual review of cyber and business interruption insurance coverage against identified risks

The verb in both titles is "considers." That wording matters for how auditors test the insurance point of focus in particular, as explained below.

Does SOC 2 require a business continuity plan?

SOC 2 does not use the words "business continuity plan" as a requirement. CC9.1 requires that you develop mitigation activities for business disruption risks, and the point of focus describes planned policies, procedures, communications, and alternative processing solutions. A documented business continuity plan is the most direct way to show that, which is why nearly every SOC 2 control set includes one.

What an auditor looks for in the plan is not length. It is whether the plan is credible for your actual operations. A strong plan for a SaaS company usually covers:

  • Critical services and dependencies. Which customer-facing services matter most, and which systems, vendors, and people they depend on.
  • Recovery objectives. Recovery time objective (RTO) and recovery point objective (RPO) for critical services, and whether current architecture can meet them.
  • Scenarios. Loss of a cloud region, loss of a critical vendor, ransomware or destructive attack, loss of key personnel, and loss of office or remote work infrastructure where relevant.
  • Roles and communication. Who decides to invoke the plan, who communicates with customers, and how.
  • Review and approval. A named owner, a review at least annually or after significant change, and management approval.

A plan written two years ago that names people who have since left, or describes infrastructure you no longer run, is one of the most common CC9.1 findings.

Does SOC 2 require cyber insurance?

SOC 2 does not require cyber insurance. The CC9.1 point of focus says the organization considers the use of insurance to offset the financial impact of loss events. The criterion asks for a decision, not a purchase.

In practice, auditors generally look for evidence that management considered insurance as part of risk mitigation. That evidence can take several forms:

  • A current cyber liability or business interruption policy, with the declarations page showing coverage and the policy period.
  • A documented risk treatment decision explaining why insurance was not purchased or was limited, approved by management.
  • Minutes or records of an annual review comparing coverage to identified risks.

Many service organizations carry cyber insurance anyway because enterprise customer contracts require it. If you do, make sure the policy period covers the SOC 2 review period without a lapse, and that someone actually reviews whether the coverage still fits your risks. An expired policy discovered during fieldwork is an easy exception to avoid.

Does SOC 2 require disaster recovery testing?

Disaster recovery testing is required most directly by A1.3, which is part of the Availability category. If Availability is in scope, the auditor will test that recovery plan procedures, including backup restoration, were tested during the period. If your report covers Security only, CC9.1 does not explicitly require a DR test.

That said, a continuity plan that has never been exercised is hard to defend as an effective mitigation. Two lightweight activities give a Security-only report much more credibility:

  1. A tabletop exercise. Walk the plan through a realistic scenario with the people named in it, and record the gaps found and the actions assigned.
  2. A backup restoration test. Restore a backup to a non-production environment and confirm the data is complete and usable. CC7.5, which covers recovery from security incidents, is often supported by the same evidence.

Document both. A tabletop that happened but left no record cannot be tested.

How do auditors test CC9.1?

Auditors test CC9.1 by inspecting the documents that show mitigation was developed, and by checking that those documents were maintained during the period. Typical procedures in a SOC 2 Type 2 include:

  • Inspecting the risk assessment to confirm business disruption risks were identified, and tracing them to mitigation activities.
  • Inspecting the business continuity plan for content, approval, and evidence of review during or shortly before the period.
  • Inspecting the business impact analysis, if one exists, to see how critical services and recovery objectives were set.
  • Inspecting insurance evidence, such as the declarations page and policy period, or a documented decision not to insure.
  • Inspecting exercise records, such as tabletop or restoration test reports, and following up on the actions they produced.

Most CC9.1 controls operate annually, so the auditor will often test the single instance that falls within the period. If your annual BCP review happened one month before the review period started and the next one is due one month after it ends, the auditor may have nothing within the period to test. Schedule annual reviews so at least one occurrence lands inside the period.

What evidence do auditors request for CC9.1?

Evidence What it demonstrates
Risk assessment or risk register with disruption risks and linked treatments Disruption risks were identified and mitigation selected
Business continuity plan with version history and management approval Planned policies, procedures, and communications exist and are maintained
Business impact analysis with RTO and RPO for critical services Mitigation is based on an understanding of impact
Architecture documentation for redundancy, such as multi-zone or multi-region design Alternative processing solutions exist
Tabletop exercise report or backup restoration test records The plan was exercised and gaps were addressed
Cyber insurance declarations page or documented insurance decision Insurance was considered to offset financial impact
Review of the cloud provider's SOC 2 report, including its continuity controls Dependence on a subservice organization is monitored

Example: disruption risks and mitigations in a risk register

The following illustrative entries show how disruption risks and their mitigations can be linked in a way an auditor can test. This is an example format, not a template you must follow.

Disruption risk Likelihood and impact (illustrative) Mitigation activities Owner
Loss of the primary cloud region Low likelihood, high impact Multi-zone deployment; cross-region backups; documented regional failover runbook; customer communication template Head of Infrastructure
Ransomware or destructive attack on production Medium likelihood, high impact Immutable backups in a separate account; restoration test; incident response plan; cyber insurance Security Lead
Outage at a critical third-party service, such as the payment or email provider Medium likelihood, medium impact Vendor status monitoring; documented degraded-mode procedure; contractual SLAs reviewed under CC9.2 Head of Engineering
Loss of key personnel with sole knowledge of a system Medium likelihood, medium impact Runbooks for critical systems; cross-training; shared on-call rotation CTO
Financial loss from a data breach Low likelihood, high impact Cyber liability insurance reviewed annually against breach cost estimates CFO

Notice that one mitigation can serve several risks, and several criteria. Immutable backups support CC9.1, CC7.5, and A1.2. Describing them once and mapping them consistently keeps your report coherent.

What are the most common CC9.1 exceptions?

1. A stale continuity plan

The plan was approved once and never reviewed, or it names former employees and retired systems. Review it at least annually and after significant changes.

2. No evidence of review within the period

The annual review happened, but outside the review period. Align the review calendar with your SOC 2 period.

3. Disruption risks missing from the risk assessment

The risk register covers security threats but not disruption, so the auditor cannot trace CC9.1 mitigation to an identified risk.

4. Insurance lapsed or never considered

The policy expired mid-period, or there is no record that insurance was ever discussed. Either is avoidable with a calendar reminder and a short annual record.

5. The plan ignores the cloud provider

The plan assumes the hosting provider never fails. A single-region architecture with no documented response to a regional outage is a gap in alternative processing planning.

6. Exercises with no follow-through

A tabletop exercise identified gaps, but none of the resulting actions were tracked or completed.

How does CC9.1 map to ISO 27001:2022?

The table shows close ISO/IEC 27001:2022 equivalents. It is a practitioner mapping, not an official crosswalk.

CC9.1 theme Closest ISO 27001:2022 equivalents
Risk treatment decisions Clause 6.1.3 Information security risk treatment
Information security during disruption A.5.29 Information security during disruption
ICT readiness for business continuity A.5.30 ICT readiness for business continuity
Backups A.8.13 Information backup
Redundancy and alternative processing A.8.14 Redundancy of information processing facilities

ISO 27001 certified organizations usually have a continuity plan already. The common gap when adding SOC 2 is the insurance consideration, which ISO 27001 does not specifically call for, and evidence that the plan was reviewed within the SOC 2 period.

How should you prepare for CC9.1?

  1. Add disruption risks to your risk register. Cover infrastructure, vendors, people, and destructive attacks, and link each to its mitigation.
  2. Refresh the continuity plan. Confirm owners, contacts, systems, and recovery objectives are current, then have management approve it.
  3. Run and record one exercise. A tabletop or a backup restoration test, with gaps tracked to closure.
  4. Record the insurance decision. Keep the declarations page or a documented decision, and check the policy period covers your SOC 2 period.
  5. Align the calendar. Make sure annual CC9.1 activities fall inside the review period.

A SOC 2 readiness assessment from Ledger Audits reviews your risk register, continuity plan, and insurance evidence together and checks that they line up with the controls described in your report.

Frequently asked questions

What does SOC 2 CC9.1 require?

SOC 2 CC9.1 requires a service organization to identify, select, and develop risk mitigation activities for risks arising from potential business disruptions. Its points of focus describe planning to respond to, mitigate, and recover from disruptive events, and considering insurance to offset the financial impact of loss events.

Is cyber insurance required for SOC 2?

Cyber insurance is not required for SOC 2. The CC9.1 point of focus asks the organization to consider insurance as a way to offset financial impact. Auditors typically look for either a current policy or a documented management decision explaining why insurance was not purchased.

Is a business continuity plan required for SOC 2?

A business continuity plan is not named as a requirement, but CC9.1 requires mitigation activities for business disruption risks, and a documented, approved, and current continuity plan is how nearly every organization demonstrates that. Auditors test whether the plan is credible and maintained during the period.

Do I need disaster recovery testing for a Security-only SOC 2?

Disaster recovery testing is required most directly under A1.3 when Availability is in scope. A Security-only SOC 2 does not explicitly require it under CC9.1. However, a tabletop exercise or a backup restoration test makes the continuity plan far more credible and also supports CC7.5 on incident recovery.

What is the difference between CC9.1 and CC9.2?

CC9.1 covers risk mitigation for potential business disruptions, such as outages, attacks, and loss of key people. CC9.2 covers assessing and managing risks associated with vendors and business partners. A critical vendor outage touches both: CC9.2 governs how the vendor is assessed and monitored, and CC9.1 governs how you would continue operating if it failed.

What is the difference between CC9.1 and the Availability criteria?

CC9.1 is a common criterion included in every SOC 2 and focuses on planning mitigation for disruption risks. The Availability criteria, A1.1 to A1.3, apply only when Availability is in scope and address capacity, environmental protections, backup and recovery infrastructure, and testing of recovery procedures.


Get independent eyes on it before your auditor or buyer does.

Ledger Audits provides readiness and internal audit work only. We never issue SOC 2 reports or ISO certificates, which keeps our review independent of your examination.

Book a discovery call
Get started

Book a discovery call

Tell us where you are in your SOC 2 or ISO 27001 journey and what you need to pass. We will tell you, honestly, what it takes.

01A 30‑minute call with a lead auditor, not a sales rep.
02An honest read on your framework, scope, and timeline.
03A fixed, written figure within one business day.

Prefer email? [email protected]

Discovery requestConfidential

We reply within one business day. Your details stay confidential.