Home / Guides / A SOC 3 is the public summary of a SOC 2 examination, and AWS, Google and Microsoft publish one
Guide, read 12 Nov 2026
A SOC 3 is the public summary of a SOC 2 examination, and AWS, Google and Microsoft publish one
Open the glossarySee the ranked index
The AICPA classes a SOC 3 as a general-use report that can be freely distributed
The AICPA's SOC 3 page, read 12 Nov 2026, says SOC 3 reports, like SOC 2 reports, address controls relevant to security, availability, processing integrity, confidentiality or privacy, but do not provide the same level of detail. For that reason they are considered general use reports and can be freely distributed. The text read states no further distribution conditions. The page lists resources, including an illustrative SOC 3 report and a logo.
Microsoft describes its SOC 3 as a short, public-facing summary of its SOC 2 Type 2 attestation report, for users who need assurance but do not need the full report or are not eligible under SOC 2 to receive one. That last clause points at the SOC 2 restriction. A SOC 2 is meant for users with a business need, not for anyone who asks.
Both reports are issued under the same attestation standards. AWS's page lists SSAE No. 18 with AT-C 105 and AT-C 205 for its SOC 2 and its SOC 3, and the same 2017 Trust Services Criteria for each. The two reports differ in audience and content, not in the standard or the criteria. A company that has the examination behind a SOC 2 has done the testing a SOC 3 relies on.
A SOC 3 holds the opinion, the assertion and a short description, and leaves out the tests
Schellman (March 18, 2025) lists the parts of a SOC 3: the auditor's opinion on whether management's assertion is fairly stated, management's assertion about the system and controls, and a system description less detailed than a SOC 2's. Microsoft's pages describe the same pair: a written assertion by management on control effectiveness against its commitments, and the service auditor's opinion on whether that assertion is stated fairly.
Schellman states that a SOC 3 requires an existing SOC 2, because it is a broad summary of the SOC 2 without the detailed testing results or control activities in Section 4. It also says the SOC 3 rests on the same audit, so no extra assessment is needed, only a separate report prepared for broader distribution. Google says the same of its own reports: the SOC 3 is based on the same scope as the related SOC 2.
Because the examination is shared, the period and categories match. AWS says its SOC 2 and SOC 3 each cover 12 months ending 3/31 or 9/30. If a company's SOC 2 covers Security and Availability, the SOC 3 covers those two and no others. A SOC 3 cannot show more than the examination behind it, which is also why a weak SOC 2 cannot be repaired by publishing the short version.
| Element | SOC 2 | SOC 3 |
|---|---|---|
| Auditor's opinion | Yes, Section 1 | Yes |
| Management assertion | Yes, Section 2 | Yes |
| System description | Detailed, Section 3 | Shorter overview |
| Tests of controls and results | Yes, Section 4 | None, per Schellman |
| Distribution | Users with a business need, often under NDA | General use |
A SOC 2 goes to users with a business need, and a SOC 3 goes to anyone
AWS lists the audience for its SOC 2 as users with a business need, available from AWS Artifact, and for its SOC 3 as publicly available. Google lets customers request its SOC 2 and SOC 3 reports through Compliance Reports Manager. Schellman says companies typically share SOC 2 reports only under NDA with customers, prospects and partners who require deeper due diligence.
Schellman gives the reason: a SOC 2 holds descriptions of controls, testing procedures and findings that could expose security and operational detail. A SOC 3 removes the sensitive detail while still showing compliance and the scope of the review. For a buyer without an NDA, the SOC 3 is the document they can open today. For a buyer ready to review controls, it is a prompt to ask for the SOC 2.
Neither report replaces the other in diligence. Schellman's guidance on reading a vendor's report lists SOC 2 and SOC 3 together as reports on the security, confidentiality, availability, processing integrity or privacy of a system. A security reviewer who needs to see exceptions, tests and complementary controls needs the SOC 2, because those items appear only there.
AWS, Google Cloud and Azure each publish a SOC 3 on a public page
AWS lists a SOC 3 report for Security, Availability, Confidentiality and Privacy that is publicly available as a whitepaper, and says Ernst & Young LLP performs its SOC 1, SOC 2 and SOC 3 audits. It describes the SOC 3 as a public-facing report showing that AWS has met the criteria, without sharing AWS internal information. Its fall cycle, with a period ending September 30, issues SOC 1, 2 and 3 in about late November.
Google Cloud says its core Google Cloud and Google Workspace SOC 3 reports are issued quarterly through the Compliance Reports Manager, with the first quarter covering February 1 through January 31 and issuing in late April. A small group of other products get separate SOC 3 reports semi-annually or annually. Google also says it issues no bridge letters for SOC 3 and points readers to the bridge letters for the related SOC 2.
Microsoft's Azure page says the Azure SOC 3 attestation report is publicly available, and describes the SOC 3 as a short, publicly facing version of the SOC 2 Type 2 report. Microsoft lists the services in scope by name. These three show the pattern a smaller company can copy: a public file, a stated period, a named scope and a pointer to the fuller report for customers who qualify.
| Provider | Where the SOC 3 sits | Cadence stated | Period stated |
|---|---|---|---|
| AWS | Public whitepaper linked from the AWS SOC page | Twice per year | 12 months ending 3/31 or 9/30 |
| Google Cloud | Compliance Reports Manager | Quarterly for core services | Quarter 1: February 1 through January 31 |
| Microsoft Azure | Publicly available Azure SOC 3 attestation report | None found on the page read | None found on the page read |
Using a SOC 3 on a website means matching the claim to the report
Link the report file itself, the auditor's signed PDF, and show its coverage dates beside the link. AWS and Google both state coverage periods on their pages. Visitors then see what was examined and when, rather than a badge. Replace the file when the next period's report is issued, since a report from a past period beside a current sales claim invites questions from every careful reader.
State the categories and the system. A SOC 3 covers the categories chosen for the SOC 2 and the system in its description. If the examination covers one product, the web copy should name that product, not the company as a whole. Microsoft's pages list the in-scope services by name, which is the pattern to follow: name the services, then link the report.
Schellman calls the SOC 3 a marketing tool that can reduce friction in procurement; treat that as the firm's view. The AICPA page lists a logo resource under SOC 3, and its terms were not retrieved on 12 Nov 2026, so confirm mark usage with the CPA firm before placing one. If the examination ended in anything other than an unqualified opinion, the public report will say so too, because the opinion is a required part of it.
More guides
- SOC 2 auditors test a sample of each control population, and one firm publishes a 3 to 30 item range
- What a SOC 2 Type 2 auditor asks for: population lists, samples and dated evidence
- The SOC 2 observation window: 3 to 12 months, and every control must run through it
Sources
- AICPA & CIMA: SOC 3 topic page, read 12 Nov 2026
- Schellman: What You Need to Know About SOC 3 Reports, read 12 Nov 2026
- Schellman: How to Read Your Vendor's SOC Report, read 12 Nov 2026
- Microsoft Learn: SOC 3 overview, read 12 Nov 2026
- Microsoft Learn: Azure SOC 3, read 12 Nov 2026
- AWS: SOC Compliance and FAQs, read 12 Nov 2026
- Google Cloud: SOC 3 compliance, read 12 Nov 2026
- BARR: Breaking Down SOC 2 Reports, Each Section, read 12 Nov 2026
Last reviewed 12 Nov 2026.