SOC 2 with AI

SOC 2 Risk Assessment with AI: Template and Worked Example

The short answer

A SOC 2 risk assessment template is a risk register: one row per risk, with its cause, a likelihood and an impact score, the existing controls, the treatment, an owner and the person in management who decided. The CSV template below has those columns and three marked examples. An AI assistant can suggest candidate risks. Which risks are in, how they score, how each is treated and who accepts what are management’s decisions.

Key takeaways

  • The register must be yours. A generic list with no company-specific risks is a common finding.
  • Use the assistant for breadth: candidate risks, missing categories, rows that do not add up.
  • Scores, treatment, acceptance and owners are decided by named people in management, and the register records who.
  • The template is a CSV. It works as a spreadsheet with no AI at all.

What is in a SOC 2 risk register template?

Download the SOC 2 risk register template (CSV). It works as a spreadsheet with no AI at all. Each row is one risk.

Columns of the SOC 2 risk register template and what to enter in each.
ColumnWhat to enter
IDA reference, starting at R-001
RiskWhat could go wrong, in one sentence
Asset or processThe system, data or process affected
Cause or threatWhy it could happen
Likelihood (1-5)Management’s rating
Impact (1-5)Management’s rating
Score (likelihood x impact)The two ratings multiplied
Existing controlsWhat already reduces the risk
Treatment (mitigate / accept / transfer / avoid)The response management chose
Decision made byThe person in management who decided
OwnerWho carries out the treatment
Target dateWhen the treatment is due
Related criteria seriesCC1 to CC9: where the controls sit
Last reviewedThe date of the latest review

The file opens with three rows marked “EXAMPLE” and “(delete)”. Remove them and start at R-001. The template uses a five-point scale; a three-point scale also works. Under the risk assessment series (CC3), an auditor expects a dated, approved register that links risks to controls, and evidence that management reviewed it. See SOC 2 risk assessment: what auditors expect.

What does a worked SOC 2 risk register look like?

These are the three example rows of the template, without the columns that hold names and dates. The values illustrate the format. Your own risks and scores will differ.

Worked example: three rows of a SOC 2 risk register.
RiskAsset or processCause or threatLikelihoodImpactScoreExisting controlsTreatmentSeries
A leaver keeps access to production after the last dayProduction cloud accountOffboarding steps are manual and depend on one person3412Offboarding checklist; quarterly access reviewmitigateCC6
A change reaches production without reviewDeployment pipelineBranch protection can be bypassed by administrators248Pull request reviews; deployment logmitigateCC8
A key vendor has an outage or a breachHosting and identity providersDependence on a small number of vendors2510Vendor list; annual review of vendor reportsacceptCC9

Read the first row as a chain of decisions. Management judged that a leaver keeping access is possible (3) and serious (4), which gives 12. The existing controls are named, so each can be traced to a record: the checklist and the access review. The treatment is “mitigate”, so the row needs an owner, a target date and a change to make, for example tying account removal to the HR termination record.

In the third row management accepts the risk. That is a legitimate decision, and “Decision made by” records who made it. The controls behind that row are covered in vendor management for SOC 2.

What prompts generate candidate risks for a SOC 2 risk assessment?

Use the assistant for breadth, then cut. Start from your scope (see how to scope systems for SOC 2). Each prompt keeps scoring and treatment out of the assistant’s hands.

Candidate risks from your own system

Help me list candidate risks for a SOC 2 risk assessment. Ask me, one question at a time, about our product, the systems and data behind it, who has access, our key vendors and what changed this year. Then propose candidate risks, each with the asset or process and the cause or threat. Do not score them or choose a treatment: management does that. Mark every guess as [ASSUMPTION].
List anything you assumed that I need to verify.

What is missing from the list

Our draft list of risks is pasted below. Ask me what you need to know about how we work today. Then tell me which kinds of risk are missing or thin: fraud or misuse by an insider, a major change such as a new product or a cloud migration, a vendor outage or breach, loss of a key person, business disruption. Suggest candidates only. Mark every guess as [ASSUMPTION].
List anything you assumed that I need to verify.

Review the register before management approves it

Review the risk register pasted below. Change no score and no decision. Ask me about any row you cannot follow. Then list: risks with no owner or no treatment, risks marked "mitigate" with no existing control or target date, scores that do not equal likelihood times impact, and rows where the cause does not fit the risk. Mark every guess as [ASSUMPTION].
List anything you assumed that I need to verify.

Fraud and major change are in the second prompt because the risk assessment series expects both to be considered. A gap assessment is another source of candidates: every criterion you scored low points to something that could go wrong.

Which risk assessment decisions can only management make?

An assistant produces a list. A risk assessment is a set of decisions, and the auditor looks for evidence that management made them.

  • Which risks are in. Management keeps, merges or drops each candidate and can say why.
  • Scoring. Likelihood and impact are management’s judgment. Record the reasoning.
  • Treatment. Mitigate, accept, transfer or avoid.
  • Acceptance. A named person with the authority to do so accepts the risk.
  • Owners. Each treated risk has one owner and a target date.
  • Approval. Management reviews the register and signs off. Record the meeting.

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read. The same holds for a register. The auditor evaluates whether the process is designed and operating, not whether each score is “right”.

Each risk marked “mitigate” points to one or more controls, and those controls need written rules: see SOC 2 policies with AI. SOC 2 with AI shows the whole workflow, and the Zero-Platform SOC 2 Audit is the examination that follows it: AI-guided preparation, CPA-performed audit.

Who does what

Who does what in a SOC 2 risk assessment prepared with AI.
TaskYour team (with or without AI)Your AI assistantThe auditor
List candidate risksDescribes the systems, data and vendors; adds the risks it knowsSuggests candidates and asks questionsNo role
Decide which risks are inManagement decides and can say whyNo roleNo role
Score likelihood and impactManagement rates each risk and records the reasoningPoints out scores that do not add upEvaluates whether the process is designed and operating, not whether each score is right
Treat, accept, assign ownersManagement decides, names owners and approves the registerDrafts the wording of decisions already madeInspects the dated, approved register and the record of management’s review
Link risks to controlsMaps each mitigated risk to controls it operatesLists rows with no control namedTests the controls

Frequently asked questions

Can AI do our SOC 2 risk assessment?

It can produce a starting list and check a register for missing fields. The risks, ratings and decisions must reflect your company and be owned by management.

Will the auditor tell us which risks to include?

No. Auditsuisse explains the criteria and sends its evidence request list once engaged. It does not choose a client’s risks, scores, treatments or controls: those are management decisions. If you want hands-on help, that is a separate provider.

Do we need risk management software?

No. A spreadsheet is enough. What matters is that the register is dated, approved by management, linked to controls and reviewed. What auditors accept from AI explains how documents prepared with an assistant are examined.

Sources & further reading

AICPA, 2017 Trust Services Criteria (with revised points of focus, 2022), series CC3 and CC9; SSAE No. 18, AT-C sections 105 and 205.

Related: SOC 2 risk assessment: what auditors expect, SOC 2 controls list by Trust Services Criteria, SOC 2 readiness checklist.

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

Sébastien Ruosch

Work with a licensed CPA firm

Auditsuisse Assurance NA PC is a licensed US CPA firm, enrolled in the AICPA Peer Review Program and authorized to perform SOC 2 examinations and issue SOC 2 reports. You prepare; we examine your evidence. See the Zero-Platform SOC 2 audit or book a scoping call.

Back to top ↑