Skip to main content
COOKIE NOTICECOOKIE CHOICE

We use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI). Strictly necessary cookies keep the site working. See our Cookie Policy for what each one does and how to opt out.

We’d like to use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI), and none of them is set unless you accept. Cookie Policy

Learn · SOC Reports

How to Read a SOC 2 Report

A SOC 2 report is the deliverable of an independent CPA firm's examination of a service organization's controls against the AICPA Trust Services Criteria — typically 60–150+ pages in five sections. Here is what each section contains, how Type 1 and Type 2 differ on the page, and what to check before you rely on one.

There is no SOC 2 certificate. SOC 2 is an attestation examination under the AICPA’s standards — the deliverable is a report carrying an opinion, not a certification. Full reports are restricted-use documents, typically shared under NDA. The general-use public summary is SOC 3.

5sections in every SOC 2 report
3–12 motypical Type 2 review period
1,000+audits delivered by TCSA

Plain-English explainer · Applies to Type 1 & Type 2 · Last reviewed July 2026

A SOC 2 report is the deliverable of an independent CPA firm’s examination of a service organization’s controls against the AICPA Trust Services Criteria — typically 60–150+ pages organized into five sections: the auditor’s opinion, management’s assertion, the system description, the controls-and-tests matrix, and an optional section of other information. It is an attestation, performed by a licensed CPA firm under the AICPA’s attestation standards (SSAE, codified at AT-C sections 105 and 205) — not a certification. No certificate exists. “SOC 2 certified” is marketing shorthand for “we have a report.” Only licensed CPA firms can issue the opinion inside one. If the framework itself is new to you, start with what SOC 2 is. This page is about the document. One access note before the anatomy: SOC 2 reports are restricted-use — intended for the service organization, its customers, and other specified parties — so vendors share them under NDA rather than publishing them. The general-use summary designed for public distribution is SOC 3.

Key Takeaways

  • Every SOC 2 report has the same five-part skeleton: the auditor’s opinion (Section 1), management’s assertion (Section 2), the system description (Section 3), the controls-and-tests matrix (Section 4), and optional unaudited other information (Section 5).
  • Read Section 1 first. The opinion — unmodified, qualified, adverse, or disclaimed — frames everything else in the document.
  • Type 1 covers control design as of a single date. Type 2 adds operating effectiveness over a review period, typically 3–12 months, with the test results in Section 4.
  • Section 3 sets the boundary: confirm the system described is the product you actually buy, then treat the CUECs and carved-out subservice organizations as your own homework.
  • SOC 2 is an attestation, not a certification — there is no certificate, reports are restricted-use and shared under NDA, and SOC 3 is the public version.
Report Anatomy

The Five Sections at a Glance

The binding order is standard, but experienced reviewers rarely read front to back: they read the opinion, check the boundary, then go hunting for exceptions. Here is the map before the walkthrough.

SectionWritten byRead it for
Section 1
Independent Service Auditor’s Report
The CPA firmThe opinion — unmodified, qualified, adverse, or disclaimed — plus the scope, the period, and the inherent limitations.
Section 2
Management’s Assertion
Service-organization managementManagement’s own written claim that the description is fairly presented and controls were suitably designed (and, in Type 2, operating effectively).
Section 3
Description of the System
Management, per DC section 200The boundary of the assurance: services, commitments, system components, CUECs, and subservice organizations.
Section 4
Trust Services Criteria, Controls & Tests of Controls
Controls by management, tests and results by the auditorThe matrix: every criterion, every control, how it was tested, and every exception the auditor found.
Section 5
Other Information (optional)
Management — unauditedManagement’s responses to exceptions and future plans. Context, not assurance — the auditor performed no procedures on it.

Page counts vary with the number of trust services categories in scope and the size of the control set, but Section 4 is almost always more than half the document — which is why the short sections at the front punch far above their page count.

Section by Section

An Annotated Walkthrough

What each section is for, who wrote it, and what a careful reader takes from it. To click through a full illustrative report, open the annotated SOC 2 report example.

  1. 1

    Independent Service Auditor’s Report

    The report opens with the auditor’s letter — a few pages that carry all of the assurance. It states the scope (the system, the period, the applicable trust services criteria), each party’s responsibilities (management prepared the description and assertion, and the auditor examined them), the inherent limitations of any system of controls, and — the part to read twice — the opinion paragraph. Opinions come in four forms: unmodified (clean), qualified (fair except for specific described matters), adverse (the description is not fairly presented or controls broadly failed), and a disclaimer (the auditor could not obtain enough evidence to opine). We unpack what triggers each in SOC 2 opinions and exceptions. This is the first thing experienced reviewers read: three minutes here tells you whether the remaining hundred pages deserve two hours or ten.

  2. 2

    Management’s Assertion

    A SOC 2 is an assertion-based examination: the auditor does not examine the system in the abstract, it examines management’s written claims about the system. Section 2 is that claim — management asserts the description is fairly presented and that controls were suitably designed (and, for Type 2, operated effectively over the period) to meet the applicable criteria. It reads like boilerplate, and mostly is — but it puts management’s name, not just the auditor’s, behind the report. Quick check: the system name, period, and categories in the assertion should match the opinion and the description exactly. Mismatches are drafting errors at best.

  3. 3

    Description of the System

    The longest prose section, prepared by management under the AICPA Description Criteria (DC section 200 — specific to SOC 2, while SOC 1’s description requirements live in AT-C 320 instead). A conforming description covers the services provided, plus the principal service commitments and system requirements — what the organization promises customers and what the system must do to deliver it. It covers the system’s components across five dimensions (infrastructure, software, people, procedures, and data), relevant incidents, and which trust services categories are in scope. It covers complementary user entity controls (CUECs) — the controls the report assumes you operate. And it covers subservice organizations and whether they are treated under the carve-out or inclusive method, and, in Type 2 reports, significant changes to the system during the period. Read it for the boundary above all else: a vendor may operate ten products, and the description may cover one. If the product, environment, or entity you buy from sits outside the described system, the opinion — however clean — does not cover your risk.

  4. 4

    Trust Services Criteria, Related Controls & Tests of Controls

    The heart of the report and usually more than half its page count: a matrix pairing each applicable criterion with the organization’s controls, the auditor’s tests, and the results. Controls are evaluated against the Trust Services Criteria (the 2017 criteria, points of focus revised in 2022), organized into five categories: Security — mandatory in every SOC 2, expressed as the common criteria CC1–CC9 and aligned to the 17 COSO internal-control principles — plus optional Availability, Processing Integrity, Confidentiality, and Privacy. In a Type 2, each row shows the test procedures (inquiry, observation, inspection of evidence, reperformance) and a result: “no exceptions noted,” or a description of the exception found. A Type 1’s Section 4 describes control design only — no tests of operating effectiveness, no results. Exceptions are not automatic failures: read each one against the opinion (did it drive a qualification?) and against management’s response.

  5. 5

    Other Information Provided by Management (optional)

    Some reports end with an unaudited appendix: most commonly management’s responses to the exceptions in Section 4, remediation status, and planned system or control changes. The auditor performs no procedures on this section, and it sits outside the opinion. It is still worth reading — a thoughtful, specific exception response says a lot about a control environment — but weigh it as management’s unaudited words, nothing more.

Type 1 vs Type 2

Telling Them Apart on the Page

The full comparison lives in our Type 1 vs Type 2 guide. As documents, there are two fast tells — the wording of the opinion and the columns in Section 4.

Type 1 — a point in time

  • The opinion speaks “as of” a single date — design and implementation on that day, nothing about the months before or after.
  • Section 4 lists the criteria and controls but shows no test procedures and no results — the auditor evaluated design, not operation.
  • Common as a first milestone for a young compliance program. Most buyers accept it once, then expect a Type 2.
  • It cannot tell you whether controls kept operating — that is precisely what it does not cover.

Type 2 — a review period

  • The opinion covers a stated period — typically 3–12 months — and addresses operating effectiveness throughout it.
  • Section 4 shows, for every control, the tests the auditor performed and their results, including any exceptions.
  • The version enterprise buyers and security reviews expect from an established vendor, refreshed annually.
  • Exceptions can and do appear under clean opinions — read them with management’s responses rather than just counting them.
For Reviewers

An Eight-Step Review Checklist

Vendor-risk teams rarely get hours per report. This sequence covers what matters, in the order that saves the most time.

  1. 1

    Check the type and the period. Type 1 or Type 2, and when the period ended. A report whose period ended more than 12 months ago is stale — ask when the next one lands, or request interim coverage.

  2. 2

    Read the opinion. Unmodified, qualified, adverse, or disclaimed — and if qualified, exactly which criteria or parts of the description the qualification touches.

  3. 3

    Check the categories in scope. Security must be there. If you depend on uptime commitments, look for Availability. If the vendor holds data under confidentiality obligations, look for Confidentiality.

  4. 4

    Confirm the system boundary. Does Section 3 describe the product, environment, and legal entity you actually buy from — or a different one?

  5. 5

    Scan Section 4 for exceptions. Read each exception, the criteria it touches, and management’s response. A handful of well-handled exceptions is normal in a Type 2.

  6. 6

    Map the CUECs. List every complementary user entity control and confirm your organization actually operates it — the report’s assurance assumes you do.

  7. 7

    Note the subservice organizations. Under the carve-out method you inherit the job of monitoring them — typically by obtaining and reviewing their own SOC reports.

  8. 8

    Close any period gap. If the period ends well before your fiscal year-end or review date, ask for a bridge letter covering the interim months.

SOC 2 Reports — Common Questions

What the document is, what each section contains, and how to review one.

What is a SOC 2 report?
A SOC 2 report is the deliverable of an attestation examination performed by an independent licensed CPA firm under the AICPA’s attestation standards (SSAE, at AT-C sections 105 and 205). The auditor examines a service organization’s controls against the Trust Services Criteria and issues an opinion. The document — typically 60–150+ pages — contains the auditor’s report, management’s assertion, a description of the system, the controls-and-tests matrix, and optional other information from management.
What are the sections of a SOC 2 report?
Five. Section 1 is the independent service auditor’s report, ending in the opinion. Section 2 is management’s assertion. Section 3 is management’s description of the system, prepared under the AICPA Description Criteria (DC section 200). Section 4 pairs the applicable trust services criteria with the related controls and — in Type 2 reports — the auditor’s tests and results. Section 5, optional and unaudited, carries other information from management, such as responses to exceptions.
What is the system description (Section 3) in a SOC 2 report?
The system description is management’s account of what was examined, prepared under DC section 200. It covers the services provided, principal service commitments and system requirements, the system’s components (infrastructure, software, people, procedures, and data), relevant incidents, the trust services categories in scope, complementary user entity controls, subservice organizations and whether the carve-out or inclusive method applies, and, in Type 2 reports, significant changes during the period. It defines the boundary of the assurance.
How is a Type 1 report different from a Type 2 on the page?
Two tells. First, the opinion wording: a Type 1 opines on design and implementation “as of” a single date, while a Type 2 covers operating effectiveness throughout a review period — typically 3 to 12 months. Second, Section 4: a Type 1 describes controls but shows no test procedures and no results. A Type 2 shows the tests the auditor performed on each control and the result, including any exceptions noted.
How recent does a SOC 2 report need to be?
Reports do not formally expire, but the working convention is 12 months. Most service organizations run annual Type 2 cycles, so a report whose period ended more than a year ago with no successor examination underway is a red flag. For shorter gaps — the months between the period end and your own review or fiscal year-end — ask the vendor for a bridge letter and the expected date of the next report.
Is SOC 2 a certification?
No. SOC 2 is an attestation examination: a licensed CPA firm issues an opinion on management’s assertion, and the deliverable is a report, not a certificate. “SOC 2 certified” is marketing shorthand — there is no certificate, no accreditation badge, and no registry. If a vendor offers a certificate or logo in place of a report, ask for the report. It is the only artifact that carries the auditor’s opinion.
Can I get a SOC 2 report example PDF?
Usually not a real one. Full SOC 2 reports are restricted-use documents intended for the service organization, its customers, and other specified parties, so they are shared under NDA rather than published. The public equivalent is SOC 3, a general-use summary — several large cloud providers publish theirs, and reading one shows the style of the auditor’s report and system overview, though not the Section 4 controls-and-tests detail that makes SOC 2 reports useful to reviewers.

Written By Expert Auditors

Surendra Pal SinghChief Information Security Officer & Data Protection OfficerCISODPOCISAMCSEITILISO 27001 Lead AuditorISO 27701 Lead AuditorISO 42001 Lead Auditor
Saundhi ChauhanLead AuditorISO 27001 Lead AuditorISO 27701 Lead AuditorISO 42001 Lead Auditor
Last reviewed: July 2026 • Content verified by certified lead auditors

Get in touch

Book a free consultation or send us your requirements. We respond within 24 hours.

Send us your requirement.

01Your details
02What is it about?
SOC 2
03Send
Asking about: SOC 2