CC9.1 Mitigating risks of business disruption
Measures to reduce the risk of business disruption are identified, selected and developed. Points of focus: policies, procedures, communication plans and fallback processing are prepared in advance so the organisation can respond, limit the damage and recover from disruptive security events, with monitoring and information flows to meet objectives during those efforts; and insurance is considered to cover the financial cost of loss events.
Source: SOC 2 (2017 Trust Services Criteria), CC9.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open SOC 2 (2017 Trust Services Criteria) in the compliance library.
These are criteria, not controls: you design controls that meet them, and which criteria are in scope follows the categories your report covers (Security always; Availability, Confidentiality, Processing Integrity and Privacy only if chosen). A Type 2 report tests that the controls operated across the period, so the evidence asked for is samples across that period, not one copy.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Business impact analysis · Document repository
governing documentDocuments that govern the control
- Business continuity and disaster recovery plans covering the in-scope service · Policy repository / GRC workspace
- Cyber or business interruption insurance policy details · Policy repository / GRC workspace
First move
Common gaps auditors find
- Continuity plan does not cover the in-scope system
- No business impact analysis to set recovery priorities
- Insurance never considered
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetCC8.1 Managing changes to procedures, software, data and infrastructure · CC9.2 Assessing and managing vendor and business partner risk