SOC 2 ControlsRisk RegisterCC3Risk ManagementSOC 2

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.

SecureSpect Team··8 min read

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:

FieldDescription
|---|---|
Risk IDUnique identifier (e.g., R-001)
Risk descriptionWhat could go wrong
Affected Trust CriteriaWhich CC/A/C criteria this risk impacts
Inherent likelihood1–5 scale before controls
Inherent impact1–5 scale before controls
Existing controlsWhat currently mitigates this risk
Residual likelihood1–5 after controls
Residual impact1–5 after controls
Risk ownerWho is responsible
Risk responseAccept / Mitigate / Transfer / Avoid
Review dateWhen this entry was last reviewed
A 20–50 entry register is typical for a growth-stage SaaS company. Fewer than 20 suggests under-coverage; more than 100 often indicates noise that obscures real risks.

Risk Categories to Cover

Technology risks

  • Unauthorized access to production systems
  • Data breach via compromised credentials
  • Infrastructure failure / availability event
  • Insecure third-party integrations
Operational risks
  • Key person dependency (single engineer has unique access)
  • Misconfigured change to production
  • Failure to conduct access reviews
Vendor risks
  • Critical SaaS vendor outage
  • Vendor data breach exposing your customer data
  • Vendor discontinues product without warning
Compliance risks
  • 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.

Automate your SOC 2 evidence collection

Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

Start Free →More Articles