Platform OverviewOne evidence trail, from intake to Jira.See how it fits together
See it on your documentsA 30-minute call. Bring a vendor you are reviewing now.Book a demo
Free templateXLSXUpdated

SOC 2 report review checklist

28 checks for reading a vendor's SOC 2 report: the opinion, the period, the scope, subservice organisations, complementary user entity controls, exceptions and the bridge letter, with where to find each in the report.

For security and third-party risk reviewers who receive SOC 2 reports from vendors.

XLSX · 28 checks

Get the template

Free. Fill in your details and the download starts at once. We also email you a link to it. Opens in Excel and Google Sheets.

We use these details to send you the template and occasional updates about it. See our Privacy Policy.

What this template is for

Most SOC 2 reports are accepted after a glance at the cover page. The problems are inside: a period that ended over a year ago, a scope that leaves out the product you buy, a data centre carved out of the report, or controls your own team is expected to run.

This checklist walks through the report in the order it is written, and says for each check where in the report to look and what a gap looks like.

How to use it

  1. Check the basicsType, period, auditor and opinion. A qualified or adverse opinion changes everything that follows.
  2. Check the scopeThe system description must cover the service you buy, from the locations that serve you.
  3. Follow the dependenciesNote every subservice organisation and whether it is carved out. Carved-out providers need their own evidence.
  4. Take on your controlsList the complementary user entity controls and confirm your team actually runs them.
  5. Read the exceptionsEvery deviation in section four, with management's response, and whether it touches your use of the service.
  6. Close the gapIf the period ended more than three months ago, ask for a bridge letter.

What is inside

The full contents of the spreadsheet. The file adds columns for your answers, with drop-down lists for results and decisions.

Checklist

Result is pass, gap or not applicable. Carry each gap into your findings log.

IDAreaCheckWhere to lookWhat a gap looks like
B-1BasicsThe report is SOC 2, not SOC 1 or SOC 3Title pageA SOC 3 or a SOC 1 sent instead of a SOC 2
B-2BasicsThe report is Type II, covering a period of timeTitle page, section 1Type I only: design at a point in time, no testing of operation
B-3BasicsThe period is at least six monthsSection 1A three-month first-year period for a critical vendor
B-4BasicsThe period ended less than 12 months agoSection 1A report older than 12 months with no newer one
B-5BasicsThe auditor is a licensed CPA firm and is namedSection 1, signatureNo firm name or an unknown firm with no licence details
B-6BasicsThe opinion is unqualifiedSection 1, opinion paragraphQualified, adverse or disclaimed opinion
B-7BasicsThe report is addressed to the service organisation and restricted to its customersSection 1Use restrictions that exclude you
S-1ScopeThe system described is the product or service you buySection 3, system descriptionReport covers a different product line or only the corporate network
S-2ScopeThe Trust Services Criteria in scope match your needsSections 1 and 3Availability or confidentiality left out when you rely on them
S-3ScopeThe locations and data centres that serve you are in scopeSection 3Your region served from a site outside the report
S-4ScopeKey components (infrastructure, software, people, data, procedures) are describedSection 3A thin description with no infrastructure detail
SS-1Subservice organisationsEvery subservice organisation is listedSection 3A cloud provider you know is used but not listed
SS-2Subservice organisationsThe method (carve-out or inclusive) is stated for eachSections 1 and 3Method not stated
SS-3Subservice organisationsFor carved-out providers, you hold or can obtain their own reportsSection 3A carved-out hosting provider with no report on file
SS-4Subservice organisationsComplementary subservice organisation controls are listed and plausibleSection 3Controls assumed at the provider that it does not perform
C-1User entity controlsComplementary user entity controls are listedSection 3No CUECs listed for a service with customer-managed access
C-2User entity controlsEach control is mapped to an owner on your sideSection 3, your own recordsA CUEC nobody on your side performs
C-3User entity controlsControls you cannot perform are raised with the vendorSection 3A CUEC that assumes access you do not have
E-1Testing and exceptionsEvery control has a test and a resultSection 4Controls with no test described
E-2Testing and exceptionsAll exceptions are read, not only the summarySection 4Exceptions in access reviews or change management missed
E-3Testing and exceptionsEach exception has a management responseSection 4 or 5Exception with no response or remediation
E-4Testing and exceptionsExceptions that touch your data or service are logged as findingsSection 4A relevant exception accepted without a decision
E-5Testing and exceptionsControls not tested because they did not operate in the period are notedSection 4Incident response 'not tested' because no incident occurred, with nothing else
BL-1Bridge letterIf the period ended more than 3 months ago, a bridge letter is providedSeparate documentA six-month gap with no bridge letter
BL-2Bridge letterThe bridge letter is signed by management and covers to a recent dateBridge letterUnsigned, or dated months ago
BL-3Bridge letterIt confirms no material changes to the system or controlsBridge letterSilent on changes, or lists changes without detail
N-1Next reportThe date of the next report is knownVendor's trust centre or correspondenceNo commitment to a next period
N-2Next reportA reminder is set for the next report and bridge letterYour own recordsReport expires with nobody chasing the next

Download

XLSX · 28 checks

Ready to use it?

Free. Fill in your details and the download starts at once. We also email you a link to it. Opens in Excel and Google Sheets.

We use these details to send you the template and occasional updates about it. See our Privacy Policy.

Vendor profilesby ProcureCortex

See it in the vendors you review

39 of 39 widely used SaaS vendors list a SOC 2 report. Read what each one publishes on its own pages, with the source behind every line.

See how to get each vendor’s SOC 2 report

Run these checks on your vendors’ own documents.

Open a demo workspace with a sample vendor, its documents and its findings. Or bring your own vendor to a 30-minute call.

Procurement, compliance, security and auditOne workspace, one record of every decision

SOC 2 report review checklist: questions

Short, direct answers.

Read it in order: the opinion and period in section 1, management's assertion in section 2, the system description, subservice organisations and complementary user entity controls in section 3, and the tests and exceptions in section 4. Then decide whether each exception and each carved-out provider affects your use of the service.

Most teams accept a report whose period ended in the last 12 months, with a bridge letter covering the gap if it ended more than three months ago. A report older than that no longer tells you how controls operate today.

Under the carve-out method, the subservice organisation's controls are excluded from the report and you need separate evidence for them. Under the inclusive method, they are described and tested within the report.

Controls the vendor assumes you run, such as reviewing your own users' access. If your team does not perform them, the assurance in the report does not hold for you.