Follow your buyers. If you sell into North America, SOC 2 is what procurement expects; if you sell into the UK or Europe, ISO 27001 is; if you sell into both, you will most likely end up holding both. The deeper difference is mechanical: ISO 27001 ends in a certificate with a number that anyone can verify, while SOC 2 ends in an attestation report that someone has to sit down and read.
| Criterion | ISO 27001 | SOC 2 |
|---|---|---|
| What you receive | A certificate from an accredited certification body | An attestation report from an independent CPA firm |
| Governing body | ISO/IEC | AICPA |
| How it works | Prescriptive management system (an ISMS) with Annex A reference controls | Criteria-based: you select controls that meet the Trust Services Criteria |
| Minimum scope | Your defined ISMS scope | Security (the common criteria) is always included; the other four categories are optional scope choices |
| Strongest market | UK and Europe | North America |
| Renewal shape | Three-year certificate cycle with surveillance audits | Annual examination is the market norm |
Why listen to us: Atoro is an Irish AI governance and cyber compliance consultancy for software companies, and the first consultancy in Europe certified against ISO/IEC 42001 (certificate AIMS-AT-120224, issued by A-LIGN under ANAB accreditation). Atoro.io states more than 200 certifications delivered (atoro.io, checked 08-08-2026). We prepare software companies for both regimes, so we see which artefact actually unblocks which deal.
Criterion 1: certification vs attestation (what your buyer actually receives)
This is the difference that decides deals, and the one most comparison pages get wrong. ISO 27001 is a certification: an accredited certification body audits your information security management system and issues a certificate with a registration number, which any buyer can verify independently, including through IAF CertSearch, the international accreditation forum’s public certificate database [1][7]. SOC 2 is not a certification at all. It is an attestation: an independent CPA firm examines your controls under the AICPA’s attestation standards (AT-C section 105 and AT-C section 205) and issues a report containing its opinion [2]. There is no SOC 2 certificate, no register and no number to check.
The procurement consequence matters more than the terminology. A certificate gets verified in seconds: a security or legal team types the number into a database and moves on. A SOC 2 report has to be read. It contains the auditor’s opinion, management’s description of the system, the controls the auditor tested and the results of those tests [2]. Someone on the buyer’s side has to check the opinion, weigh any exceptions and decide whether the report covers what they care about. Neither artefact is better in the abstract; they simply make different demands on the person doing the checking.
Straight verdict: if your buyer’s security review runs on verifiable registers and tick-box supplier lists, the ISO 27001 certificate is the easier artefact for them to process. If it runs on security engineers reading evidence, the SOC 2 report gives them more to work with.
Criterion 2: prescriptive standard vs criteria-based framework (who chooses your controls)
ISO 27001 is the prescriptive one. ISO/IEC 27001:2022 specifies the management system you must build (context of the organisation, leadership, planning, support, operation, performance evaluation, improvement) and points to Annex A’s 93 reference controls organised in four themes [1]. You must scope the system, run a risk assessment, produce a Statement of Applicability explaining which Annex A controls you have adopted and why, and keep the whole system audited, reviewed and improved [1]. The shape of the work is defined for you.
SOC 2 prescribes almost nothing. The AICPA publishes criteria, not controls: the Trust Services Criteria are, in the AICPA’s own words, “outcome-based criteria designed to be used when evaluating whether a system and related controls are effective” [4]. Security (the common criteria, the CC1 to CC9 series) is included in every SOC 2 examination; the other four categories (availability, processing integrity, confidentiality and privacy) are optional scope choices you make with your auditor [2]. The accompanying points of focus are guidance, not requirements: the AICPA states that using the criteria “does not require an assessment of whether each point of focus is addressed” [2]. Your company identifies the controls that meet the criteria, and the auditor judges whether they do.
Straight verdict: if you want a defined structure to build against, ISO 27001 hands you one. SOC 2 gives you more freedom and, with it, more judgement calls about scope and control design.
Criterion 3: geography (where each artefact carries weight)
The working rule of thumb: sell into North America and you need SOC 2; sell into the UK or Europe and you need ISO 27001; sell into both and you will likely need both. The reason is not geography for its own sake but the procurement mechanics in criterion 1. Each market’s enterprise security teams built their vendor-review habits around one artefact, and they ask for the one they know how to process. For the UK and Ireland version of this question, including who actually performs SOC 2 examinations for Irish and British companies, see our dedicated guide: SOC 2 for UK and Ireland companies.
Straight verdict: let your pipeline, not your preference, pick the framework.
Criterion 4: audit mechanics and cadence (what living with each one feels like)
ISO 27001 runs on a certificate cycle. Certification involves a formal audit by the certification body, after which the certificate is maintained across a three-year cycle with surveillance audits in between; the heavy cost lands in the certification year and the in-between years are lighter [5][6]. The certificate stays valid as long as surveillance keeps passing.
SOC 2 runs on an annual examination rhythm, and it comes in two types. A Type 1 report covers the suitability of the design of your controls; it contains no opinion on operating effectiveness and no detailed description of the auditor’s tests [2]. A Type 2 report covers both design and operating effectiveness “throughout a specified period”, and includes the detailed tests of controls and their results [2]. Because a Type 2 opinion covers a defined period, the report ages: buyers want a current one, which is why the examination recurs every year. In practice, companies treat Type 1 as a stepping stone and Type 2 as the artefact procurement means when it asks for “your SOC 2”.
Straight verdict: ISO 27001 concentrates effort into a certification year and then maintains; SOC 2 Type 2 is a yearly discipline. Plan budget and team capacity accordingly.
Criterion 5: cost shape
One honest structural point, no invented figures. SOC 2’s cost is an annual examination fee that recurs every year, because the report ages out; ISO 27001’s cost concentrates in the certification year, with lighter surveillance years across the three-year certificate cycle [5][6]. Everything beyond that shape depends on scope, readiness and provider. For sourced SOC 2 fee figures, including CPA examination fees and the readiness and platform costs around them, see our SOC 2 certification cost guide.
Who ISO 27001 is really for
ISO 27001 is for software companies whose buyers sit in the UK, Europe or other ISO-fluent markets, and for companies that want a defined management system rather than an open-ended criteria exercise. It suits teams that would rather be handed a structure (clauses, risk assessment, Statement of Applicability, Annex A reference controls) and build to it. If an enterprise prospect’s supplier onboarding asks for a certificate number, this is the artefact that answers it.
Who SOC 2 is really for
SOC 2 is for software companies selling into North America, where “send us your SOC 2” is a standard line in enterprise security review. It suits companies whose buyers have security teams that will genuinely read a report, and companies that want the freedom to design controls around their own systems and commitments rather than adopt a prescribed list. Because Security is the only mandatory category, it also suits companies that want to start narrow and add availability, confidentiality or privacy later as customers ask [2].
The question underneath the comparison
You are not really choosing between two security standards. The day-to-day security work underneath both is substantially the same, which is why the AICPA itself publishes an official mapping of the 2017 Trust Services Criteria to ISO 27001 [3]. Note what that mapping is and is not: it exists, and the AICPA lists it publicly, but the AICPA publishes no statement that the two frameworks are equivalent or interchangeable [3][6]. Treat any precise overlap percentage you see quoted online with caution; none of the figures circulating in vendor content trace to a source [6].
The real decision is which artefact unblocks your next deals. That is a pipeline question: where your buyers are, how their procurement teams verify vendors, and which document they were trained to trust. Answer that, and the framework choice makes itself. Sequencing matters too: if both markets are on your roadmap within a couple of years, build the security work once so the second engagement reuses it.
The honest next step is a scoping conversation about who is asking, which market your pipeline depends on, and what you already have in place. Atoro’s SOC 2 implementation service covers readiness, control design and evidence preparation for the examination; if ISO 27001 is the artefact your buyers want, the same conversation applies to that path.
FAQs
Is SOC 2 a certification?
No. SOC 2 is an attestation: an independent CPA firm examines your controls under the AICPA’s attestation standards and issues a report containing its opinion [2]. ISO 27001, by contrast, is a certification issued by an accredited certification body. Any provider selling “SOC 2 certification” is misdescribing the product, and that is worth treating as a warning sign.
Do we need both ISO 27001 and SOC 2?
If you sell at enterprise level into both sides of the Atlantic, most likely yes, eventually. Which artefact each market expects is set out in criterion 3 above; for the UK and Ireland version of the question, see our guide to SOC 2 for UK and Ireland companies. Companies selling into only one of those markets can usually hold only one.
Which should we do first, ISO 27001 or SOC 2?
Follow the revenue: do first whichever framework your current pipeline’s buyers are asking for. The underlying security work carries over heavily between the two, so the first one is the expensive one and the second reuses much of it. If neither side is asking yet, the market you are building towards is the tiebreaker.
Is SOC 2 recognised in the UK and Europe?
Yes, particularly among US-headquartered buyers and their European subsidiaries, and familiarity is growing. Whether a SOC 2 report alone will satisfy a given supplier review follows the geography rule in criterion 3 above. The UK and Ireland specifics are covered in our guide to SOC 2 for UK and Ireland companies.
How much do ISO 27001 and SOC 2 overlap?
Substantially, in practical security work, which is why the AICPA publishes an official mapping of the 2017 Trust Services Criteria to ISO 27001 [3]. Be wary of precise percentages: wildly inconsistent overlap figures circulate in vendor content and none of them cite a source [6]. Whatever you reuse, each engagement still demands its own evidence and its own external examination.
What is the difference between SOC 2 Type 1 and Type 2?
A Type 1 report covers whether your controls are suitably designed; it contains no opinion on operating effectiveness and no detailed description of the auditor’s tests [2]. A Type 2 report covers design and operating effectiveness over a specified period and includes the tests and their results [2]. When procurement asks for “your SOC 2”, it almost always means a current Type 2.
Which costs more, ISO 27001 or SOC 2?
The cost shapes differ more than the totals. SOC 2’s examination fee recurs every year because the report ages; ISO 27001’s cost concentrates in the certification year, with lighter surveillance years across the three-year cycle [5][6]. For sourced SOC 2 figures, see our SOC 2 certification cost guide; we publish no Atoro pricing.
Can one provider do both engagements for us?
Your company can build the readiness work, controls and evidence once and reuse them across both, and a consultancy can prepare you for both. The external engagements themselves are structurally separate: SOC 2 must be performed by a CPA firm under attestation standards, while ISO 27001 must be certified by an accredited certification body [1][2].
Sources
[1] ISO, “ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection: Information security management systems: Requirements” (tier 1, ISO standard page; management-system structure and Annex A as cited in prior verified programme page G11, fetched 08-08-2026): https://www.iso.org/standard/27001
[2] AICPA, TSP section 100, “2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (With Revised Points of Focus – 2022)” (tier 1, AICPA document text, accessed 19-08-2026 via the programme’s tier 1 record, research/R26-soc2-controls-primary-sources.md; attestation under AT-C 105 and AT-C 205 per par. .20-.22; common criteria applied regardless of scope per par. .07-.08; points of focus not individually required per par. .03-.04; Type 1/Type 2 distinction per par. .11): https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022
[3] AICPA, “Mapping: 2017 Trust Services Criteria to ISO 27001” (tier 1, aicpa-cima.com listing dated May 4, 2018, accessed 19-08-2026 via research/R26-soc2-controls-primary-sources.md; existence and scope statement verified, contents are AICPA member access and are NOT characterised here): https://www.aicpa-cima.com/resources/download/mapping-2017-trust-services-criteria-to-iso-27001
[4] AICPA, “Get mappings relevant to the SOC suite of services” (tier 1, aicpa-cima.com, dated Jan 22, 2020, accessed 19-08-2026 via research/R26-soc2-controls-primary-sources.md; source of the “outcome-based criteria” description): https://www.aicpa-cima.com/resources/article/get-mappings-relevant-to-the-soc-suite-of-services
[5] Programme brief for G23 (Writer_S9_G23 task instructions, slate 9): cost-shape framing authorised as “annual examination vs three-year certificate cycle”; Atoro supplied facts per the master brief.
[6] Research record research/R27-soc2-cluster-serp-map.md (19-08-2026): SERP overlap percentages recorded as unattributed ranker claims (not restated here per the slate 9 page rules); procurement-mechanics framing (verifiable certificate number vs report someone must read) identified as the strongest honest angle; no AICPA equivalency statement found (R26 FLAG 6).
[7] IAF CertSearch, International Accreditation Forum certificate verification database (tier 1, accreditation-body tool; referenced in prior verified programme research, research/R7-iso42001-market-state.md and G11): https://iafcertsearch.org
Atoro supplied facts (master brief): Irish AI governance and cyber compliance consultancy for software companies; first consultancy in Europe certified against ISO/IEC 42001 (certificate AIMS-AT-120224, A-LIGN under ANAB); “more than 200 certifications delivered” (atoro.io, checked 08-08-2026).