Guide Compliance Cybersecurity

NIS2 vs. ISO 27001: differences, requirements and how to integrate them

The NIS2 Directive sets legal cybersecurity obligations for certain entities in the European Union. ISO/IEC 27001:2022 sets out the requirements for a risk-based information security management system. The two align strongly in several control areas, but they are not equivalent. This guide explains how to use an ISO 27001 programme to prepare for NIS2, which obligations need a specific assessment, and how to organise a gap analysis without duplicating work.

2 June 2026
Updated 18 November 2026
11 min read
Key takeaways
  • NIS2 is EU law, applied through national legislation. ISO 27001 is a voluntary international standard. They are different instruments with different purposes.
  • ISO 27001 has related control areas for each of the ten measures in NIS2 Article 21(2), but a related control is not the same as meeting the legal obligation
  • A certified ISMS does not cover NIS2-specific duties such as reporting significant incidents, management body approval and training, and submitting information to the authorities
  • A requirement-by-requirement gap analysis is the right first step, whether you already hold a certificate or are starting from scratch
  • The most efficient path is one integrated programme that reuses processes, risk assessments and evidence, rather than two separate compliance projects

Two frameworks, different obligations

Compliance officers at medium and large European companies are fielding questions about NIS2 and ISO 27001 at the same time. It is easy to see why teams conflate the two: both deal with cybersecurity, both require risk assessments and documented controls, and both lead to audits. But they are fundamentally different instruments, and treating them as interchangeable leaves real compliance gaps.

NIS2 (Directive (EU) 2022/2555) is EU legislation that each member state applies through national law. It generally applies to medium-sized and large entities in the 18 sectors listed in its Annexes I and II, with size assessed under the EU definition of SMEs. Some entities are in scope regardless of size, for example providers of public electronic communications networks or services, trust service providers, top-level domain name registries and DNS service providers, and entities that are the sole provider of an essential service in a member state (Article 2(2)). If your organisation is in scope, compliance is not optional. Member states must be able to impose maximum fines of at least €10 million or 2% of worldwide annual turnover, whichever is higher, on essential entities, and at least €7 million or 1.4% on important entities. NIS2 entered into force in January 2023, and member states had until 17 October 2024 to transpose it into national law. Several transposed it late, so the national law that applies to you may be recent.

ISO/IEC 27001:2022 is an international standard for information security management systems (ISMS). Certification is voluntary. Any organisation can pursue it, in any sector, at any size. The standard does not tell you exactly what security controls to implement; it asks you to build a risk-based management system that systematically identifies threats, selects proportionate controls, and continuously improves. Third-party certification bodies assess you against the standard, within the scope you define, and issue a certificate.

18
sectors listed in NIS2 Annexes I and II
93
controls in ISO 27001:2022 Annex A, across 4 themes
10
minimum measure areas in NIS2 Article 21(2)

Where they overlap

NIS2 Article 21(2) lists ten areas that an entity's cybersecurity risk-management measures must at least include. ISO 27001 has related clauses and Annex A controls for each of them. The table below maps related control areas. It is not a statement of equivalence.

NIS2 Art. 21(2) area
Relevant ISO 27001 examples
Assessment
(a) Policies on risk analysis and information system security
Clause 6.1 (risk assessment and treatment); A.5.1 (policies for information security)
Strong alignment Check that the risk assessment covers the entities and services in NIS2 scope.
(b) Incident handling
A.5.24 to A.5.28 (incident planning, assessment, response, learning and evidence); A.6.8 (event reporting)
Strong alignment Add reporting of significant incidents to the authorities, which ISO 27001 does not require.
(c) Business continuity, backup management, disaster recovery and crisis management
A.5.29 (information security during disruption); A.5.30 (ICT readiness for business continuity); A.8.13 (information backup); A.8.14 (redundancy)
Strong alignment Verify that crisis management and recovery are planned and tested, not only documented.
(d) Supply chain security
A.5.19 to A.5.23 (supplier relationships, supplier agreements, ICT supply chain, supplier monitoring, cloud services)
Strong alignment Article 21(3) also expects you to consider each supplier's vulnerabilities and secure development practices.
(e) Security in acquisition, development and maintenance, including vulnerability handling and disclosure
A.8.8 (management of technical vulnerabilities); A.8.25 to A.8.32 (secure development life cycle through change management)
Partial alignment Vulnerability disclosure, such as a coordinated disclosure process, is not explicit in Annex A. Verify it.
(f) Policies and procedures to assess effectiveness
Clause 9 (monitoring, internal audit, management review); A.5.35 (independent review); A.5.36 (compliance with policies and standards)
Strong alignment Make sure effectiveness is measured against the NIS2 measures, not only the ISMS objectives.
(g) Basic cyber hygiene practices and cybersecurity training
A.6.3 (awareness, education and training); A.8.7 (protection against malware); A.8.8; A.8.9 (configuration management)
Strong alignment Verify the hygiene baseline against national guidance and, where it applies, the implementing regulation.
(h) Cryptography and, where appropriate, encryption
A.8.24 (use of cryptography)
Strong alignment Check that the policy covers key management and the systems in NIS2 scope.
(i) Human resources security, access control policies and asset management
A.6.1 to A.6.6 (people controls); A.5.9 (inventory of assets); A.5.15 to A.5.18 (access control, identity management, authentication information, access rights)
Strong alignment Confirm the asset inventory covers all network and information systems in scope.
(j) Multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications, where appropriate
A.8.5 (secure authentication); A.8.20 to A.8.21 (network security, security of network services); A.5.14 (information transfer)
Partial alignment Secure authentication is covered. Check secured communications and emergency communication systems.

A mapping like this shows where an existing ISMS gives you a head start. It does not show that you meet NIS2, for three reasons. First, a topic appearing in Annex A is not the same as a control being implemented, and an implemented control is not automatically enough to meet the legal obligation. Second, ISO 27001 is risk-based: your Statement of Applicability may exclude controls that NIS2 expects you to address, and your certified scope may not match the entities and services that NIS2 covers. Third, Commission Implementing Regulation (EU) 2024/2690 sets detailed technical and methodological requirements for certain digital infrastructure and ICT service providers, such as cloud, data centre, managed service, managed security service and DNS providers, and national transposition laws can add further requirements.

Where they diverge

The overlap has real limits. ISO 27001 was designed as a management system standard, not a legal compliance framework, and NIS2 adds obligations that a certificate does not address.

Topic
NIS2
ISO 27001
Legal obligation
Mandatory for in-scope entities under national law; enforced by national authorities
Voluntary; no legal obligation to certify
Who it applies to
Generally medium and large entities in 18 sectors (Annexes I and II); some entities regardless of size
Any organisation, any sector, any size, anywhere
Incident notification
For significant incidents: early warning within 24 hours of becoming aware, incident notification within 72 hours, final report within one month after the notification, with intermediate or progress reports where required. National law sets the procedure.
No external notification timelines; internal incident management only
Management body
Article 20: the management body must approve the cybersecurity risk-management measures, oversee their implementation and follow training, and can be held liable for infringements under national law
Top management must show leadership and commitment (clause 5); no legal liability provisions
Registration and information
Entities must be identified and submit information to the competent authorities (Articles 3 and 27); the procedure is set by national law
No registration requirement
Supply chain
Legal duty to address supplier security, taking into account supplier vulnerabilities, product quality and secure development practices
Supplier controls selected on risk, within a scope the organisation sets
Supervision and enforcement
National competent authorities can inspect, audit, request information and issue binding instructions; proactive supervision for essential entities, reactive for important entities
Accredited certification body audits conformity within the certified scope (e.g., BSI, Bureau Veritas, DNV)
Detailed requirements
Implementing Regulation (EU) 2024/2690 for certain digital providers; national laws may add more
93 Annex A controls, risk-based selection; not all apply to every organisation
Fines for non-compliance
Maximum of at least €10M or 2% of worldwide turnover (essential) and €7M or 1.4% (important), whichever is higher
Loss of certification; no financial penalties from the standard itself

In practice, the gaps that matter most are incident reporting, management body accountability, and registration and information submission. ISO 27001 does not require you to report incidents to an authority. It requires leadership commitment, but not that your management body approves the measures, follows training and can be held liable. And it does not require you to submit information to a national body. Supervision also works differently: a regulator assesses whether you meet the law, not whether your ISMS conforms to a standard.

Common mistake

Many organisations assume that ISO 27001 certification means NIS2 compliance. It does not. Regulators will look for documented procedures for reporting significant incidents, evidence of management body approval, oversight and training, measures that cover the full NIS2 scope, and submission of the required information. An ISO 27001 certificate alone will not satisfy a supervisory review on these points.

If you already have ISO 27001 certification

You are in a strong position, but you are not finished. The remaining NIS2-specific gaps often fall into four categories:

  • Incident reporting. Your incident response plan is unlikely to include the NIS2 reporting sequence for significant incidents. Add criteria for deciding when an incident is significant, name the people responsible for the 24-hour early warning, and test the process in a tabletop exercise.
  • Management body approval and training. NIS2 Article 20 requires the management body to approve the cybersecurity risk-management measures, oversee their implementation and follow training. Board minutes and structured training records need to demonstrate this explicitly.
  • Registration and information submission. In-scope entities must provide information to the competent authority in the way national law sets out. ISO 27001 does not prompt this step.
  • Scope and exclusions. Compare your ISMS scope and Statement of Applicability with the entities, services and systems that NIS2 covers. Controls excluded on risk grounds, and areas such as vulnerability disclosure and secured communications, may need attention. Where multi-factor authentication is appropriate for your risks, document it under A.8.5.

For a certified organisation, closing these gaps is usually targeted work rather than a transformation project. A mature ISMS lets you reuse much of your processes, policies, risk assessments and evidence. How much remains depends on your scope, the controls you have actually implemented and the specific requirements that apply to you, which only a requirement-by-requirement gap analysis will show. In some cases a focused assessment can produce a remediation plan within a few weeks.

If you are starting from scratch

Your instinct may be to pick one framework, complete it, then tackle the other. That sequence wastes material effort. Much of the documentation, risk assessments, policies, and control evidence you build for NIS2 can be reused for ISO 27001. Running them as separate projects means doing a lot of the same work twice.

In practice

A NIS2 programme structured like an ISMS gives ISO 27001 certification a strong base, because much of the risk assessment, policy and evidence work can be reused. How much extra effort certification needs depends on your scope and the controls already in place. Running two separate programmes from scratch means building the same risk assessments, policies, and control evidence twice.

If you are in scope for NIS2, that obligation is already active. Start there. But structure your NIS2 programme using ISO 27001's management system approach from day one: a defined scope, a formal risk assessment, a Statement of Applicability mapping your controls, and a documented improvement cycle. This approach means that when you are ready to pursue ISO 27001 certification, the certification body is reviewing a programme that already exists in mature form, rather than starting from scratch.

An ISO 27001 programme built without NIS2 in mind can leave legal obligations unaddressed. Building NIS2-first, with an ISO 27001-aligned structure from the start, reduces that rework.

Where to start: the gap analysis

The first step for any organisation, regardless of whether it has existing controls, existing certifications, or nothing in place, is a structured gap analysis. Without one, you are making decisions based on assumptions about your own posture that are rarely accurate.

A good gap analysis covers three things:

  1. Scope confirmation. Are you in scope for NIS2? Which tier are you (essential or important)? Have you submitted the information your national authority requires? This is not always obvious, particularly for diversified groups operating in multiple sectors.
  2. Control mapping. Requirement by requirement, where do your current controls, documentation, and processes map against NIS2 Article 21, any national or implementing requirements, and ISO 27001 Annex A? This shows which controls and evidence can be reused and produces a clear picture of what you have, what needs formalising, and what needs building from scratch.
  3. Prioritised remediation roadmap. Not everything needs to happen at once. The gap analysis should produce a risk-prioritised list of actions, with realistic timelines and resource estimates, that lets you make informed decisions about sequencing.

With that roadmap in hand, you can build a single integrated programme that moves you toward both NIS2 compliance and ISO 27001 certification in parallel, without duplicating effort or creating conflicting documentation.

Organisations that come to a NIS2 supervisory review with a completed gap analysis and a documented remediation plan are in a fundamentally different position from those that arrive without one. Regulators are looking for evidence that management has taken the obligations seriously. A credible roadmap is exactly that evidence.

Frequently asked questions

Is NIS2 the same as ISO 27001?

No. NIS2 is an EU directive, a legal obligation that applies through national law to in-scope entities in 18 sectors. ISO 27001 is an international standard for information security management systems (ISMS) that any organisation can pursue voluntarily. NIS2 tells you what you must achieve; ISO 27001 gives you a structured system that can help you achieve it and provide evidence.

Does ISO 27001 certification prove NIS2 compliance?

No. A certificate shows that your ISMS conforms to ISO 27001 within the certified scope. It can provide evidence for several NIS2 measures, such as risk management, incident handling and supplier security, but it does not replace an assessment of the legal, regulatory and operational obligations that apply to you, including reporting significant incidents, management body duties and submitting information to the authorities.

Which should we do first: NIS2 or ISO 27001?

If you are in scope for NIS2, that obligation is already active. It cannot wait. The most efficient path for most organisations is to pursue NIS2 compliance first, using an ISO 27001-aligned structure from the outset. This way, much of the work you do for NIS2 becomes the foundation of your ISO 27001 certification, rather than running two parallel programmes.

Do SMEs need to worry about NIS2?

NIS2 generally applies to medium-sized and large entities, assessed under the EU definition of SMEs, so many small and micro businesses fall outside its direct scope. There are exceptions: some entities are in scope regardless of size, such as providers of public electronic communications networks or services, trust service providers, top-level domain name registries and DNS service providers, and entities that are the sole provider of an essential service. Check the national law that applies to you. SMEs outside direct scope may still face security requirements through contracts, because in-scope customers must manage the security of their supply chains.

How long does ISO 27001 certification take?

As a planning estimate, many medium-sized organisations allow 9 to 18 months for a first ISO 27001 certification; the standard itself sets no timeline. The timeline depends on how mature your existing security controls are, the scope of the ISMS, and how quickly your team can document processes and evidence. An experienced consultancy can significantly compress this timeline by avoiding common pitfalls and structuring the programme efficiently.

Ada Bicker
About the author
Cybersecurity Consultant, Cyvra

Ada has more than five years' experience in information security, ISO 27001, SOC 2 and EU compliance, and writes about DORA, the EU AI Act and NIS2. View full profile

Gap Analysis Workshop

Not sure where your NIS2 or ISO 27001 gaps are?

Our gap analysis workshop gives you a clear, prioritised picture of what you have, what you are missing, and the fastest path to compliance.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.