- 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.
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.
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.
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.
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.
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:
- 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.
- 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.
- 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.