ISO 27001 vs SOC 2: Which Certification Does Your Company Need?
Two Standards, One Question
Nearly every B2B technology company eventually faces the same question from a prospect's security team: "Do you have ISO 27001 or SOC 2?" The answer can decide whether a deal closes on time or stalls in a procurement review for another quarter. But choosing between the two standards — or deciding to pursue both — requires understanding what each one actually delivers, how it is assessed, and which buyers expect it.
This guide breaks down the practical differences from the perspective of an auditor's chair: scope, the certification-versus-attestation distinction, the structure of the requirements, how the audits run, and how to decide based on your market rather than on marketing claims.
What Is ISO 27001?
ISO/IEC 27001 is an international standard for an information security management system (ISMS), published jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). The current edition is ISO/IEC 27001:2022. Rather than prescribing a fixed checklist, it sets out the requirements for building and running a governed system to manage information security risk.
The defining word is system. ISO 27001 expects you to identify risks, decide how to treat them, implement controls, measure whether they work, and improve continuously. That improvement loop is not optional flavour text — it is a formal requirement. Clause 10 of the standard, Continual improvement, states that "the organization shall continually improve the suitability, adequacy and effectiveness of the information security management system," and its companion clause on nonconformity and corrective action requires you to react to issues, find their root causes, fix them, and keep documented evidence of what happened and what you did about it. In other words, a one-off effort to "pass" does not satisfy the standard; the system has to live and adapt.
Alongside the management-system clauses, ISO 27001 includes Annex A, a normative reference set of information security controls. Annex A is directly derived from and aligned with ISO/IEC 27002:2022, Clauses 5 to 8, and the controls are organised into four themes:
- Organizational controls
- People controls
- Physical controls
- Technological controls
Crucially, you do not blindly apply every control. Annex A is used "in context with" the risk-treatment requirements of the standard — organisations select the applicable controls based on their own risk assessment and justify inclusions and exclusions in a Statement of Applicability. A small SaaS company and a multinational bank will arrive at very different control sets from the same Annex.
What Is SOC 2?
SOC 2 (System and Organization Controls 2) is an attestation framework governed by the American Institute of Certified Public Accountants (AICPA). Where ISO 27001 certifies that you run a conforming management system, SOC 2 produces an independent report in which a licensed practitioner gives an opinion on whether your controls meet a defined set of criteria.
Those criteria are the Trust Services Criteria, organised into five categories:
- Security
- Availability
- Processing Integrity
- Confidentiality
- Privacy
A SOC 2 engagement can address one or more of these categories, individually or in combination. The criteria were deliberately designed to be flexible across different subject matters, which is why two SOC 2 reports from different companies can cover quite different scopes.
There are two report types, and the distinction matters:
- Type 1 addresses the suitability of the design of controls. A Type 1 report does not contain an opinion on the operating effectiveness of controls, nor a detailed description of the tests the auditor performed or their results.
- Type 2 covers the suitability of design and the operating effectiveness of controls throughout a specified period. A Type 2 report includes the auditor's opinion on operating effectiveness, a detailed description of the tests of controls performed, and the results of those tests.
This is why most enterprise customers ask specifically for SOC 2 Type 2: a point-in-time design assessment tells them your controls exist, but a Type 2 report demonstrates they actually operated over a meaningful window of time.
(For completeness, the same Trust Services Criteria also underpin a SOC 3 report, which carries an opinion on operating effectiveness but omits the detailed test descriptions and results — making it a general-distribution, marketing-friendly document rather than the detailed report a security reviewer will demand.)
Key Differences
Scope and Structure
ISO 27001 is a management-system standard. The centre of gravity is governance: a documented, risk-driven, continuously improving ISMS, with leadership accountability and a built-in corrective-action discipline. Controls (Annex A) sit inside that system and are selected by risk.
SOC 2 is a controls attestation against the Trust Services Criteria. There is no formal requirement to operate a named, certified management system — though in practice you need disciplined, documented processes to pass, because a Type 2 auditor tests whether controls operated consistently across the review period.
Certification vs. Attestation
This is the cleanest way to remember the difference. ISO 27001 results in a certificate — a formal statement, issued by an accredited certification body, that your ISMS conforms to the standard. It is short, public, and easy to share with anyone who asks.
SOC 2 results in an attestation report — a detailed document containing the practitioner's opinion, a description of your system, and (for Type 2) the controls tested and the results of those tests. Because it exposes detailed information about how your security actually works, a SOC 2 report is typically shared under NDA rather than published.
Geographic and Market Recognition
ISO 27001 is recognised internationally and tends to be the common language for organisations whose customers span Europe, the Middle East, Asia-Pacific, and beyond. Where regulators or large buyers specify a named standard, ISO 27001 is frequently the one.
SOC 2 is predominantly a North American expectation. US enterprise buyers — especially in technology and financial services — often treat a SOC 2 Type 2 report as the baseline before they will move a vendor forward.
Audit Process and Cadence
ISO 27001 certification is performed by an accredited certification body, typically as a two-stage initial audit (a documentation and readiness review, followed by an on-site assessment of how the ISMS operates in practice). Certification is then maintained over an ongoing cycle through periodic surveillance and recertification activity — reflecting the standard's continual-improvement requirement. The exact cycle length and surveillance frequency are governed by the relevant accreditation and certification rules, so confirm specifics with your certification body rather than assuming a fixed number.
SOC 2 examinations are performed by a licensed CPA firm following AICPA standards. A Type 2 engagement assesses controls across a defined review period and reports the tests performed and their results. Because companies usually want continuous coverage for their customers, SOC 2 reporting is generally treated as a recurring exercise covering successive periods.
Comparison at a Glance
| Dimension | ISO/IEC 27001:2022 | SOC 2 |
|---|---|---|
| Type of result | Certificate (conformity) | Attestation report (auditor's opinion) |
| Governing body | ISO / IEC | AICPA |
| Core concept | Information security management system (ISMS) | Controls assessed against Trust Services Criteria |
| Criteria / structure | Management-system clauses + Annex A controls (Organizational, People, Physical, Technological) | Security, Availability, Processing Integrity, Confidentiality, Privacy |
| Control selection | Risk-based; documented in Statement of Applicability | Categories chosen by scope; Security always central |
| Point-in-time vs. over-time | System assessed and maintained over a cycle | Type 1 = design only; Type 2 = design + operating effectiveness over a period |
| Who performs it | Accredited certification body | Licensed CPA firm |
| Sharing | Public certificate | Detailed report, usually under NDA |
| Primary market signal | International | Predominantly North American |
Who Needs Which?
Lean towards ISO 27001 if:
- Your customers are primarily outside North America.
- You want a globally recognised credential you can share openly.
- You value a framework that institutionalises continuous security improvement.
- A regulator, partner, or large buyer specifically names ISO 27001.
Lean towards SOC 2 if:
- Your customers are primarily US-based enterprises.
- You are a SaaS provider selling into US technology or financial services.
- Prospects are explicitly asking for a SOC 2 Type 2 report.
- You need to demonstrate that controls operated effectively over time, not just that they were designed.
Pursue both if:
- You sell globally and face buyers on both sides of the Atlantic.
- Different deals stall on different credentials depending on the prospect.
- You want the strongest possible security posture to differentiate in competitive procurement.
Pursuing Both: The Efficient Path
ISO 27001 and SOC 2 are different in form but share a great deal of substance. Access control, change management, incident response, vendor risk, logging and monitoring, business continuity — the same underlying control disciplines surface in ISO 27001's Annex A themes and in the SOC 2 Trust Services Criteria. Treating the two programmes as one well-mapped effort, rather than two parallel projects, avoids re-doing the same work twice.
At Mölnir, we approach dual programmes through unified control mapping:
- Build the ISMS first. ISO 27001's management system gives you the governance, risk-treatment, and corrective-action backbone that both credentials lean on.
- Map controls across both frameworks. Identify where a single, well-designed control satisfies an Annex A objective and a Trust Services Criterion, so you are managing one control rather than two.
- Collect evidence once. Design evidence artefacts — policies, tickets, logs, reviews — so a single artefact serves both the certification body and the CPA firm.
- Sequence the audits sensibly. A mature ISO 27001 control environment becomes the foundation the SOC 2 examiner tests, reducing duplicated readiness work.
The savings come from eliminating redundant evidence collection and remediation, not from cutting corners — every control still has to genuinely work, because under SOC 2 Type 2 an auditor will test whether it operated across the whole period.
Frequently Asked Questions
Is SOC 2 a certification? No. SOC 2 produces an attestation report with an auditor's opinion, not a certificate. ISO 27001 is the one that yields a formal certificate of conformity.
Should I get SOC 2 Type 1 or Type 2? Most enterprise customers want Type 2, because it includes an opinion on whether controls operated effectively over a period, along with the tests performed and their results. A Type 1 report only covers the design of controls at a point in time and is sometimes used as an interim step on the way to a Type 2.
Does ISO 27001 require me to implement every Annex A control? No. Annex A controls are applied in context with your risk assessment and treatment. You select applicable controls and document your reasoning — typically in a Statement of Applicability — so the control set reflects your actual risk, not a universal checklist.
Which one should I get first if I have to choose? If buyers are already asking for a specific credential, get that one — the right certification is the one your market requires. If no one is asking yet and you want to get ahead, ISO 27001 builds a management-system foundation that later supports a SOC 2 examination efficiently.
Can one programme cover both? To a large degree, yes, through unified control mapping and shared evidence — the management system and many underlying controls overlap, so a coordinated programme avoids running two disconnected projects.
The Takeaway
ISO 27001 certifies that you run a governed, continuously improving security management system; SOC 2 attests, through an auditor's opinion, that your controls meet the Trust Services Criteria — and, in a Type 2 report, that they operated effectively over time. ISO 27001 tends to be the international common language; SOC 2 is the credential US enterprises most often expect. They overlap enough in substance that, with disciplined control mapping, pursuing both does not mean doing everything twice.
The worst choice is no choice. Every quarter without a recognised security credential is a quarter of deals slowed by security questionnaires and trust claims your prospects cannot verify.
Mölnir guides organisations through ISO 27001, SOC 2, and combined certification programmes — from initial gap assessment through to a successful audit, with control mapping that removes redundant work. Discuss your certification strategy with Mölnir.