Insights

NIS2 vs ISO 27001: Differences, Mapping and Where to Start

Last updated: 9 November 2026. Based on Directive (EU) 2022/2555 (NIS2), Commission Implementing Regulation (EU) 2024/2690 and ISO/IEC 27001:2022.

The short version

  • NIS2 is law; ISO 27001 is a standard. NIS2 is mandatory if your organisation is in scope. ISO 27001 is voluntary and certifiable.
  • They overlap heavily. The ten risk-management measures in Article 21 of NIS2 map closely onto ISO 27001 clauses and Annex A controls.
  • ISO 27001 does not equal NIS2 compliance. NIS2 adds legal duties that a certificate does not cover: incident reporting deadlines, registration with authorities, personal accountability for management and supervisory powers.
  • The efficient route: use an ISO 27001 management system as the engine of your NIS2 programme, then close the NIS2-specific gaps.

NIS2 vs ISO 27001 at a glance

NIS2ISO/IEC 27001
NatureEU directive, transposed into national lawInternational, voluntary standard
WhoEssential and important entities in 18 sectors, usually medium-sized and largerAny organisation, any size, any sector
ProofSupervision by national authorities, audits and inspectionsCertificate from an accredited certification body
ScopeNetwork and information systems supporting your servicesScope you define for your ISMS
Incident reportingMandatory: 24h early warning, 72h notification, final report within one monthIncident management required, no reporting to authorities
ManagementManagement bodies approve measures, must be trained and can be held liableTop management leadership and commitment
Supply chainExplicit duty to manage supplier security risksSupplier controls in Annex A
SanctionsFines up to €10M or 2% of turnover (essential) and €7M or 1.4% (important)None; loss of certificate

How Article 21 maps to ISO 27001

Article 21(2) of NIS2 lists ten minimum measures. Almost every one has a direct counterpart in ISO 27001:2022, which is why an existing ISMS is the strongest starting point.

NIS2 Article 21(2) measureWhere ISO 27001 covers it
(a) Risk analysis and information system security policiesClauses 6.1 and 8.2–8.3; control 5.1
(b) Incident handlingControls 5.24–5.28
(c) Business continuity, backups, disaster recovery, crisis managementControls 5.29, 5.30, 8.13, 8.14
(d) Supply chain securityControls 5.19–5.23
(e) Security in acquisition, development and maintenance, vulnerability handlingControls 8.8, 8.25–8.29
(f) Assessing the effectiveness of measuresClause 9 (monitoring, internal audit, management review)
(g) Cyber hygiene and trainingControls 6.3, 8.1, 8.7, 8.9
(h) Cryptography and encryptionControl 8.24
(i) HR security, access control, asset managementControls 5.9–5.18, 6.1–6.6
(j) Multi-factor authentication and secure communicationsControls 5.14, 8.5

The mapping is close, not complete. Implementing Regulation (EU) 2024/2690 sets more detailed technical requirements for digital infrastructure and ICT service providers, and national laws can add their own. Always check the rules that apply in your Member State.

What ISO 27001 does not cover

REPORTING

Incident notification

A process to classify significant incidents and notify the CSIRT or authority within 24 hours, 72 hours and one month.

GOVERNANCE

Management accountability

Board approval of measures, mandatory training for management and personal liability under national law.

REGISTRATION

Registration and scope

Determining whether you are an essential or important entity and registering with the national authority.

SUPERVISION

Evidence for authorities

Being able to show the authority, not just an auditor, that measures are in place and effective.

Which should you do first?

DECISION GUIDE

IF

You are in NIS2 scope

Start with NIS2: confirm scope, register and set up incident reporting. Use ISO 27001 as the framework to implement Article 21.

IF

You are a supplier to NIS2 entities

Start with ISO 27001. Your clients will push NIS2 requirements down the supply chain, and a certificate is the fastest proof.

IF

You already hold ISO 27001

Run a NIS2 gap analysis. Most work is in reporting, governance and national specifics.

Not sure if NIS2 applies to you? Try our free NIS2 applicability check or read our NIS2 transposition tracker.

Frequently asked questions

Does ISO 27001 certification make us NIS2 compliant?

No. ISO 27001 covers most of the technical and organisational measures in Article 21 of NIS2, but not the legal duties such as incident reporting to authorities, registration and management accountability. It is a strong foundation, not a substitute.

Is ISO 27001 mandatory under NIS2?

No. NIS2 does not require certification. Member States may require the use of certified products, services or processes, and authorities can refer to European and international standards such as ISO 27001.

What is the difference between NIS2 and ISO 27001?

NIS2 is an EU law that obliges organisations in critical sectors to manage cyber risks and report incidents. ISO 27001 is a voluntary international standard for building and certifying an information security management system.

How long does it take to align ISO 27001 with NIS2?

For an organisation that already holds ISO 27001, closing the NIS2 gaps typically takes a few months, depending on the national law, incident reporting maturity and supply chain controls.

Can one programme cover both?

Yes. Most organisations build a single ISMS with one risk process, one set of policies and one audit cycle, and add NIS2-specific procedures for reporting and governance.

Want one programme for NIS2 and ISO 27001? See our NIS2 compliance service and ISO 27001 consulting, or book a free scoping call.

Sources: Directive (EU) 2022/2555 (NIS2), Articles 20, 21, 23 and 34; Commission Implementing Regulation (EU) 2024/2690; ISO/IEC 27001:2022; ENISA technical implementation guidance.

Need help applying this to your organisation? Talk to one of our specialists — remote across the EU.