---
title: "ISO 27001 vs SOC 2: which one do your customers need?"
canonical: https://www.grcmana.io/blog/iso-27001-vs-soc-2
published: 2024-07-22
updated: 2026-10-22
authors: ["Harry West"]
---

# ISO 27001 vs SOC 2: which one do your customers need?

## Key takeaways

ISO 27001 is a certificate for an information security management system, issued by an accredited certification body; SOC 2 is an attestation report on controls, signed by a licensed CPA firm. UK firms should get ISO 27001 for UK, European and regulated buyers, and add SOC 2 when US enterprise customers make it a contract condition. An existing ISMS carries much of the SOC 2 groundwork, but not the system description or Type 2 period evidence.

- **Certificate vs attestation** — ISO 27001 certification comes from a certification body that UKAS, the government-appointed UK accreditation body, accredits. SOC 2 is a CPA examination under the AICPA's attestation standards, with no certificate.
- **Who can sign a SOC 2** — The AICPA's Journal of Accountancy notes that SOC engagements are required under US state law to be performed by licensed CPAs, so a UK firm without that licence cannot sign one.
- **ISAE 3000 route** — Some UK firms report on the Trust Services Criteria under ISAE 3000. ICAEW calls the AICPA attestation standards broadly equivalent to the international ones, but the report is not a SOC 2.
- **UK legal position** — No UK law mandates ISO 27001 or SOC 2. UK GDPR Article 32 requires appropriate security measures without naming a standard, and PPN 014 names Cyber Essentials for certain government contracts.

A US prospect has asked for your SOC 2 report, and your ISO 27001 certificate has not settled the question. For UK founders, COOs and security leads, ISO 27001 vs SOC 2 is a decision about which customers you sell to, not a contest between two standards.

The verdict: get ISO 27001 if your customers are mainly in the UK, Europe or regulated sectors, add SOC 2 when US enterprise customers make it a contract condition, and if you sell into both, expect to hold both, built on one set of controls.

This page sets out how the two differ, the triggers for each, and what an existing management system carries into a SOC 2. For the basics of each framework, start with our [ISO 27001 hub](https://www.grcmana.io/vault/iso-27001) and [SOC 2 hub](https://www.grcmana.io/vault/soc-2).

## ISO 27001 vs SOC 2: what is the difference?

ISO 27001 is a certifiable standard for an information security management system: an accredited certification body audits your system against it and issues a certificate. SOC 2 is an attestation report: a licensed CPA firm examines your controls against the AICPA's Trust Services Criteria and gives a written opinion.

The UK accreditation body, UKAS, puts the ISO side plainly. Certification bodies are "the checkers", and UKAS, as the "government-appointed National Accreditation Body", checks them, as set out in its [guide to accreditation and certification](https://www.ukas.com/accreditation/about/accreditation-vs-certification/).

SOC 2 sits outside that structure. The AICPA's Journal of Accountancy describes SOC reports as [examinations performed by CPAs](https://www.journalofaccountancy.com/issues/2026/feb/promises-of-fast-and-easy-threaten-soc-credibility/) under the AICPA's attestation standards, restricted to specified parties.

| Compared on | ISO 27001 | SOC 2 |
| --- | --- | --- |
| What you receive | A certificate that anyone can check | An attestation report, shared privately under the report's use restrictions |
| Who issues it | A certification body, accredited in the UK by UKAS | A licensed CPA firm, under AICPA attestation standards |
| What it is tested against | The requirements of the ISO/IEC 27001 standard for a management system | The AICPA Trust Services Criteria, chosen by category |
| What the scope covers | The management system: risk process, policies, leadership and the controls you select | A defined system and its controls, set out in a system description you write |
| How the audit runs | A certificate on a multi-year cycle, with surveillance audits in between | Type 1 at a single date, or Type 2 across a period you agree with the auditor |
| Who usually asks for it | UK, European and regulated buyers, and public-sector procurement | US enterprise security and procurement teams |
| The UK position | Recognised widely, with UKAS-accredited certification bodies based in the UK | A US framework; only a licensed CPA firm can sign the report |

A certificate tells a buyer the system was checked. A SOC 2 report shows them how it runs.

Neither is the stronger test in every respect. ISO 27001 examines how you govern security; a SOC 2 Type 2 tests how controls operated over a period, control by control. Our [SOC 2 Type 1 vs Type 2 guide](https://www.grcmana.io/vault/soc-2/type-1-vs-type-2) explains that split.

## When should you choose ISO 27001?

Choose ISO 27001 when your customers are mainly in the UK or Europe, when they work in regulated sectors such as financial services or insurance, or when tenders ask for a certificate by name. ISO 27001 is the proof most UK and European buyers expect, and a buyer can confirm a certificate from an accredited body.

The triggers are concrete. ISO 27001 comes first when most of these are true:

- **Who is asking.** A UK or European enterprise customer, or a regulated firm running outsourcing due diligence on you.
- **What the contract says.** The tender or supplier questionnaire asks for ISO 27001 certification, or for "an accredited certificate".
- **Where you are going.** Your pipeline is mostly UK and European, and US deals are occasional.
- **What you want to build.** You want a management system that keeps working between audits, not only a report for one buyer.

The order and timing of the audits are set out in our [ISO 27001 certification process guide](https://www.grcmana.io/vault/iso-27001/certification-process).

The standard asks you to run security as a system, with risk decisions, owners and reviews, and that system is what the rest of this page builds on.

## When should you choose SOC 2?

Choose SOC 2 when a US enterprise customer makes it a contract condition, or when US revenue is a growth target and every new prospect will ask. A SOC 2 report is the document US security and procurement teams build their vendor reviews around, so it shortens those reviews in a way a certificate often cannot.

SOC 2 comes first, or alongside ISO 27001, when any of these apply:

- **Who is asking.** A US enterprise security team, or a buyer of any nationality whose vendor-risk process lists SOC 2 as a required document.
- **What the contract says.** It names SOC 2, SOC 2 Type 2, an AICPA report or a licensed CPA firm.
- **What the questionnaire wants.** It asks for the report period, the auditor's test results or exceptions, which only a Type 2 report contains.
- **Where you are going.** The US is a target market, so one report serves the next ten prospects, not just this one.

A certificate the buyer did not ask for does not unblock the deal.

How the examination itself runs, and who can perform it, is covered in our [SOC 2 audit guide](https://www.grcmana.io/vault/soc-2/audit).

## Will a US customer accept ISO 27001 instead of SOC 2?

Some US customers will accept ISO 27001 instead of SOC 2, usually when their requirement says "SOC 2 or equivalent" or asks for independent assurance without naming a standard. When the contract names SOC 2, an AICPA report or a licensed CPA firm, a certificate will not meet it. Ask the buyer in writing before you commit to either.

Three questions settle it:

1. Will you accept an ISO 27001 certificate from an accredited body in place of a SOC 2 report?
2. If not, must the report be a SOC 2 signed by a US-licensed CPA firm, or will an equivalent assurance report do?
3. Do you need design only, or operation over a period, and how long a period?

There is a middle route. Some UK assurance firms offer reports under ISAE 3000, the international assurance standard, tested against the same Trust Services Criteria. ICAEW's [assurance glossary](https://www.icaew.com/technical/audit-and-assurance/assurance/what-is-assurance/assurance-glossary) calls the AICPA's attestation standards "broadly equivalent" to the international ones. An ISAE 3000 report is not a SOC 2, though, so it only works where the buyer accepts an equivalent. Our [ISAE 3000 vs SOC 2 guide](https://www.grcmana.io/vault/soc-2/soc-2-vs-isae-3000) covers when it satisfies a buyer.

## What carries over from ISO 27001 to SOC 2?

Most of the groundwork carries over from ISO 27001 to SOC 2: the risk assessment, the policies, the named owners and many of the running controls, such as access reviews and change records. What SOC 2 adds is a system description written to AICPA criteria and, for a Type 2, evidence that each control operated across the whole period.

An ISO 27001 management system gives you three head starts:

- **Risk decisions on record.** A SOC 2 auditor wants to see that your controls answer real risks, and your risk register already shows that.
- **Policies with owners.** The governance a SOC 2 examination expects is already written, approved and reviewed.
- **Controls that leave records.** Controls that run on a cycle produce the evidence a Type 2 auditor samples.

Two things do not carry over. The first is the system description: SOC 2 asks you to describe the specific system in scope, and the auditor gives an opinion on whether that description is fairly presented. The second is time. A Type 2 period starts on the day you agree, and evidence from before it does not count.

An ISMS is a head start, not a SOC 2 report.

Where you hold ISO 27001 already, we recommend scoping the SOC 2 to the same services and reusing the same control owners, so one set of controls answers both auditors. The control-by-control mapping between the two belongs in a separate guide.

## Frequently asked questions

### Is ISO 27001 equivalent to SOC 2?

No. ISO 27001 certifies a management system against an international standard, while SOC 2 is a CPA's attestation report on controls against the AICPA Trust Services Criteria. Much of the underlying work overlaps, but the outputs differ, so a buyer who names one will not always accept the other.

### Is SOC 2 legally required?

No UK law requires a SOC 2 report. SOC 2 is requested by customers, usually through contracts and vendor-risk reviews, not imposed by a regulator. Once a signed contract names a SOC 2 report, providing it becomes a contract term, with whatever remedies that contract sets.

### Is ISO 27001 mandatory in the UK?

No. [UK GDPR Article 32](https://www.legislation.gov.uk/eur/2016/679/article/32) requires appropriate technical and organisational measures to protect personal data, but it does not name ISO 27001. Where UK government sets a cyber requirement for suppliers, the Cabinet Office's [PPN 014](https://www.gov.uk/government/publications/ppn-014-cyber-essentials-scheme/ppn-014-cyber-essentials-scheme-html) names Cyber Essentials for certain contracts, not ISO 27001. Customers may still require it by contract.

### Can a UK audit firm issue a SOC 2 report?

Only if the signing firm is a licensed CPA firm, because SOC engagements are attestation work that US state law reserves for licensed CPAs. A UK firm without that licence cannot sign one. Some UK firms offer an ISAE 3000 report on the Trust Services Criteria instead, which is not a SOC 2. Ask who will sign before you engage.
