Audit Insights & Preparation

SOC 2 Report Explained: What It Contains and How to Read It

Tyler Carbone
Published Updated 10 min read

An unqualified opinion does not mean the report has zero findings. What we always explain to clients is that it means any exceptions identified were not material enough, individually or collectively, to prevent the auditor from expressing a clean opinion. Minor exceptions are common and expected, even in unqualified reports.

Key Takeaways

  • •A SOC 2 report contains five sections: auditor's opinion, management's assertion, system description, criteria/controls/tests/results, and other information
  • •The auditor's opinion is the most important element — an unqualified (clean) opinion means controls met the Trust Service Criteria
  • •The system description defines what is in scope — we always advise verifying that the specific service you use is covered
  • •Complementary User Entity Controls (CUECs) define your responsibilities as a customer — failing to implement CUECs creates control gaps

This guide walks through each section of a SOC 2 report, explains what to look for, how to interpret the auditor's opinion, what exceptions and findings mean, and how to evaluate whether a report demonstrates adequate controls for your vendor risk management program.

For the next operating decision, compare SOC 2 compliance for startups with policies needed for SOC 2. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.

What sections make up a SOC 2 report?

The Five Sections

Every SOC 2 report follows a standardized structure defined by AICPA attestation standards:

What sections make up a SOC 2 report? — comparison
SectionWhat It ContainsWho Writes It
Section 1: Independent Auditor's ReportThe auditor's opinion on whether controls meet the Trust Service CriteriaThe CPA firm (auditor)
Section 2: Management's AssertionManagement's statement that the system description is fairly presented and controls are suitably designed (and operating effectively for Type II)The service organization's management
Section 3: System DescriptionDetailed description of the service, infrastructure, software, people, procedures, and dataThe service organization (reviewed by auditor)
Section 4: Description of Criteria, Controls, Tests, and ResultsTrust Service Criteria mapped to specific controls; for Type II, includes test procedures and resultsControls described by management; tests and results by auditor
Section 5: Other InformationOptional section for additional context provided by managementThe service organization

Type I vs Type II Report Differences

What sections make up a SOC 2 report? — comparison
ElementType I ReportType II Report
Opinion scopeControls are suitably designed at a point in timeControls are suitably designed and operating effectively over a period
Test resultsNo testing of operating effectivenessDetailed testing procedures and results for each control
Observation periodSingle date (e.g., December 31, 2025)Date range (e.g., January 1, 2025 through December 31, 2025)
Typical length40-80 pages80-200+ pages
Enterprise buyer acceptanceLimited — many buyers require Type IIBroadly accepted by enterprise procurement

What does the independent auditor’s opinion say?

What It Contains

The auditor's report is the most critical section — it contains the CPA firm's professional opinion on whether the service organization's controls met the applicable Trust Service Criteria. The opinion letter typically includes:

  • The scope of the engagement (which Trust Service Criteria were evaluated)
  • The period covered (Type II) or date evaluated (Type I)
  • The auditor's responsibilities and the standards used
  • The opinion itself — unqualified, qualified, adverse, or disclaimer

The Four Opinion Types

What does the independent auditor’s opinion say? — comparison
OpinionWhat It MeansHow to Interpret
Unqualified (clean)Controls are suitably designed and operating effectively; no material exceptionsThe report meets the standard — proceed with vendor evaluation based on the details
QualifiedMaterial exceptions exist in specific areas, but the overall control environment is effectiveReview the specific qualifications carefully; evaluate whether the exceptions affect controls relevant to your data
AdverseSignificant and pervasive control deficiencies; controls do not meet the Trust Service CriteriaThe report indicates fundamental control failures — significant concern for vendor risk
DisclaimerThe auditor was unable to obtain sufficient evidence to form an opinionThe auditor could not complete the assessment — treat as a red flag

What to Look For

Specialized firms (Schellman, A-LIGN, KirkpatrickPrice, BARR Advisory, Coalfire, Linford & Company) and regional CPA firms with SOC 2 practices produce credible reports

Section 2: Management's Assertion

What It Contains

Management's assertion is a formal statement from the service organization's leadership asserting that:

  • The system description is fairly presented
  • Controls are suitably designed to meet the applicable Trust Service Criteria (Type I and Type II)
  • Controls operated effectively throughout the specified period (Type II only)

What to Look For

  • Signed by management — typically the CEO, CTO, or VP of Engineering
  • Consistent with the auditor's opinion — the assertion should align with the scope and period of the auditor's report
  • No disclaimers or limitations — management should assert without significant caveats

Management's assertion is analogous to a company's representation letter in a financial audit — it establishes management's accountability for the accuracy of the information in the report.

Section 3: System Description

What It Contains

The system description is the longest section and provides detailed context about the service organization's environment. Key components include:

Section 3: System Description — comparison
ComponentWhat It DescribesWhy It Matters
Services providedThe specific services covered by the SOC 2 reportConfirms the report covers the services you use
System boundariesThe infrastructure, software, people, procedures, and data within scopeDefines what was evaluated and what was excluded
InfrastructureCloud providers, data centers, network architectureConfirms appropriate infrastructure for your data
SoftwareApplications, databases, operating systems used to deliver the serviceIdentifies the technology stack and potential risk areas
PeopleOrganizational structure, roles, and responsibilitiesShows who is responsible for security and compliance
ProceduresKey operational procedures (change management, incident response, backup)Describes how the organization operates day-to-day
DataTypes of data processed, data flows, data storageConfirms whether your data types are in scope
Complementary User Entity Controls (CUECs)Controls the customer must implement for the overall control environment to be effectiveIdentifies your responsibilities as a customer
Complementary Subservice Organization Controls (CSOCs)Controls performed by subservice organizations (cloud providers, data processors)Identifies dependencies on third parties

What to Look For

  • Service coverage — does the system description cover the specific service or product you use? Some organizations have multiple products but only include certain services in their SOC 2 scope
  • Infrastructure alignment — is data stored in regions and on infrastructure appropriate for your requirements?
  • CUECs — what controls are you expected to implement? Common CUECs include MFA configuration, access management for your users, and data encryption settings. If you do not implement the CUECs, there may be gaps in the overall control environment
  • Subservice organizations — who are the critical dependencies? If the organization relies on AWS, GCP, or other subservice organizations, those organizations should have their own SOC 2 reports (carve-out method) or be included in the service organization's scope (inclusive method)
  • Carve-out vs inclusive method — if subservice organizations are carved out, their controls are not tested in this report; you may need to review the subservice organization's own SOC 2 report separately

Section 4: Criteria, Controls, Tests, and Results

What It Contains

This section maps the applicable Trust Service Criteria to the service organization's specific controls and (for Type II) includes the auditor's test procedures and results:

Section 4: Criteria, Controls, Tests, and Results — comparison
ElementDescription
Trust Service CriteriaThe specific criterion being evaluated (e.g., CC6.1 — logical access security)
Control descriptionHow the organization addresses the criterion (e.g., "MFA is required for all production system access")
Test procedure (Type II only)What the auditor did to test the control (e.g., "Inspected MFA configuration for all in-scope systems")
Test result (Type II only)Whether the control operated effectively or whether exceptions were identified

Understanding Exceptions

Exceptions are findings where a control did not operate as designed during the observation period. Exceptions are documented in the report regardless of their severity.

Section 4: Criteria, Controls, Tests, and Results — comparison
Exception SeverityWhat It MeansHow to Evaluate
Minor / isolatedA single instance where a control did not operate as designed (e.g., one employee's access was deprovisioned two days late)Low concern — isolated instances are common; check whether the issue was remediated
PatternMultiple instances of the same control failure (e.g., five of twenty-five sampled terminations had deprovisioning delays)Medium concern — indicates a systemic weakness in the control; evaluate whether the pattern affects your data
PervasiveControl failures across a significant portion of the observation period or across multiple control areasHigh concern — may indicate fundamental program weaknesses; evaluate carefully

What to Look For

  • Exception count and severity — how many exceptions were identified? Are they isolated or patterns?
  • Exception areas — which control domains had exceptions? Access management exceptions are more concerning than documentation gaps
  • Remediation — did the organization remediate the exceptions? Some reports note corrective actions taken during the observation period
  • Controls relevant to your data — focus your review on controls that protect the data you entrust to the vendor (access controls, encryption, monitoring, incident response)

Section 5: Other Information

What It Contains

This optional section includes additional context that management wants to provide but is not part of the auditor's evaluation. Common content includes:

  • Remediation plans for identified exceptions
  • Future control improvements planned
  • Additional certifications or compliance efforts (ISO 27001, HIPAA, etc.)
  • Business context about the organization

Important Distinction

The auditor's opinion does not cover Section 5. Information in this section is management's representation only — not independently verified. We always advise clients to treat it as supplementary context, not audited evidence.

How do you Evaluate a Vendor's SOC 2 Report?

Evaluation Checklist

How do you Evaluate a Vendor's SOC 2 Report? — comparison
Evaluation StepWhat to CheckRed Flag
1. Verify the opinionIs the opinion unqualified?Qualified, adverse, or disclaimer opinion
2. Check the periodDepends on scope and readinessDepends on scope and readiness
3. Verify criteriaDoes the report include the Trust Service Criteria you require?Missing criteria that are relevant to your use case
4. Review system descriptionDoes the report cover the service you use?The specific service or product you use is not in scope
5. Review CUECsWhat controls are you responsible for implementing?Extensive CUECs that shift significant control responsibility to you
6. Review exceptionsAre exceptions minor and isolated, or systemic and concerning?Multiple exceptions in access management or data protection
7. Check subservice organizationsAre critical dependencies (cloud providers) addressed through carve-out or inclusive method?Critical subservice organizations not addressed at all
8. Assess relevanceDo the controls described actually protect your data in the way you need?Controls are generic and do not address your specific data handling requirements

Common Evaluation Mistakes

How do you Evaluate a Vendor's SOC 2 Report? — comparison
MistakeWhy It Is a Problem
Only checking the opinion without reading the detailsAn unqualified opinion can coexist with exceptions in areas relevant to your data
Accepting a Type I report when you need Type IIType I only assesses design, not operating effectiveness
Not reviewing CUECsYou may have control responsibilities you are not fulfilling
Ignoring the observation period datesA report from two years ago does not reflect the current control environment
Treating SOC 2 as a binary pass/failSOC 2 is nuanced — the details matter more than the opinion alone
Not checking whether your specific service is in scopeOrganizations with multiple products may only include certain services

Complementary User Entity Controls (CUECs)

CUECs deserve special attention because they define your responsibilities as a customer of the service organization.

Common CUECs

Complementary User Entity Controls (CUECs) — comparison
CUECYour Responsibility
Implement MFA for user accountsEnable and enforce MFA for all users accessing the vendor's platform
Manage user access appropriatelyProvision and deprovision user access according to your own access management policies
Protect authentication credentialsEnsure API keys, passwords, and tokens are securely managed
Monitor your usageReview access logs and activity within the vendor's platform
Maintain your own security controlsImplement security controls for systems and data under your control that interact with the vendor
Report security incidentsNotify the vendor of any security incidents that may affect the shared environment

If you do not implement CUECs, there is a gap in the overall control environment — even if the vendor's controls are operating effectively. We always advise our clients that their SOC 2 report review should include an assessment of whether their organization is fulfilling the specified CUECs.

AICPA & CIMA’s SOC overview describes CPA assurance services. It defines the assurance context; it does not establish vendor rankings, market prices, or a particular company’s readiness.

Frequently Asked Questions

What are complementary user entity controls in a SOC 2 report?
Controls the report assumes you — the customer — will perform for the vendor's control objectives to hold. They define your side of the boundary, and skipping them is how organizations assume coverage they do not actually have.
Which section of a SOC 2 report should you read first?
The auditor's opinion in Section 1. It tells you whether the opinion is unqualified, what period it covers, and which criteria were in scope. Section 4 then shows the tests performed and any exceptions found.
What does a qualified SOC 2 opinion mean?
That the auditor found one or more controls did not operate effectively during the period. It is not automatically disqualifying — what matters is which control failed, how wide the exception was, and management's documented response.
Tyler Carbone

Tyler Carbone

Managing Director and Cofounder

Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.

LinkedIn

Related Reading

Stay ahead of compliance

Expert insights on cybersecurity compliance delivered to your inbox.

We respect your privacy. Unsubscribe anytime.