On this page

A SOC 2 report is a restricted-use report for customers and other specified readers: it describes your system in detail and lists the auditor’s tests of controls and their results. A SOC 3 report covers the same AICPA Trust Services Criteria over a stated period, but leaves out the detailed system description and the tests, so it is ordinarily a general-use report you can post publicly (the AICPA’s guide allows a restriction in some cases, covered below). Most companies get a SOC 3 by asking their CPA firm to issue one at the end of a SOC 2 Type 2 examination, which adds a short report rather than a second audit. A SOC 3 does not replace a SOC 2 when a customer asks for the SOC 2.

What is the difference between SOC 2 and SOC 3?

The difference between SOC 2 and SOC 3 is how much each report shows and who may read it. Both rest on a CPA firm’s examination of controls against the Trust Services Criteria. A SOC 2 includes the system description and the auditor’s tests and results, so it is restricted to specified readers. A SOC 3 gives management’s assertion and the auditor’s opinion with a brief account of the system’s boundaries, so it can ordinarily go to any reader.

SOC 2SOC 3
Who may read itManagement and specified parties who understand the service, usually customers and their auditorsAnyone in the usual case; the AICPA names the intended users as interested parties
What it containsSystem description, management’s assertion, the auditor’s opinion, and the auditor’s tests of controls with resultsManagement’s assertion, including the system’s boundaries and principal service commitments, and the auditor’s opinion on it
Report typesType 1 (design at a date) or Type 2 (design and operation over a period)One type, covering a period
CriteriaTrust Services Criteria: security, plus any of availability, processing integrity, confidentiality, and privacyThe same criteria
Test exceptionsListed with the test resultsNot listed; only a modified opinion would show a problem
How it is sharedRestricted use, usually through a request process and often under an NDAGeneral use unless the report restricts use: post it on your site or send it to anyone
Typical readerA customer’s security, procurement, or vendor-risk reviewerA prospect or website visitor who does not have the SOC 2

Sources: AICPA SOC 2 guide, Appendix A (2022 edition); AICPA SOC 1 guide, Appendix E, for the single SOC 3 report type; AICPA SOC 3 overview.

What is a SOC 3 report?

A SOC 3 report is a CPA firm’s report, ordinarily for general use, on whether a service organization’s controls were effective throughout a stated period at meeting its service commitments and system requirements under the Trust Services Criteria. The AICPA’s SOC 3 overview describes it as covering the same subjects as SOC 2 with less detail, which is why it can ordinarily be distributed freely.

A SOC 3 has two parts:

  1. Management’s assertion that the controls were effective throughout the period. The assertion also describes the boundaries of the system and the principal service commitments and system requirements.
  2. The service auditor’s report, giving the CPA firm’s opinion on whether that assertion is fairly stated against the applicable criteria.

The AICPA’s illustrative SOC 3 report shows the format. Large providers publish real ones. As of October 2026, Google Cloud issues its core SOC 3 reports quarterly, each covering a 12-month period, and Microsoft issues its Office 365 SOC 3, which is based on the SOC 2 examination, at the same time as the SOC 2.

A person points to SOC 3 document next to SOC 2, with padlocks, representing security reports.

What does a SOC 2 include that a SOC 3 leaves out?

A SOC 2 Type 2 adds two sections a SOC 3 does not have: the full system description, written against the AICPA’s description criteria, and the auditor’s description of each test of controls with its results. Those sections are where a customer’s reviewer finds the controls that map to their requirements, any exceptions, the complementary user entity controls the customer must run, and the subservice organizations (a cloud host, for example) the report carves out. A SOC 3 reader gets the opinion and a short account of the system’s boundaries and commitments, without that detail.

That is why a SOC 3 rarely closes a vendor review on its own. Our guide to the SOC 2 audit report explains how reviewers read those sections.

Can you have a SOC 3 without a SOC 2?

Yes, but it is rare. The AICPA treats a SOC 3 as its own examination under the same attestation standard and guide as SOC 2, with its own components and users, so a CPA firm can perform one on its own. But the AICPA’s SOC logo guidelines (September 2020 edition) describe asking the auditor to “also issue a SOC 3 report at the end of the SOC 2 examination,” and that is how most firms provide it.

CPA firms describe the practice in similar terms:

  • Schellman states that a SOC 3 requires an existing SOC 2 and relies on the SOC 2 examination.
  • Linford & Co. says a company with only a SOC 3 is rare, because a standalone SOC 3 needs the same testing and costs about as much as a SOC 2.

If you want only a public report, ask each firm whether it performs standalone SOC 3 examinations and expect Type 2 testing and fees. If customers will ask for a SOC 2 anyway, request both reports from one examination covering one period.

Is there a SOC 3 Type 1 or Type 2?

No. There is only one type of SOC 3 report, as the AICPA’s comparison of SOC reports in its SOC 1 guide states and paragraph 1.74 of its SOC 2 guide confirms. Management’s assertion in a SOC 3 covers whether controls were effective throughout a specified period, so every SOC 3 covers a period, as a SOC 2 Type 2 does. When someone says “SOC 3 Type 2”, they mean that one report.

  • A SOC 2 Type 1 cannot produce a SOC 3. A Type 1 covers design at a single date. Plan the SOC 3 with your first Type 2 period; see SOC 2 Type 1 vs Type 2 for choosing between them.
  • There is no “SOC 2 Type 3” or “SOC Type 3” report. SOC 2 comes in Type 1 and Type 2 only, and SOC 3 is a separate report, not a third type.

Which report do you need, SOC 2 or SOC 3?

Neither report is better; they serve different readers. Start from who will read it and what they will do with it:

SituationReport to requestWhat to settle with the CPA firm
A customer’s security, procurement, or vendor-risk team asks for your SOC 2SOC 2 Type 2, or Type 1 if the customer accepts itA SOC 3 will not satisfy this request
You want prospects and website visitors to see independent assurance without an NDASOC 3, issued with your SOC 2 Type 2The same system, criteria, and period as the SOC 2
Enterprise customers need detail, and you also sell self-serveBoth, from one examinationA separate SOC 3 line in the proposal
You have only a SOC 2 Type 1 so farNo SOC 3 yetAdd the SOC 3 to your first Type 2 proposal
A customer asked for “a SOC report” without saying whichAsk which one they needSOC 1 vs SOC 2 explains how to tell, including where SOC 3 fits

Some buyers accept a public SOC 3 at an early screening and ask for the SOC 2 before signing. Ask target customers which report their review accepts, and set the deliverables during audit preparation so the proposal covers both if you need both. Other framework comparisons are listed in our compliance framework comparison.

How do you share a SOC 2 and publish a SOC 3?

A SOC 2 is intended for specified users with enough knowledge of the service and its controls. Companies commonly share it through a request process, sometimes under an NDA; the AICPA’s restricted-use designation does not itself require every recipient to sign one. Because the report contains operational detail, decide who may receive it and how you will track that:

  • Check each recipient. Confirm the requester is an intended user and apply your sharing terms, including an NDA where your policy requires one.
  • Watermark each copy with the recipient’s name and the date to discourage onward sharing and trace leaks.
  • Keep an access log of who received the report and when.

Our guide on whether customers can see your SOC 2 report covers the request process in more detail.

A SOC 3 is ordinarily general use. Check the auditor’s report for any statement limiting who may use it, then post the PDF on your security or trust page and state the system, period, criteria, and CPA firm it covers. Call it a report, not a certification, and keep any summary within the scope of the auditor’s opinion.

There is no SOC 3 seal. The AICPA and CPA Canada ended the SysTrust seal program for SOC 3 reports in October 2014 and issued no seals after December 31, 2014, according to Weaver’s summary of the announcement. SOC 3 reports themselves continued. Today a company with a SOC 1, SOC 2, or SOC 3 report from a licensed CPA can register for the AICPA’s SOC for Service Organizations logo, and the AICPA’s terms limit its display to 12 months after the report date. Our SOC 2 logo guide covers registration and the wording to use with it.

How much does a SOC 3 add to a SOC 2 audit?

When a SOC 3 is issued with a SOC 2 for the same system and period, the fieldwork is shared and the SOC 3 adds a short report; Schellman describes the added cost as minimal. A standalone SOC 3 needs the same testing as a SOC 2 Type 2, so Linford expects a similar fee. Ask each firm to price the SOC 3 as its own line, on the same system, criteria, and period as the SOC 2, so proposals compare like for like. Our SOC 2 audit cost guide covers the examination fee itself.

The SOC 3 is usually issued alongside the SOC 2, as in Microsoft’s case above. Ask the firm for draft-review and issue dates for both reports, and if a launch depends on the SOC 3, get its proposed issue date in writing.

What should you check in a vendor’s SOC 3?

If you are reading another company’s public SOC 3, six checks tell you whether it covers what you need:

  1. The period and report date. A SOC 3 covers a stated period, and the period can end months before you read it. As of October 2026, Google Cloud, for example, issues no bridge letters for SOC 3 and points customers to the bridge letter for the related SOC 2.
  2. The criteria. The common criteria for security apply to every report; availability, processing integrity, confidentiality, and privacy appear only if the company chose them.
  3. The system boundaries. The assertion names the services and system covered. Confirm that the product you are buying is inside them.
  4. The opinion. Look for an unmodified opinion on management’s assertion. Because a SOC 3 omits the test results, you will not see exceptions that did not change the opinion.
  5. The CPA firm. Confirm who signed the report and that the firm is licensed to perform the examination.
  6. Any limit on who may use it, and what the boundaries leave out. “General use” is the usual case, not a guarantee. If the system relies on a carved-out subservice organization or on controls customers must run, the AICPA’s guide says a SOC 3 can mislead readers and its use may be restricted. What limits a general-use SOC 3 has the paragraphs.

If you need the controls, exceptions, or complementary user entity controls, ask the vendor for its SOC 2 under its sharing terms. SOC 2 report red flags lists what reviewers look for once they have it.

What limits a general-use SOC 3?

A SOC 3 has no system description and no test results, so a reader sees less than the examination covered. The AICPA’s SOC 2 guide (October 2022 edition) also says where that gap can leave a SOC 3 misleading. The right-hand column is our reading of what each paragraph means for someone holding a SOC 3, not the guide’s wording.

ParagraphsWhat the guide saysWhat it means for a reader
1.15Management may engage a service auditor to examine and report on controls in a SOC 3 examination when it wants to distribute a report to users who lack the knowledge to read a SOC 2. A SOC 3 is “ordinarily appropriate for general users.”A SOC 3 can be its own engagement, and general use is the normal case.
1.73 to 1.75A SOC 3 holds only management’s assertion and the service auditor’s opinion on it. The assertion comes with the boundaries of the system and the principal service commitments and system requirements. There is no description of the system, no description of the auditor’s tests and results, and no Type 1 equivalent. The guide’s reason for leaving out the test results is that, for readers without the context, they may overshadow the opinion or be misunderstood.You see the opinion and the boundaries. Controls, tests and exceptions sit in the SOC 2.
2.192Before agreeing to a SOC 3, management and the auditor consider whether it will meet the information needs of its intended users or be misunderstood. The guide’s example is a security monitoring provider whose customers’ own consumers could not read the report in context. Management and the auditor may then agree to restrict use to the customers who can.Who may use a given SOC 3 is settled engagement by engagement. Look in the auditor’s report for a statement limiting use.
2.193A SOC 3 gives no account of what a carved-out subservice organization does for the service organization, which a SOC 2 does. The carve-out method is permitted, but the guide says to consider whether it may be misleading. The boundary disclosures may supply enough. If they do not, the report may need restricting to a subset of readers, such as user entities that have a SOC 2 or SOC 3 from the subservice organization.If the boundaries name a cloud host or other provider as outside the examination and say nothing about how it bears on the service commitments, ask the vendor, or ask for the SOC 2.
2.194A SOC 3 that says customer-side controls (complementary user entity controls) are needed may be misunderstood without a system description. The auditor may consider restricting it to readers who have detailed communications about those controls.If the report says controls on your side are needed and does not say which, ask for the SOC 2 or the vendor’s description of them.
4.121 to 4.123The assertion, or an exhibit to it, should disclose the system boundaries and the principal service commitments and system requirements. Typical boundary disclosures include customer-side controls, controls assumed at subservice organizations, whether each subservice organization is carved out or included, and anything else that helps readers see the limits of the examination and opinion. If management leaves these out, the auditor would ordinarily restrict use to readers who already know the boundaries, which in most situations means the service organization and its board of directors.A SOC 3 that is silent on subservice organizations and customer-side controls, while the product plainly uses them, is a question for the vendor.

Read the assertion’s boundary section first. A vendor that posts a SOC 3 for a platform built on a public cloud should say which parts of the service the examination covers and how it treats the cloud provider. If you are the one commissioning a SOC 3, ask your firm at the proposal stage how it will present subservice organizations and customer-side controls, and whether it expects to restrict use.

Source: AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization (October 2022 edition), paragraphs 1.15, 1.73 to 1.75, 2.192 to 2.194 and 4.121 to 4.123, read October 21, 2026.

Who issues SOC 3 reports?

A licensed CPA firm issues a SOC 3, usually the same firm that performs the SOC 2. 60 of the 187 audit firms in our directory list SOC 3 among their services. A firm with no recorded service list may still issue one, so ask when you request a SOC 2 proposal.


If you need a SOC 2 report, with or without a SOC 3, compare audit firms by scope, price, timeline, and industry experience before requesting quotes.