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
- Check the basicsType, period, auditor and opinion. A qualified or adverse opinion changes everything that follows.
- Check the scopeThe system description must cover the service you buy, from the locations that serve you.
- Follow the dependenciesNote every subservice organisation and whether it is carved out. Carved-out providers need their own evidence.
- Take on your controlsList the complementary user entity controls and confirm your team actually runs them.
- Read the exceptionsEvery deviation in section four, with management's response, and whether it touches your use of the service.
- 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.
| ID | Area | Check | Where to look | What a gap looks like |
|---|---|---|---|---|
| B-1 | Basics | The report is SOC 2, not SOC 1 or SOC 3 | Title page | A SOC 3 or a SOC 1 sent instead of a SOC 2 |
| B-2 | Basics | The report is Type II, covering a period of time | Title page, section 1 | Type I only: design at a point in time, no testing of operation |
| B-3 | Basics | The period is at least six months | Section 1 | A three-month first-year period for a critical vendor |
| B-4 | Basics | The period ended less than 12 months ago | Section 1 | A report older than 12 months with no newer one |
| B-5 | Basics | The auditor is a licensed CPA firm and is named | Section 1, signature | No firm name or an unknown firm with no licence details |
| B-6 | Basics | The opinion is unqualified | Section 1, opinion paragraph | Qualified, adverse or disclaimed opinion |
| B-7 | Basics | The report is addressed to the service organisation and restricted to its customers | Section 1 | Use restrictions that exclude you |
| S-1 | Scope | The system described is the product or service you buy | Section 3, system description | Report covers a different product line or only the corporate network |
| S-2 | Scope | The Trust Services Criteria in scope match your needs | Sections 1 and 3 | Availability or confidentiality left out when you rely on them |
| S-3 | Scope | The locations and data centres that serve you are in scope | Section 3 | Your region served from a site outside the report |
| S-4 | Scope | Key components (infrastructure, software, people, data, procedures) are described | Section 3 | A thin description with no infrastructure detail |
| SS-1 | Subservice organisations | Every subservice organisation is listed | Section 3 | A cloud provider you know is used but not listed |
| SS-2 | Subservice organisations | The method (carve-out or inclusive) is stated for each | Sections 1 and 3 | Method not stated |
| SS-3 | Subservice organisations | For carved-out providers, you hold or can obtain their own reports | Section 3 | A carved-out hosting provider with no report on file |
| SS-4 | Subservice organisations | Complementary subservice organisation controls are listed and plausible | Section 3 | Controls assumed at the provider that it does not perform |
| C-1 | User entity controls | Complementary user entity controls are listed | Section 3 | No CUECs listed for a service with customer-managed access |
| C-2 | User entity controls | Each control is mapped to an owner on your side | Section 3, your own records | A CUEC nobody on your side performs |
| C-3 | User entity controls | Controls you cannot perform are raised with the vendor | Section 3 | A CUEC that assumes access you do not have |
| E-1 | Testing and exceptions | Every control has a test and a result | Section 4 | Controls with no test described |
| E-2 | Testing and exceptions | All exceptions are read, not only the summary | Section 4 | Exceptions in access reviews or change management missed |
| E-3 | Testing and exceptions | Each exception has a management response | Section 4 or 5 | Exception with no response or remediation |
| E-4 | Testing and exceptions | Exceptions that touch your data or service are logged as findings | Section 4 | A relevant exception accepted without a decision |
| E-5 | Testing and exceptions | Controls not tested because they did not operate in the period are noted | Section 4 | Incident response 'not tested' because no incident occurred, with nothing else |
| BL-1 | Bridge letter | If the period ended more than 3 months ago, a bridge letter is provided | Separate document | A six-month gap with no bridge letter |
| BL-2 | Bridge letter | The bridge letter is signed by management and covers to a recent date | Bridge letter | Unsigned, or dated months ago |
| BL-3 | Bridge letter | It confirms no material changes to the system or controls | Bridge letter | Silent on changes, or lists changes without detail |
| N-1 | Next report | The date of the next report is known | Vendor's trust centre or correspondence | No commitment to a next period |
| N-2 | Next report | A reminder is set for the next report and bridge letter | Your own records | Report expires with nobody chasing the next |
Download
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.