# SOC 2 Risk Assessment with AI: Template and Worked Example

> A SOC 2 risk assessment template as CSV, prompts to generate candidate risks and the decisions only management can make. CPA firm audit from $4,400.

- Canonical: https://auditsuisse.com/soc-2-risk-assessment-with-ai
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/evaluation-des-risques-soc-2-avec-l-ia, es → https://auditsuisse.com/es/evaluacion-de-riesgos-soc-2-con-ia

SOC 2 with AI

 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)](https://auditsuisse.com/kit/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.

| Column | What to enter |
| --- | --- |
| ID | A reference, starting at R-001 |
| Risk | What could go wrong, in one sentence |
| Asset or process | The system, data or process affected |
| Cause or threat | Why it could happen |
| Likelihood (1-5) | Management’s rating |
| Impact (1-5) | Management’s rating |
| Score (likelihood x impact) | The two ratings multiplied |
| Existing controls | What already reduces the risk |
| Treatment (mitigate / accept / transfer / avoid) | The response management chose |
| Decision made by | The person in management who decided |
| Owner | Who carries out the treatment |
| Target date | When the treatment is due |
| Related criteria series | CC1 to CC9: where the controls sit |
| Last reviewed | The 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](https://auditsuisse.com/soc-2-risk-assessment).

## 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.

| Risk | Asset or process | Cause or threat | Likelihood | Impact | Score | Existing controls | Treatment | Series |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| A leaver keeps access to production after the last day | Production cloud account | Offboarding steps are manual and depend on one person | 3 | 4 | 12 | Offboarding checklist; quarterly access review | mitigate | CC6 |
| A change reaches production without review | Deployment pipeline | Branch protection can be bypassed by administrators | 2 | 4 | 8 | Pull request reviews; deployment log | mitigate | CC8 |
| A key vendor has an outage or a breach | Hosting and identity providers | Dependence on a small number of vendors | 2 | 5 | 10 | Vendor list; annual review of vendor reports | accept | CC9 |

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](https://auditsuisse.com/vendor-management-for-soc-2-compliance).

## 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](https://auditsuisse.com/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](https://auditsuisse.com/soc-2-gap-assessment-with-ai) 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](https://auditsuisse.com/soc-2-policies-with-ai). [SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai) shows the whole workflow, and the [Zero-Platform SOC 2 Audit](https://auditsuisse.com/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.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| List candidate risks | Describes the systems, data and vendors; adds the risks it knows | Suggests candidates and asks questions | No role |
| Decide which risks are in | Management decides and can say why | No role | No role |
| Score likelihood and impact | Management rates each risk and records the reasoning | Points out scores that do not add up | Evaluates whether the process is designed and operating, not whether each score is right |
| Treat, accept, assign owners | Management decides, names owners and approves the register | Drafts the wording of decisions already made | Inspects the dated, approved register and the record of management’s review |
| Link risks to controls | Maps each mitigated risk to controls it operates | Lists rows with no control named | Tests the controls |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## 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](https://auditsuisse.com/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)](https://www.aicpa-cima.com/resources/download/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](https://auditsuisse.com/soc-2-risk-assessment), [SOC 2 controls list by Trust Services Criteria](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria), [SOC 2 readiness checklist](https://auditsuisse.com/soc-2-readiness-checklist-2026).

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

---
Source: https://auditsuisse.com/soc-2-risk-assessment-with-ai · This Markdown edition is generated from the same content as the HTML page.
