Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A SOC 3 report is the public, general-use summary of a SOC 2 Type 2 examination: the auditor’s opinion and a short system description, without the detailed control testing.

What Is a SOC 3 Report?
A SOC 3 report is the publishable version of a SOC 2. It comes from the same examination, performed by the same licensed CPA firm against the same Trust Services Criteria, but it strips out everything a competitor could exploit: the detailed control descriptions, the auditor’s test procedures, and the results of those tests.
What remains is the independent opinion, a condensed description of the system, and management’s assertion. Because nothing in it is sensitive, a SOC 3 is a general-use report that can sit on a public web page. The major cloud providers publish theirs exactly that way.
| Section | SOC 2 Type 2 | SOC 3 |
|---|---|---|
| Independent auditor’s opinion | Yes | Yes |
| Management assertion | Yes | Yes |
| System description | Detailed | Condensed |
| Control descriptions and test procedures | Yes | No |
| Test results and exceptions | Yes | No |
| Complementary user entity controls | Yes | Usually not |
| Distribution | Restricted, under NDA | Unrestricted, public |
A SOC 3 typically runs to half a dozen pages against the hundred or more of a SOC 2. The brevity is deliberate rather than a sign of a lighter audit; the work behind both documents is identical.
There is no separate SOC 3 engagement in the ordinary sense. An organisation commissions a SOC 2 Type 2 examination covering a defined observation period, and asks the auditor to issue a SOC 3 alongside it. The incremental cost is small because the fieldwork has already been done.
One constraint matters: a SOC 3 can only be issued when the opinion is unqualified. If the examination found exceptions significant enough to qualify the opinion, there is nothing to publish, which is part of why a SOC 3 on a vendor’s website carries meaning despite its brevity. It is a signal that an independent examination took place and passed.
SOC 3 earns its place in three situations. The first is marketing: a downloadable report with an auditor’s name on it answers the “are you secure” question on a website without an NDA exchange. The second is scale: a provider with tens of thousands of customers cannot negotiate confidentiality agreements with every one of them, which is why hyperscale cloud platforms publish SOC 3 openly while reserving the SOC 2 for customers under agreement. The third is a quick first-pass filter during supplier selection, before you commit effort to a full assessment.
It is the wrong document for actual due diligence. A SOC 3 cannot tell you which controls failed testing, which subservice organisations were carved out, or what the report assumes you are doing at your end. Those sit in the sections SOC 3 omits, and they are precisely what a supplier security assessment needs to examine.
British buyers see SOC 3 most often on American SaaS vendors’ trust pages. Treat it as a screening artefact: confirm the report is current, check the period it covers, note which Trust Services Criteria were in scope, and then request the SOC 2 Type 2 under NDA before signing anything material. If a vendor publishes a SOC 3 but will not share the underlying SOC 2, that refusal is itself information.
For UK and European assurance, ISO 27001 certification remains the more familiar reference, and a certificate is also public by nature. The two serve the same screening function; neither replaces reading the detail behind it, and under UK GDPR you remain accountable for assessing the processors you appoint whatever documents they publish.
Published reports are sometimes accompanied by a logo or seal on a vendor’s site. Check the date on the report rather than trusting the badge: seals persist on web pages long after the examination period they refer to has ended, and a report covering a period that finished two years ago describes an organisation that may no longer exist in the same form.
If you are assessing a supplier whose published reports leave questions open, our cyber risk analysis services can evaluate the residual exposure that paperwork does not cover.
Both come from the same examination against the Trust Services Criteria. SOC 2 is a detailed, restricted-use report containing control descriptions, test procedures, test results, and complementary user entity controls, shared under NDA. SOC 3 is a short, general-use summary containing only the auditor’s opinion, a condensed system description, and management’s assertion, and it can be published publicly.
Only as a first filter. It confirms that an independent examination took place and that the opinion was unqualified, but it omits the test results, exceptions, carve-outs, and user entity controls that a real assessment depends on. Request the SOC 2 Type 2 under NDA before entering a contract that gives the supplier access to personal or sensitive data.
Only marginally. Because it is derived from a SOC 2 Type 2 examination that has already been performed, the additional work is drafting and issuing a condensed report. Most audit firms quote it as a small add-on to the SOC 2 engagement. It can only be issued when the auditor’s opinion on the underlying examination is unqualified.
Rarely by name. UK and European buyers typically ask for ISO 27001 certification, and American buyers ask for SOC 2. SOC 3 is used more by vendors than by buyers, as a public assurance artefact that avoids NDA overhead. UK procurement teams encounter it mainly on the trust pages of US cloud and SaaS providers.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.