If most of your customers are in Europe, start with ISO 27001: it is the certificate EU procurement, public buyers and NIS2-regulated companies recognise. If you sell mainly to US companies, start with SOC 2 Type II, because US security teams expect an AICPA attestation report. The technical controls overlap heavily, so the second one later costs far less than the first.
Neither is required by EU law. Both are ways to prove to a customer that you run security properly. This post compares them on what actually matters to a 10 to 80 person company: who asks for which, how long each takes, what the auditor does, and how each one maps to NIS2, DORA and GDPR. All sources were checked in November 2026.
The short version: what each one is
ISO 27001 is a certifiable international standard for an information security management system (ISMS). SOC 2 is an attestation report by a licensed US CPA firm on your controls. One gives you a certificate, the other gives you a long report that customers read under NDA.
| ISO/IEC 27001:2022 | SOC 2 | |
|---|---|---|
| Owner | ISO and IEC (international standard) | AICPA (US professional body) |
| Who audits | An accredited certification body | A licensed CPA firm |
| What you get | A public certificate, valid 3 years, with annual surveillance audits | A restricted-use report, typically renewed every year |
| What is assessed | The management system (clauses 4 to 10) plus the Annex A controls you select in your Statement of Applicability | Your controls against the Trust Services Criteria you choose; Security is mandatory |
| Control catalogue | 93 Annex A controls in 4 themes (37 organisational, 8 people, 14 physical, 34 technological) | 2017 Trust Services Criteria with points of focus revised in 2022 |
| Point-in-time vs period | Certification audit, then yearly surveillance | Type I: design at a date. Type II: operating effectiveness over a period, usually 6 to 12 months |
| Who recognises it best | EU and global enterprise buyers, public sector | US enterprise buyers and US-headquartered SaaS vendors |
Sources: ISO/IEC 27001:2022 at iso.org and the AICPA SOC 2 page, which still lists the 2017 Trust Services Criteria (with revised points of focus, 2022) as current.
What EU and US customers actually ask for
In our experience, European procurement asks for ISO 27001 by name, and US security teams ask for a SOC 2 Type II report. Most enterprise questionnaires accept either one as a reason to skip half the questions, but the first answer you give sets the tone.
- EU enterprise and public sector. Tender documents and vendor-risk forms usually list ISO 27001 explicitly. A SOC 2 report is accepted by many, but some procurement teams do not know what to do with it, and the report is not public, so you end up sending it under NDA for every deal.
- US enterprise. Vendor-risk teams are used to reading SOC 2 reports, especially the exceptions section and the complementary user entity controls. An ISO certificate tells them a management system exists, but not how individual controls performed over time, so they often follow up with a questionnaire.
- NIS2-regulated customers. Since NIS2 makes them responsible for supply-chain security (Article 21(2)(d)), they are pushing requirements down to suppliers. ISO 27001 maps directly to the language they use. More on that below.
- German buyers of cloud services sometimes ask for BSI C5 on top. That is rare for startups, but worth knowing before you promise anything in a contract.
Before you commit, look at your pipeline, not your ambitions. Count the deals in the last 12 months that asked for one or the other. That number decides more than any comparison table.
The ISO 27001:2022 transition is over
Only the 2022 edition counts now. Every accredited certificate against ISO 27001:2013 expired or was withdrawn on 31 October 2025, under the IAF transition rules (IAF MD 26), regardless of the expiry date printed on it.
Certification bodies had to audit new clients against the 2022 edition from 30 April 2024 at the latest, and certificates issued against 2013 during the transition carried the 31 October 2025 end date (SGS summary). If a supplier or a target in a due diligence still shows you a 27001:2013 certificate, it is no longer valid; an organisation that missed the deadline goes back to a full initial audit. The 2022 edition cut Annex A from 114 to 93 controls and added 11 new ones, including threat intelligence, information security for cloud services, data masking, monitoring activities and secure coding. Those new controls are exactly the ones a cloud-native startup can show evidence for easily.
A related change: ISO/IEC 27701:2025, the privacy extension, became a standalone management system standard in October 2025 and no longer requires ISO 27001 as a prerequisite. For most startups 27001 alone is still the right first step.
SOC 2 Type I vs Type II
Type I says your controls were designed properly on a given date. Type II says they actually operated over a period. Enterprise buyers want Type II; Type I is a stepping stone you use to unblock a deal while the observation period runs.
A common sequence: get a Type I once controls are in place, then start a Type II observation window immediately. AICPA does not fix a minimum period; auditors commonly accept 3 months for a first Type II and expect 6 to 12 months after that. Ask your auditor before you start the clock, because the period you choose is the period your evidence must cover with no gaps.
ISO has no equivalent split. The certification audit is in two stages (stage 1 documents and readiness, stage 2 effectiveness), but the auditor wants to see the ISMS running, typically with at least one internal audit and one management review completed before stage 2.
How each maps to NIS2, DORA and GDPR
None of these laws requires SOC 2 or ISO 27001, but ISO 27001 is the reference the EU itself uses. If you also need to show NIS2 or DORA readiness, the ISO evidence translates more directly.
| Regulation | ISO 27001 | SOC 2 |
|---|---|---|
| NIS2 | The Implementing Regulation (EU) 2024/2690 for cloud, data centre, managed service and other digital infrastructure providers says its requirements are based on ISO 27001, ISO 27002 and ETSI EN 319 401. ENISA's technical implementation guidance (June 2025) maps each requirement to ISO 27001:2022 controls. | No official mapping. The controls overlap, but you translate them yourself. Incident reporting deadlines (24h, 72h, one month) are not part of SOC 2. |
| DORA | Helps with the ICT risk management framework and with the evidence financial customers request from ICT suppliers. Not a substitute for DORA's own requirements. | Same: useful evidence for your financial customers' third-party risk assessment, nothing more. |
| GDPR | Supports Article 32 "appropriate technical and organisational measures". Not a GDPR certification under Article 42. ISO 27701 adds the privacy layer. | The optional Privacy criteria cover similar ground, but are US-centric and not aligned with GDPR concepts like lawful basis. |
For the practical side, see our NIS2 checklist for AWS and our guide to GDPR-friendly logging in EU regions. If your customers are banks, insurers or payment companies, they will ask about DORA too; our DORA technical checklist covers what changes.
The overlap, and how to do both without doing it twice
Roughly the same technical controls satisfy both. The difference is mostly paperwork: ISO wants a risk-driven management system, SOC 2 wants evidence that each control ran during the period. Build one control set and map it to both.
| Area | What you build once | ISO 27001 Annex A | SOC 2 criteria |
|---|---|---|---|
| Access | SSO, MFA, least privilege, quarterly access reviews | 5.15 to 5.18, 8.2, 8.5 | CC6.1 to CC6.3 |
| Logging and monitoring | CloudTrail org trail, alerting, log retention | 8.15, 8.16 | CC7.2 |
| Change management | Pull requests with review, CI/CD, infrastructure as code | 8.25, 8.32 | CC8.1 |
| Vulnerability management | Dependency scanning, patching SLAs, pen test | 8.8 | CC7.1 |
| Incident response | Runbook, on-call, post-mortems | 5.24 to 5.28 | CC7.3 to CC7.5 |
| Backup and continuity | Tested restores, DR plan | 8.13, 5.30 | A1.2, A1.3 (if Availability is in scope) |
| Suppliers | Vendor inventory and reviews | 5.19 to 5.23 | CC9.2 |
| Risk and governance | Risk register, policies, management review | Clauses 6, 9, 10 | CC1, CC3 |
Our SOC 2 on AWS checklist goes through these controls service by service; almost every item there is also ISO evidence. Three practical tips if you plan both:
- Use one policy set written to ISO structure. SOC 2 auditors accept ISO-style policies; the reverse is less smooth.
- Collect evidence continuously from day one (a compliance automation tool or a well-kept evidence folder), so the SOC 2 period and ISO surveillance draw from the same source.
- Some audit firms offer both a certification body and a CPA practice, and can run the audits back to back with shared fieldwork. Ask; it shortens the second audit.
Decision table by customer base and stage
Choose by where your next ten deals come from. Stage changes the timing, not the answer.
| Your situation | Start with | Then |
|---|---|---|
| Pre-seed or seed, no one asking yet | Neither. Build the controls and keep evidence; answer questionnaires honestly | Start an audit when a deal depends on it |
| Selling to EU mid-market and enterprise | ISO 27001 | SOC 2 only when US deals appear |
| Selling to EU public sector or NIS2-regulated companies | ISO 27001 | ISO 27701 if you process a lot of personal data |
| Selling to EU banks, insurers, payment firms | ISO 27001, plus a DORA-ready contract and exit story | SOC 2 Type II if your buyers' parent companies are US-based |
| Mostly US customers, EU-based team | SOC 2 Type I, then Type II | ISO 27001 when EU enterprise deals start |
| Even split, Series A or later | The one blocking the largest open deal | The other within 12 months, mapped to the same controls |
Two warnings from audits we have helped prepare. First, scope tightly: one product, one production environment in one AWS organisation. A narrow scope you can defend beats a broad one full of exceptions. Second, the certificate is not the goal; a working security programme is. Customers increasingly read the SOC 2 exceptions and ask for your ISO Statement of Applicability, so shortcuts show.
How long it takes
For a cloud-native startup on AWS with no existing programme, expect a few months of preparation before either audit. SOC 2 Type II adds the observation period on top; ISO adds the time to run an internal audit and management review.
The preparation is mostly the same work: identity, logging, backups, change control, vendor management and written policies. If you have done a cloud readiness self-assessment, the gaps it shows are usually the same gaps the auditor will find.
If you want to know where you stand before you pay an auditor, our cloud audit reviews your AWS estate against the controls both frameworks expect and gives you a prioritised gap list. If you would rather not run the evidence collection and quarterly reviews yourself, our managed DevOps service keeps those controls running between audits.
Frequently asked questions
Should a European startup get SOC 2 or ISO 27001 first?
If most of your pipeline is European, start with ISO 27001, because EU procurement, public buyers and NIS2-regulated companies ask for it by name and the ENISA guidance maps to it. If most customers are US companies, start with SOC 2 Type II. The controls overlap heavily, so the second framework later is much cheaper.
Are ISO 27001:2013 certificates still valid?
No. Under the IAF transition rules, all accredited ISO 27001:2013 certificates expired or were withdrawn on 31 October 2025, whatever date was printed on them. Only ISO/IEC 27001:2022 certificates are valid now. An organisation that missed the transition has to go through a full initial certification audit again.
What is the difference between SOC 2 Type I and Type II?
Type I reports on whether your controls were suitably designed at a single date. Type II reports on whether they operated effectively over a period, usually 6 to 12 months, with 3 months often accepted for a first report. Enterprise buyers expect Type II; Type I mainly helps unblock a deal while the observation period runs.
Does ISO 27001 make you compliant with NIS2 or DORA?
No, but it helps a lot. The NIS2 Implementing Regulation for digital providers is based on ISO 27001, and ENISA maps each requirement to ISO 27001:2022 controls. DORA has its own requirements, such as incident timelines and a register of information, that a certificate alone does not cover. Treat ISO 27001 as the foundation, then close the gaps.