Which SOC report your client means: SOC 1 for their financial auditors, SOC 2 for their security team, SOC 3 for the public, ISAE 3402 abroad.
SOC 1 vs SOC 2 comes down to who reads the report. SOC 1 covers controls relevant to clients' financial reporting and is written for their auditors. SOC 2 covers security, availability, processing integrity, confidentiality or privacy and serves vendor risk reviews. SOC 3 is a freely distributable summary of SOC 2, not a substitute, and ISAE 3402 is the IAASB's international counterpart to SOC 1.
A US client's onboarding form asks for "your SOC report", and nobody on your side is sure whether that means SOC 1, SOC 2 or both. This SOC 1 vs SOC 2 comparison is for UK founders, COOs and finance or security leads at service providers who need to answer that request correctly the first time.
The verdict: get SOC 1 if your service affects your clients' financial reporting, get SOC 2 if they want assurance over security and data handling, and treat SOC 3 as a public summary of SOC 2, never a substitute. ISAE 3402 is the international counterpart to SOC 1.
Below you'll find the differences side by side, the triggers for each report, when you need both, and how to answer a client who just asks for "a SOC report". For what SOC 2 is and how its criteria work, start with our SOC 2 overview.
SOC 1 and SOC 2 are both attestation reports in which an independent CPA examines controls at a service organisation. SOC 1 covers controls relevant to your clients' internal control over financial reporting. SOC 2 covers controls relevant to security, availability, processing integrity, confidentiality or privacy. They answer different readers, not stronger and weaker versions of one question.
SOC now stands for System and Organization Controls, the AICPA's name for its suite of service offerings. The older name, "Service Organization Control", still turns up in questionnaires. Neither report is a certification.
| Compared on | SOC 1 | SOC 2 | SOC 3 |
|---|---|---|---|
| What it covers | Controls likely to be relevant to clients' internal control over financial reporting | Controls relevant to security, availability, processing integrity, confidentiality or privacy | The same subject matter as SOC 2, in less detail |
| Standard and criteria | AICPA attestation standards (SSAE 18, AT-C section 320), tested against the control objectives in your system description | AICPA attestation standards, tested against the Trust Services Criteria | AICPA attestation standards, tested against the Trust Services Criteria |
| Who reads it | Your clients and the auditors of their financial statements | Your clients' security, risk and procurement teams | Anyone: prospects, the public, your website visitors |
| Distribution | Restricted to your management, clients and their auditors | Restricted to specified parties | General use; can be freely distributed |
| Type 1 and Type 2 | Both available | Both available | One report on design and operation; no tests or results shown |
| International or UK counterpart | ISAE 3402, issued by the IAASB | ISAE 3000 (Revised) assurance reports | No direct equivalent |
The table rests on the AICPA's SOC 1 and SOC 3 pages and its Journal of Accountancy overview of the three SOC reports. If a client asks which Type you need, our SOC 2 Type 1 vs Type 2 guide covers that choice.
The number on the report matters less than the reader it is written for.
You need a SOC 1 report when your service feeds numbers into your clients' financial statements and their auditors rely on your controls. The AICPA describes SOC 1 as meeting the needs of user entities and the CPAs who audit their financial statements. If your output lands in a client's ledger, expect their auditor to ask for it.
Typical SOC 1 triggers for a UK provider:
A SOC 1 report is written for an auditor. Our SOC 1 glossary entry explains the engagement itself.
You need a SOC 2 report when a client wants independent assurance over how you protect their systems and data. The Journal of Accountancy notes that SOC 2 reports give "a level of detail sufficient to address the user's vendor risk management needs". For a UK SaaS or data-processing firm, this is often the report a deal turns on.
Typical SOC 2 triggers:
A SOC 2 report answers the client's security team. It says nothing to the client's auditor about the accuracy of the numbers.
You need both when your service touches clients' financial reporting and also holds data their security teams must review. A payroll or billing platform sold as SaaS is the common case: the finance auditor wants SOC 1, the security team wants SOC 2. The two reports share a structure, so much of the work carries over.
What carries over between the two:
What does not carry over is the frame. SOC 1 is tested against the financial-reporting control objectives in your description, and SOC 2 against the AICPA's Trust Services Criteria. We recommend scoping both at once, so one set of evidence serves two reports.
A SOC 3 report is not enough when a client's security team is reviewing you as a vendor. SOC 3 covers the same subject matter as SOC 2 but leaves out the auditor's tests and results. The AICPA calls it a general use report that can be freely distributed, which makes it a trust-centre asset.
Use a SOC 3 report for what it does well: a public signal on your website or trust centre, and an early answer for prospects who are not yet under NDA. When the deal reaches the vendor review, the security team will still ask for the SOC 2 report itself, because it needs the detail to judge how your controls affect its own risk.
A SOC 3 report on a website is a summary, not evidence a reviewer can test.
ISAE 3402 serves the same purpose as SOC 1 under international rather than US standards. The IAASB issued it in December 2009 for assurance reports on service organisation controls relevant to user entities' internal control over financial reporting. It offers the same Type 1 and Type 2 split.
The IAASB's staff overview of ISAE 3402 says it is effective for reports covering periods ending on or after 15 June 2011, and that its reports can provide evidence under ISA 402, the auditing standard for clients that use a service organisation. ICAEW lists ISAE 3402 as expanding on ISAE 3000 (Revised) for service organisation controls, alongside AAF 01/20, its own UK guidance for service auditors reporting on a service organisation's controls. Our ISAE 3402 glossary entry sets out the standard in full.
Which report should you commission? The difference is the rulebook and the practitioner. SOC 1 is performed by a CPA under AICPA standards; ISAE 3402 by a professional accountant in public practice under IAASB standards. Whether a US client's auditor will accept an ISAE 3402 report in place of SOC 1 is that auditor's decision, so ask before you commission.
If your clients sit on both sides of the Atlantic, ask your service auditor whether one engagement can report under both AT-C section 320 and ISAE 3402. The SOC 2 equivalent, ISAE 3000, is covered in our ISAE 3000 vs SOC 2 comparison.
Answer a request for "a SOC report" with three questions: who in the client will read it, what they need it for, and whether an international or UK equivalent would do. A finance or audit reader points to SOC 1 or ISAE 3402. A security or procurement reader points to SOC 2. A public-facing request points to SOC 3.
Put the questions in one email and keep the reply, because it fixes the scope before anyone pays for an examination. If you already hold ISO 27001, mention it in the same email: an ISO 27001 certificate does not replace a SOC 2 report, but it shows a security management system is already running, and much of its control set and evidence can feed a SOC 2.
The cheapest SOC report is the one that matches the reader who asked for it.
Only if your service affects your clients' financial reporting. A SOC 2 report covers security and related criteria, not the controls a client's financial auditor relies on. If you run payroll, billing or payments for a client, their auditor may still ask for SOC 1 or ISAE 3402, whatever SOC 2 report you hold.
No. The AICPA's SOC suite has SOC 1, SOC 2 and SOC 3 for service organisations, plus SOC for Cybersecurity and SOC for Supply Chain. A "SOC 4" in a questionnaire is usually a mistake for one of these, so ask which report the client actually means.
No. Both are attestation reports: a CPA's opinion on your controls under the AICPA's attestation standards, not a certificate. An AICPA vice president put it plainly in a 2026 Journal of Accountancy podcast: "SOC 2 is not a certification." The same applies to SOC 1, which is also an examination under the attestation standards.