On this page

A SOC 2 risk assessment is a dated, management-approved record of the risks to your service commitments. Each risk is scored for likelihood and impact, tied to the controls that treat it, and given an owner and a treatment decision. Auditors test it under CC3.1 to CC3.4. The free register below comes prefilled with five worked risks for a 40-person SaaS company.

Download the register: Excel or CSV, free with no signup.

What goes in a SOC 2 risk register?

A usable register has one row per risk and three groups of columns: what the risk is (statement, category, objective, fraud flag, change trigger), how serious it is before and after controls (scores, existing controls, control rating), and what you will do about it (treatment, action, owner, status). The download holds every column.

The five rows below describe a 40-person B2B SaaS company on a public cloud. Their scores are illustrative judgements, not benchmarks. Take your own from your incident history, architecture and customer commitments.

RiskRisk statementCategoryFraud risk
R-01A phished or reused administrator password gives an attacker control of the cloud console and identity provider, exposing customer data and breaking our confidentiality commitments.TechnicalNo
R-02A known-vulnerable open-source dependency is merged and deployed, and an attacker uses it to run code in production and reach customer data.TechnicalNo
R-03A multi-hour outage at our primary cloud hosting provider takes the product offline and misses the uptime commitment in customer contracts.OperationalNo
R-04An employee with billing access issues credits or changes payout details for personal gain, causing revenue loss and false billing records.FinancialYes
R-05A configuration mistake makes a cloud storage bucket holding customer exports public, exposing customer files to anyone with the link.TechnicalNo

Every statement names a threat, the asset it touches, and a consequence for the business or a customer commitment. “Poor security” cannot be scored, assigned or tested. R-01 can.

RiskInherent (likelihood × impact)Existing controlsControl ratingResidual (likelihood × impact)TreatmentOwner
R-013 × 5 = 15AC-01, AC-02, AC-07, LG-02Strong2 × 5 = 10MitigateHead of IT
R-024 × 4 = 16CM-01, CM-02, VM-01, VM-02Partial3 × 4 = 12MitigateEngineering manager
R-033 × 4 = 12VR-01, VR-02, BC-02, BC-06Partial3 × 3 = 9AcceptCTO
R-042 × 4 = 8AC-03, AC-06, CM-06, LG-01Partial2 × 3 = 6MitigateFinance lead
R-053 × 5 = 15NS-01, VM-01, CM-01, DP-01Strong1 × 5 = 5MitigateDevOps lead

R-03 shows an accepted risk: the CTO owns it, the acceptance column records who approved it and when, and the action sets a date to revisit it. R-04 is the fraud example. The Excel file adds dropdowns, score columns that calculate themselves, an Instructions sheet and 25 blank rows with the formulas carried down. The CSV holds the headers and the five examples.

How do you score likelihood and impact?

Score each risk from 1 to 5 for likelihood and from 1 to 5 for impact, multiply them for an inherent score, then re-score both with your existing controls in place for a residual score. This is one common method, not a requirement. The Trust Services Criteria prescribe no scoring formula, so write down yours and apply it to every risk.

Linford & Company, a CPA firm, says its auditors check that risks have a likelihood and impact score, include fraud risks, and were reviewed or updated within the period. Its audit manager adds that a spreadsheet of risks and rankings falls short unless the rationale for how they were identified and ranked is written down. Put that rationale on a cover page: the scales, the banding, the risk tolerance and who took part.

ScoreLikelihoodImpact
1Not expected within five yearsNegligible, no customer effect
2Once in three to five yearsMinor, internal only
3Once in one to three yearsModerate, some customers affected or a commitment briefly missed
4About once a yearMajor, many customers affected or a contract commitment missed
5Several times a yearSevere, customer data exposed or most customers without service

This is one example scale. Rewrite the impact column in terms of your own commitments. One example banding for the product is 1 to 6 low, 8 to 12 medium and 15 to 25 high, but the line that matters is the residual score management agrees in writing to accept.

The control rating column (Strong, Partial, Weak) records your judgement of whether each control is designed, operating and evidenced. It explains why a residual score is lower than the inherent score and feeds no formula. Rate a control Strong only if you can show the auditor it ran.

Treatment has four options. Mitigate by changing or adding a control, as R-01 does with hardware security keys. Accept with a named approver, as R-03 does. Transfer the financial loss, for example with cyber liability insurance, which leaves the risk itself in place. Avoid by dropping the activity, such as cancelling a vendor integration that fails review. A customer questionnaire can also expose a missing control; the vendor security questionnaire guide shows how to answer “no” and record the risk treatment.

What do CC3.1 to CC3.4 ask the register to show?

CC3 has four criteria: CC3.1 asks for clear objectives, CC3.2 for identifying and analyzing risks, CC3.3 for considering fraud, and CC3.4 for assessing change. In our controls library they map to RA-01 (CC3.1, CC3.2), RA-02 (CC3.3) and RA-03 (CC3.4), while RA-04, the control matrix that links each risk to its controls and names an owner for every control, maps to CC5.1, CC5.2 and CC1.5.

The quotations below come from the AICPA 2017 Trust Services Criteria (revised points of focus, 2022). The points of focus are guidance, not requirements.

CC3.1: tie each risk to an objective

“The entity specifies objectives with sufficient clarity to enable the identification and assessment of risks relating to objectives.”

Start from the objectives and customer commitments you have written down and derive the risks from them. RA-01 expects a statement of the service commitments and system requirements the assessment started from, plus management sign-off on the finished assessment. The objective column does that job row by row. Linford describes an audit where IT alone ran the assessment, so only technical risks appeared because the business objectives had never been identified, and recommends involving leadership, finance and HR.

CC3.2: identify and analyze the risks

“The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managed.”

The AICPA’s points of focus for this criterion include identifying information assets, assessing how critical they are, identifying threats and vulnerabilities, assessing likelihood, and evaluating whether residual risk is appropriate, including whether to accept, reduce or share it. They are guidance, but they are why each statement above names an asset and why the register has residual columns. Put vendor risk on the same register: SOC 2 vendor management requirements covers CC9.2. Linford says an assessment whose risks have a single owner or contributor is most likely not sufficient, which is why the register has an owner column and why the cover page lists attendees. RA-01 lists a dated register with each risk’s rating, treatment, owner and linked controls as its evidence. Its common gap is a register that never changes from year to year.

CC3.3: consider fraud

“The entity considers the potential for fraud in assessing risks to the achievement of objectives.”

RA-02 asks for fraud scenarios in the register, with ratings and the controls on each: how staff, contractors or outsiders could misuse access, alter records or billing, or override controls. The common gap is a register that covers outside attackers only. The AICPA’s points of focus for this criterion cover incentives and pressures, opportunities, and rationalizations, plus threats that come from the use of IT and access to information. Linford suggests putting fraud on the meeting agenda, because people do not raise it unprompted. The fraud column makes the coverage visible, and R-04 is the worked example.

CC3.4: assess changes that affect the risks

“The entity identifies and assesses changes that could significantly impact the system of internal control.”

RA-03 asks for a risk review before a significant change, such as a new product line, a major architecture change, an acquisition or a new critical vendor, with the register updated as a result. For a Type 2 report, keep a review for each significant change made during the period, dated before or at the change, so the auditor can match changes to reviews. The AICPA’s points of focus name changes in the business model, leadership, systems and technology, vendor relationships and the external environment. Linford describes a client that adds one question to its change tickets: does this change add or remove any risks? It also reports that CC3.4 usually fails because the people who know what changed were left out of the assessment. The change trigger column records which changes send you back to each row.

List the IDs of the controls that already reduce each risk, then keep a control matrix that gives every control an owner and a cadence. That matrix is RA-04 in our controls library. The criteria below are the library’s mapping for each control, so they show where the control gets tested, not that it satisfies the criterion.

RiskLibrary controlsCriteria those controls map to
R-01AC-01, AC-02, AC-07, LG-02CC6.1, CC6.3, CC7.2, CC7.3
R-02CM-01, CM-02, VM-01, VM-02CC5.1, CC7.1, CC8.1
R-03VR-01, VR-02, BC-02, BC-06CC2.3, CC7.2, CC9.2, A1.2
R-04AC-03, AC-06, CM-06, LG-01CC2.1, CC6.2, CC6.3, CC7.2, CC8.1
R-05NS-01, VM-01, CM-01, DP-01CC5.1, CC6.1, CC6.6, CC7.1, CC8.1, C1.1

The IDs are our library’s labels. On the SOC 2 controls list, look up each control under the criteria in the right-hand column to see its evidence; the control-to-evidence matrix is an editable copy. Availability criteria (A1.1, A1.2) and confidentiality criteria (C1.1) apply only if those categories are in your scope. R-03’s continuity controls are explained in SOC 2 business continuity controls.

Before you hand the register over, check three things. Every risk has at least one control or an explicit Accept. Every control named still has an owner who works at the company, which is RA-04’s common gap. Every Mitigate row has a specific action and a date.

How often should you review the risk assessment?

Review the whole register on the cadence your policy states, annually for most companies, and update the affected rows when a significant change happens in between. The Trust Services Criteria name no review frequency. Annual is the cadence our controls library uses, and in a Type 2 audit the auditor looks for an assessment completed inside the audit period.

Run the review as a meeting with engineering, IT, finance, HR and the business, and keep minutes: who attended, which risks were re-scored, which were added, which control ratings changed and what was decided. Save a dated copy of the register each time, so this year’s version visibly differs from last year’s.

Between reviews, the change triggers matter more than the calendar. RA-03’s common gap is a major change, such as a new cloud region or an AI feature, that ships with no record that anyone considered its risks until the next annual assessment. A post-incident review that shows a control failed should also change the register.

What should you hand the auditor?

Hand over the register, the objectives and commitments it started from, a dated management approval, a record of who took part, and a dated risk review for each significant change in the period. Then walk the auditor through the two or three highest residual risks and the controls on each instead of only emailing the file.

Your CPA firm sets its own requests and sample sizes, and the criteria prescribe none. What a SOC 2 auditor asks for shows where the risk assessment sits among the other requests, and the SOC 2 controls list gives an example control for each criterion the register feeds. The free SOC 2 readiness check scores a signed-off annual risk assessment as one of its questions.

Where does the register fit in SOC 2 preparation?

The register comes first because the control matrix, the vendor program and the continuity plan each answer a risk written down here. The SOC 2 compliance checklist shows the order of work, and the readiness assessment checklist covers the rest of the preparation.

For the criteria around CC3, see the SOC 2 Trust Services Criteria. When the register is in shape, you can request ballpark quotes from matched firms through our quote form.