What is a SOC 2 report and who reads it?
Direct answer
A SOC 2 report is the written output of an attestation engagement: an independent CPA firm examines a service organization's controls against the AICPA Trust Services Criteria and issues a formal opinion. The report is a private document: unlike an ISO 27001 certificate, it is not publicly verifiable.
It is distributed under NDA to enterprise customers and prospects who request it during vendor due diligence. Procurement and security teams read three things in a SOC 2 report: the auditor's opinion (whether it is unqualified or contains exceptions), the system description (which services and systems were in scope), and the exceptions table (any controls that failed or deviated during the audit period). A narrow scope or a qualified opinion raises questions a buyer will ask about. A Type II report with a clean, unqualified opinion and appropriate scope is the artifact that closes enterprise deals where a vendor security questionnaire alone would not suffice. The report is typically renewed annually, which is why the observation-period cadence is ongoing rather than one-time.
What is inside a SOC 2 report?
A SOC 2 report is the result of an examination engagement under the AICPA attestation standards (AT-C sections 105 and 205, from SSAE No. 18, effective for reports dated on or after 1 May 2017). In an examination, the CPA, called the practitioner, expresses an opinion on the subject matter, or on management’s assertion about it, against an identified set of criteria. For SOC 2, those criteria are the Trust Services Criteria for the categories in scope.
The report is built around management’s description of the service organization’s system. That description is prepared and evaluated against a separate AICPA benchmark, the 2018 SOC 2 Description Criteria. The objectives the controls are judged against are the organization’s commitments to its customers and its system requirements.
What the report contains beyond that depends on the type. According to the AICPA, a Type 2 report includes an opinion on the operating effectiveness of controls throughout a specified period, plus a detailed description of the auditor’s tests of controls and their results. A Type 1 report covers the same system but contains neither. See SOC 2 Type I vs Type II.
How does SOC 2 differ from SOC 1 and SOC 3?
- SOC 1 examines controls at a service organization that are likely to be relevant to its customers’ internal control over financial reporting. Its readers are those customers (user entities) and the CPAs who audit their financial statements (user auditors).
- SOC 2 examines controls relevant to security, availability, processing integrity, confidentiality or privacy. It is the report security and procurement teams ask for.
- SOC 3 covers the same categories. The AICPA describes it as a general use report that can be freely distributed, which contains an opinion on the operating effectiveness of controls but not the detailed description of tests and results.
A payroll or billing provider may need SOC 1 for its customers’ financial auditors and SOC 2 for their security teams. A company that wants something to publish on its website uses SOC 3.
What should a reader check before relying on a report?
A report is only useful if it covers what you actually rely on:
- The services and systems in the system description match the ones you buy. A report on one product says nothing about another.
- The categories in scope match your concerns. If you depend on uptime, a report limited to Security does not test Availability.
- The period overlaps the time you rely on the service, and the report is recent.
- The opinion, and for a Type 2 the tests and their results, show no exceptions on the controls that matter to you.
- The signing CPA firm is one you can identify and check.
Security teams usually file the result with the rest of the supplier’s assessment, so the report is read once, in context, rather than every time someone asks. See how supplier security grading works.
How Acuna GRC handles it
- Solution
SOC 2
Keep SOC 2 evidence for the whole period as work happens, reuse your ISO 27001 controls, feed controls from your tools and share the report under NDA.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Module
Trust Center
Answer RFPs and security questionnaires from an approved answers library and an exposure library, and share a public trust page with gated documents.
Sources
- AICPA, 2017 Trust Services Criteria (With Revised Points of Focus, 2022), TSP section 100, paragraphs .11, .14 and .20
- AICPA, 2018 SOC 2 Description Criteria (With Revised Implementation Guidance, 2022)
- AICPA & CIMA, SOC 1 (internal control over financial reporting)
- AICPA & CIMA, SOC 3 general use report
This page explains the rules in general terms and is not legal advice.
Frequently asked
Who is allowed to issue a SOC 2 report?
A CPA performing an attestation engagement under the AICPA attestation standards. The AICPA sets the professional standards for SOC engagements and has said it acts against members whose SOC work does not follow them.
Is a SOC 2 report the same as a SOC for Cybersecurity report?
No. SOC for Cybersecurity reports on the effectiveness of an entity’s cybersecurity risk management program, using the criteria for security, availability and confidentiality. SOC 2 reports on a service organization’s system and the controls over it.
Can we publish our SOC 2 report?
SOC 2 reports are usually shared under NDA. To publish something, organisations use a SOC 3 report, which the AICPA describes as a general use report that can be freely distributed.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

