If most of your customers are in the US, start with SOC 2. If they're in the UK or Europe, start with ISO 27001. Both prove you run a working information security program, and they overlap heavily — but buyers in each market ask for "their" standard by name. Many SaaS companies end up with both, and building them on one shared control set avoids doing the work twice.
What each one is
| SOC 2 | ISO/IEC 27001 | |
|---|---|---|
| Created by | AICPA (US) | ISO/IEC (international) |
| Output | Attestation report from a licensed CPA firm | Certificate from an accredited certification body |
| What it covers | Controls against the Trust Services Criteria | An Information Security Management System (ISMS) plus Annex A controls |
| Structure | Security criteria (CC1–CC9) + optional Availability, Confidentiality, Processing Integrity, Privacy | Clauses 4–10 + 93 Annex A controls in four themes (organisational, people, physical, technological) |
| Period | Type II covers an observation window | Three-year certificate cycle with annual surveillance audits |
| Strongest in | US B2B procurement | UK, EU and international procurement; UK public sector supply chains often pair it with Cyber Essentials |
The real difference: report vs certificate
A SOC 2 report is detailed. It describes your system, lists your controls and shows what the auditor tested and found — including any exceptions. US security teams like it because they can read exactly what was tested.
An ISO 27001 certificate is a pass/fail statement that your ISMS meets the standard, backed by a Statement of Applicability. It's simpler to share and widely recognised internationally, but gives buyers less detail on individual controls.
Which should you get first?
- Mostly US customers, enterprise sales → SOC 2 Type II
- Mostly UK/EU customers → ISO 27001
- UK public sector or supply chains → Cyber Essentials (or Cyber Essentials Plus) early, then ISO 27001
- Selling into both markets → start with the one blocking your biggest deals, design controls to satisfy both, and add the second within 6–12 months
How much overlaps?
A lot. Risk assessment, access control, change management, vendor management, incident response, logging and monitoring, backups and business continuity, HR security and training all appear in both. Most of the extra work for the second framework is:
- For ISO 27001 after SOC 2: the management-system layer — ISMS scope, Statement of Applicability, internal audit, management review, continual improvement — plus a few Annex A controls you may not have formalised.
- For SOC 2 after ISO 27001: the system description, mapping controls to the Trust Services Criteria, and producing evidence across the Type II observation window.
Build once, certify twice
- Write one policy set that covers both frameworks' requirements.
- Keep one control register mapped to both SOC 2 criteria and ISO 27001 Annex A.
- Collect evidence once and reuse it for both audits.
- Align audit timing so fieldwork doesn't hit the team twice in the same quarter.
Where AI fits
Neither SOC 2 nor ISO 27001 addresses AI-specific risks in depth. If you build AI products, ISO/IEC 42001 uses the same management-system structure as ISO 27001, so it slots in naturally on top. See SOC 2 vs ISO 42001.
FAQ
Is ISO 27001 accepted in the US?
Often, yes — especially by companies with international operations. But many US security teams still ask specifically for a SOC 2 report, so expect to be asked for it if US enterprise is your main market.
Is SOC 2 recognised in the UK?
Increasingly, particularly by tech companies and US-owned UK businesses. UK procurement teams still most commonly ask for ISO 27001 and, in the public sector, Cyber Essentials.
Which is cheaper?
It depends on scope and maturity. The bigger cost driver is usually the internal work to implement controls, not the audit itself — which is why building one shared control set for both saves the most.
Selling to both the US and UK? Book a free scoping call and we'll map the fastest path to both, or see our SOC 2 compliance service.