BlogSOC 1 vs SOC 2 (and SOC 3): which report do your clients need?
Trust

SOC 1 vs SOC 2 (and SOC 3): which report do your clients need?

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.

Harry WestFounder & CEO7 June 20248 min read
Inside This Article
SOC 1 vs SOC 2: what is the difference?When do you need a SOC 1 report?When do you need a SOC 2 report?Do you need both SOC 1 and SOC 2?Is a SOC 3 report enough instead of SOC 2?How does ISAE 3402 compare with SOC 1?How should you answer a client who asks for "a SOC report"?Frequently asked questions
Get The Pulse

Key takeaways

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.

SOC 1 report
An examination of controls at a service organisation that are likely to be relevant to clients' internal control over financial reporting, written for those clients and the auditors of their financial statements.
SOC 2 report
A CPA's report on controls relevant to security, availability, processing integrity, confidentiality or privacy, detailed enough for vendor risk management and restricted to specified parties.
SOC 3 report
A general use report on the same subject matter as SOC 2, without the auditor's tests and results and with a less detailed system description, so it can be freely distributed.
ISAE 3402
The IAASB's international standard, issued in December 2009, for Type 1 and Type 2 assurance reports on service organisation controls relevant to user entities' financial reporting.

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 vs SOC 2: what is the difference?

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 onSOC 1SOC 2SOC 3
What it coversControls likely to be relevant to clients' internal control over financial reportingControls relevant to security, availability, processing integrity, confidentiality or privacyThe same subject matter as SOC 2, in less detail
Standard and criteriaAICPA attestation standards (SSAE 18, AT-C section 320), tested against the control objectives in your system descriptionAICPA attestation standards, tested against the Trust Services CriteriaAICPA attestation standards, tested against the Trust Services Criteria
Who reads itYour clients and the auditors of their financial statementsYour clients' security, risk and procurement teamsAnyone: prospects, the public, your website visitors
DistributionRestricted to your management, clients and their auditorsRestricted to specified partiesGeneral use; can be freely distributed
Type 1 and Type 2Both availableBoth availableOne report on design and operation; no tests or results shown
International or UK counterpartISAE 3402, issued by the IAASBISAE 3000 (Revised) assurance reportsNo 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.

When do you need a SOC 1 report?

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:

  • Payroll processing, where your calculations become the client's salary costs and tax liabilities.
  • Billing and invoicing platforms, whose output becomes the client's revenue and receivables.
  • Payments and treasury services, including fintech platforms that move or reconcile client money.
  • Fund, pensions or claims administration, where your records drive the client's reported positions.
  • Any platform whose output feeds client ledgers, such as expense or accounting integrations.
  • US-listed clients. Section 404(b) of the Sarbanes-Oxley Act, as the AICPA explains, "requires the independent auditor of a public company to attest to, and report on, management's assessment" of its internal accounting controls. Smaller and newly listed companies are exempt from that auditor attestation, as the SEC sets out, but their auditors still consider internal control in the financial statement audit. Either way, your controls may sit inside that work.

A SOC 1 report is written for an auditor. Our SOC 1 glossary entry explains the engagement itself.

When do you need a SOC 2 report?

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 security questionnaire or due-diligence pack from a US or enterprise prospect that asks for an independent controls report.
  • SaaS products that host or process client data, where the buyer's security team owns the review.
  • Data processing and managed services, where confidentiality or availability is written into the contract.
  • A procurement gate that names SOC 2 as a condition of signing or renewal.

A SOC 2 report answers the client's security team. It says nothing to the client's auditor about the accuracy of the numbers.

Do you need both SOC 1 and SOC 2?

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:

  • The system description. Both reports start from management's description of the service, its components and its boundaries.
  • The report types. Both come as a Type 1 (design at a date) or a Type 2 (operation across a period), so you can align the periods.
  • Shared controls. Controls over access to and changes in the systems that process client data can serve SOC 1 control objectives and the SOC 2 criteria at the same time.
  • Your evidence habits. Records that show a control ran across the period are tested the same way in both.

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.

Is a SOC 3 report enough instead of SOC 2?

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.

How does ISAE 3402 compare with SOC 1?

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.

How should you answer a client who asks for "a SOC report"?

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.

Frequently asked questions

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.

Profile image for Harry West, Founder and CEO of GRCMANA
Author

Harry West

Harry is the founder of GRCMANA, he helps regulated service providers close the enterprise trust gap — turning GRC, cyber resilience and AI governance from paperwork exercises into shippable systems.

GRCMANA
  • About
  • Insights
  • Contact
Ask the Trust ArchitectJoin the GRC Pulse
  • About
  • Insights
  • The Vault
    Compliance VaultCyber Essentials→ISO 27001→SOC 2→ISO 42001→
    Domain VaultGRC Fundamentals→Risk Management→AI Governance→GRC Engineering→
    Other ResourcesFree Tools→Templates→Newsletter→
  • Contact
Join the GRC PulseAsk the Trust ArchitectFixed fee. ISO 27001 in as few as six weeks.
GRCMANA

Helping high-growth B2B tech startups close the Enterprise Trust Gap through security, governance, and AI resilience.

ISO 27001ISO 42001ISO 9001Cyber EssentialsEU AI Act ReadyNIST AI RMF

The Vault

GRC EngineeringAI GovernanceISO 27001ISO 42001All Vault Resources

Resources

BlogFree ToolsTemplatesNewsletter

Company

About GRCMANAContactPrivacy PolicyTerms & ConditionsCookie Policy
© 2025 GRCMANA · All rights reservedRegistered in England & Wales under company registration 16810805. VAT Registration 506308024