A SOC 3 report is a general-use summary report based on your SOC 2 examination. You can publish it freely on your website to demonstrate your security compliance without exposing confidential technical details.

SOC 3 is based on the same audit as your SOC 2, but it's designed to be shared freely — without exposing the technical detail of your controls.
| Criteria | SOC 2Full | SOC 3Public |
|---|---|---|
| Audit Basis | A full audit of the Trust Services Criteria (security, availability, integrity, confidentiality, privacy). | The same audit as the SOC 2 — not a separate or additional process. |
| Level of Detail | Includes the full system description, the tests performed, and detailed results for each control. | A high-level summary with the auditor's opinion, without the technical detail of the tests. |
| Audience | Clients and prospects, typically under a non-disclosure agreement (NDA). | The general public — no distribution restrictions. |
| Where Is It Used? | Security questionnaires, vendor reviews, procurement teams. | Website, "Trust & Security" page (Trust Center), sales materials. |
| Does It Replace the Other? | No — it remains the document that clients with stricter security requirements will ask for. | No — it's a public-facing complement, not a substitute for SOC 2. |
Any organization with a current SOC 2 report that wants to demonstrate its compliance publicly, without exposing confidential details about its controls.
| Type of company | How SOC 3 helps | Where it is used | SOC 2 required first? |
|---|---|---|---|
| SaaS companies | Shortens the sales cycle by answering prospects' security questions up front. | Trust Center or "Security & Trust" page | Yes |
| Cloud / hosting providers | Shows enterprise customers that the infrastructure meets recognized standards. | Corporate website and master service agreements | Yes |
| FinTech companies and payment processors | Builds trust with end users and banking partners without publishing sensitive technical details. | App, website, and regulatory materials | Yes |
| Marketing and sales teams | Use the SOC 3 report as evidence of compliance in sales proposals and RFP responses. | Proposals, landing pages, and initial security questionnaires | Yes |
| Growth-stage startups | Answers baseline security questions from investors and early enterprise customers. | Investor data room and website | Yes |
The most common questions about the SOC 3 report, how it relates to SOC 2, and how to use it publicly. Select a question to see the answer.
A SOC 3 report is a general-use attestation report, issued under the same AICPA SSAE 18 framework as SOC 2, that summarizes the auditor's opinion on your organization's controls relevant to the Trust Services Criteria, without including the confidential technical details of control testing.
Unlike the full SOC 2 report, which is restricted-use, a SOC 3 report is designed so you can publish it freely on your website, without requiring readers to sign a nondisclosure agreement.
SSAE 18 · Trust Services CriteriaNo. Like the SOC 2 report it is derived from, SOC 3 is not a certification granted by a certifying body. It is an attestation report containing the opinion of an independent CPA auditor.
Important distinction: the correct phrasing is "obtaining a SOC 3 report" or "displaying a SOC 3 seal," not "getting SOC 3 certified."
They are the same five categories evaluated in a SOC 2: Security (required), Availability, Processing Integrity, Confidentiality, and Privacy. The SOC 3 report summarizes the auditor's opinion on these same criteria in a format suitable for public distribution.
Many website "security seals" are just marketing graphics with nothing behind them. SOC 3 is different: it is an actual report containing an independent CPA auditor's opinion, verifiable, with an issue date and a defined coverage period — not just an icon.
A SOC 3 report lets you:
| Criteria | SOC 2 (full report) | SOC 3 (general use) |
|---|---|---|
| Underlying audit | Full examination against the Trust Services Criteria | The same examination as the SOC 2 — not an additional process |
| Level of detail | Full system description and detailed results for each control | High-level summary with the auditor's opinion |
| Distribution | Restricted, under NDA | Public, with no restrictions |
In short, SOC 3 is the public-facing version of SOC 2, not a separate report.
No. A SOC 3 report is issued from the same SOC 2 Type 2 examination. It is not a separate audit process, but a summarized, general-use version of the same work.
SOC 3 is derived only from SOC 2 and summarizes the Trust Services Criteria (Security, Availability, and so on) for public distribution. SOC 1 evaluates controls relevant to your customers' financial reporting (ICFR) and, because it contains sensitive information, has no equivalent public version.
No. SOC 3 is a public-facing complement, not a substitute. Customers with stricter security requirements will still request the full SOC 2 report under NDA.
It is common among:
In general, any company that already has a SOC 2 report and wants to demonstrate its compliance publicly.
If you answer yes to any of these questions, you should consider one:
Most commonly, it is posted on a Trust Center or "Security & Trust" page on your website and used as supporting evidence in sales proposals, RFP responses, and initial security questionnaires.
Virtually none. Because it is issued from the same examination, the SOC 3 report is delivered together with the SOC 2 Type 2 report, with no additional examination period or fieldwork.
Important: if you haven't started your SOC 2 yet, you can't skip straight to SOC 3. The SOC 2 Type 2 examination is completed first, and the SOC 3 report is issued from that same work.
It includes:
It does not include the detailed control matrix or individual test results — those remain only in the full SOC 2 report.
No. If you are already completing your SOC 2 Type 2 with us, just request it and we include it as part of the same process. No additional evidence, controls, or testing is required.
Yes. If the underlying SOC 2 had them, the public summary may reflect a qualified opinion. That is why many companies prefer to remediate significant deviations before publishing their SOC 3, although it is not mandatory.
Like the SOC 2 it is derived from, it is renewed annually. When you renew your SOC 2 Type 2 each year, the SOC 3 is updated along with it.
Yes. Because it is based on the same AICPA SSAE 18 framework as SOC 2, it is recognized in the United States, Latin America, and other markets where service providers are asked for security assurance.
Yes. We work with technology companies in the United States, Colombia, Mexico, Chile, Peru, Argentina, Panama, Costa Rica, Ecuador, and other countries, in English and Spanish.
Choose the option that best describes your situation, and we'll take you straight to what you need.
This website uses cookies to enhance user experience and to analyze performance and traffic on our website. We also share information about your use of our site with our social media, advertising and analytics partners. To learn more, view our Privacy Policy
Required for the website to function. Always active.
Remember your settings and choices.
Help us understand how visitors use the site.
Used to show you relevant ads.