SOC 2 expects you to identify risks to your service commitments and system requirements, analyze them, decide how to respond, and repeat the exercise when things change. This falls under common criteria CC3.1 to CC3.4. Auditors want a dated, approved risk register that links risks to controls, and evidence that management reviewed it.
Key takeaways
- The assessment must be yours. A generic template with no company-specific risks is a common finding.
- It must consider fraud (CC3.3) and significant change (CC3.4), not only technical threats.
- Annual is the usual minimum, with updates on major changes such as a new product, cloud migration or acquisition.
- Risk mitigation decisions, including vendors and business disruption, connect to CC9.
What the criteria ask for
| Criterion | In plain terms |
|---|---|
| CC3.1 | Define objectives clearly enough to identify risks to them |
| CC3.2 | Identify and analyze risks across the entity |
| CC3.3 | Consider the potential for fraud |
| CC3.4 | Identify and assess changes that could affect controls |
A workable method
- Set the scope and objectives. Use your service commitments: security of customer data, uptime, confidentiality.
- List assets and processes. Production systems, data stores, people, key vendors.
- Identify risks. Threats and what could go wrong: credential compromise, misconfiguration, insider misuse, vendor outage, key-person loss, unauthorized code change.
- Rate likelihood and impact. A three- or five-point scale is enough. Record the reasoning.
- Decide treatment. Mitigate, accept, transfer or avoid. Name an owner.
- Map to controls. Each mitigated risk points to one or more controls.
- Approve. Management reviews and signs off. Record the meeting.
Evidence for the audit
- The risk assessment policy or methodology.
- The dated risk register with ratings, owners and treatments.
- Minutes or sign-off showing management review.
- Follow-up on treatment plans from the prior assessment.
Mistakes that lead to exceptions
- No assessment performed within the period.
- Fraud not considered.
- Risks listed with no treatment or owner.
- The register does not reflect a major change that happened in the period.
How it connects to other work
The same register can feed a HIPAA risk analysis and ISO 27001 risk treatment. See the HIPAA risk assessment guide and multi-framework control mapping.
Frequently asked questions
Does the auditor judge my risk ratings?
The auditor evaluates whether the process is designed and operating, not whether each score is “right”.
Is a vendor risk assessment part of this?
Vendor risk falls under CC9.2. See vendor management for SOC 2.
Can AI draft the register?
It can produce a starting list. The risks, ratings and decisions must reflect your company and be owned by management.
Sources & further reading
AICPA 2017 Trust Services Criteria, CC3 and CC9; COSO Internal Control framework, principles 6 to 9.
Related: SOC 2 readiness checklist, SOC 2 controls list, SOC 2 Trust Services Criteria explained, Business continuity and disaster recovery for SOC 2.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.