Building a Risk Register for SOC 2: What to Include
A practical guide to creating and maintaining a risk register that satisfies SOC 2 CC3 requirements without over-engineering the process.
Why the Risk Register Matters for SOC 2
The AICPA's Trust Services Criteria CC3 (Risk Assessment) requires that you identify, analyze, and respond to risks that could affect the achievement of your service commitments. Your risk register is the primary evidence artifact for this control family.
Auditors don't expect a consulting-grade risk management framework. They expect a documented, regularly-reviewed register showing that your team thinks systematically about what could go wrong.
The Minimum Viable Risk Register
Each risk entry should capture:
| Field | Description |
| Risk ID | Unique identifier (e.g., R-001) |
| Risk description | What could go wrong |
| Affected Trust Criteria | Which CC/A/C criteria this risk impacts |
| Inherent likelihood | 1–5 scale before controls |
| Inherent impact | 1–5 scale before controls |
| Existing controls | What currently mitigates this risk |
| Residual likelihood | 1–5 after controls |
| Residual impact | 1–5 after controls |
| Risk owner | Who is responsible |
| Risk response | Accept / Mitigate / Transfer / Avoid |
| Review date | When this entry was last reviewed |
Risk Categories to Cover
Technology risks
- Unauthorized access to production systems
- Data breach via compromised credentials
- Infrastructure failure / availability event
- Insecure third-party integrations
- Key person dependency (single engineer has unique access)
- Misconfigured change to production
- Failure to conduct access reviews
- Critical SaaS vendor outage
- Vendor data breach exposing your customer data
- Vendor discontinues product without warning
- Audit finding requiring remediation
- Regulatory change requiring control updates
- Customer contract breach due to availability SLA failure
Risk Scoring
Use a simple 5×5 matrix. Risks with a residual score of 15 or above (high likelihood × high impact) should have active mitigation plans or documented acceptance.
Likelihood scale:
1 = Rare (< once per 5 years)
2 = Unlikely (once per 2–5 years)
3 = Possible (once per 1–2 years)
4 = Likely (once per year)
5 = Almost certain (multiple times per year)Impact scale:
1 = Negligible (no customer impact)
3 = Significant (degraded service, limited data exposure)
5 = Critical (full outage, major breach)Review Cadence
CC3 requires risk assessment to occur at least annually, and following significant changes. In practice, review your register:
- Quarterly — Update scores on risks that have changed
- On major product launches — Add risks introduced by new infrastructure
- On security incidents — Add or update risks illuminated by the event
- Pre-audit — Verify all entries are current and owners confirmed
SecureSpect's Risk module stores your register, tracks review history, and links risks to the specific controls that mitigate them — giving auditors a traceable view from risk identification to control execution.