Industry
ISO 27001

NIS2 vs ISO 27001: Differences, Mapping and Gaps

Equip IgeraSolutions
September 27, 2026
9 min read

NIS2 vs ISO 27001: Differences, Mapping and the Gaps Certification Leaves Open

Short answer: NIS2 is binding EU law; ISO 27001 is a voluntary management-system standard. Most of the ten Article 21 measures map well to ISO 27001:2022 clauses and Annex A controls, so certification is a strong head start. It does not prove NIS2 compliance by itself: incident-reporting deadlines, management-body accountability, entity scope and supervision come from law, not from the standard.

If you are searching for "NIS2 ISO 27001 mapping", this guide gives you three things: a side-by-side comparison of the two frameworks, a measure-by-measure mapping of NIS2 Article 21(2) to ISO 27001 clauses and Annex A controls with an explicit gap column, and a list of what certification does not cover. Related reading: NIS2 Article 21 measures explained, NIS2 Article 23 incident reporting timeline and the NIS2 compliance checklist for manufacturers.

NIS2 vs ISO 27001 at a glance

AspectNIS2 (Directive (EU) 2022/2555)ISO/IEC 27001:2022
Legal natureEU directive, transposed into national law by each member state. Binding once transposed.Voluntary international standard for an information security management system (ISMS).
Who must complyEssential and important entities in the sectors and size categories defined in the Directive (Arts. 2 and 3), as transposed nationally.Anyone who chooses to adopt it. Sometimes demanded by customers or contracts, never by the standard itself.
Who audits or enforcesNational competent authorities, with supervisory and enforcement powers (Arts. 32 and 33).Accredited certification bodies, via initial certification and surveillance audits.
PenaltiesAdministrative fines: maximum of at least EUR 10 million or 2% of worldwide annual turnover for essential entities, and at least EUR 7 million or 1.4% for important entities (Art. 34), plus supervisory measures.No legal penalties. The consequence of failing is losing or not obtaining the certificate.
ScopeCybersecurity risk management of the network and information systems the entity uses to operate or provide its services, with an all-hazards approach (Art. 21(1)).Whatever scope the organisation defines for its ISMS. A narrow scope can leave key sites or systems outside certification.
Incident reportingMandatory, to the CSIRT or competent authority: early warning within 24 hours, incident notification within 72 hours, final report within one month (Art. 23).Requires an incident management process (Annex A 5.24 to 5.28). No statutory reporting clock to a regulator.
Management roleManagement bodies must approve and oversee the measures and can be held liable for infringements; they must also follow training (Art. 20).Top management must show leadership and commitment (clause 5), but there is no statutory personal liability.

Note on the fines: Art. 34 sets the maximum level that member states must at least provide for; the exact amounts are fixed in each national transposition law, so confirm them for your country.

Is ISO 27001 enough for NIS2?

No, but it gets you most of the way. ISO 27001 certification shows that an independent body audited your ISMS against the standard. NIS2 asks whether your entity meets a legal duty, supervised by your national authority. Certification is useful evidence, but it is not a legal safe harbour. Article 24 of NIS2 deals with European cybersecurity certification schemes for ICT products, services and processes; an ISO 27001 certificate for an organisation is not one of those schemes and does not by itself create a presumption of conformity.

In practice, supervisors will want to see that the Article 21 measures are implemented and proportionate to your risk, that reporting works within the deadlines, and that management has approved and overseen the whole. An ISO 27001 ISMS gives you the documented risk assessment, controls, internal audits and management reviews that feed that evidence file.

NIS2 Article 21 to ISO 27001 mapping table

Article 21(2) requires entities to take appropriate and proportionate measures that include, at least, ten listed items (a to j). The table below pairs each with the ISO 27001:2022 clauses and Annex A controls that address the same subject matter, and states what typically remains open. This is a conceptual mapping prepared for practitioners: no regulator or standards body has published an official one-to-one table. Annex A has 93 controls in four themes (Organizational, People, Physical, Technological); the full control-by-control audit view is in our ISO 27001 audit checklist.

NIS2 Art. 21(2) measureISO 27001:2022 clause / Annex AGap to close for NIS2
(a) Risk analysis and information system security policiesClauses 6.1.2 and 6.1.3 (risk assessment and treatment), clause 5.2 (policy), A.5.1 (policies), A.5.2 (roles and responsibilities)Risk assessment must cover the network and information systems under an all-hazards approach and be proportionate to the entity; check that the ISMS scope includes all in-scope systems, not just the certified ones.
(b) Incident handlingA.5.24 to A.5.28 (incident planning, assessment, response, learning, evidence), A.6.8 (event reporting)Add the legal layer: criteria for a "significant incident", the 24h / 72h / one-month reporting workflow, and the authority contact points (Art. 23).
(c) Business continuity, backup management and disaster recovery, and crisis managementA.5.29 (security during disruption), A.5.30 (ICT readiness for business continuity), A.8.13 (backup), A.8.14 (redundancy)Crisis management involving senior management and communication with authorities and customers may need to go beyond the ISMS continuity plan.
(d) Supply chain security, including security-related aspects of relationships with direct suppliers and service providersA.5.19 to A.5.23 (supplier relationships, agreements, ICT supply chain, monitoring, cloud services)Art. 21(3) asks entities to consider vulnerabilities specific to each direct supplier and the overall quality of suppliers' products and cybersecurity practices, and to take into account coordinated EU-level risk assessments of critical supply chains. Most ISMS supplier processes need extending. See NIS2 supply chain security.
(e) Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosureA.8.25 to A.8.34 (secure development lifecycle, testing, outsourced development), A.8.8 (technical vulnerability management), A.8.9 (configuration management), A.8.32 (change management)Add a defined process for vulnerability handling and coordinated disclosure across systems and products.
(f) Policies and procedures to assess the effectiveness of cybersecurity risk-management measuresClauses 9.1 (monitoring and measurement), 9.2 (internal audit), 9.3 (management review), 10 (improvement), A.5.35 (independent review), A.5.36 (compliance with policies)Strong match. Make sure the metrics and audit results can be shown to a supervisor, not only to the certification body.
(g) Basic cyber hygiene practices and cybersecurity trainingClauses 7.2 and 7.3 (competence and awareness), A.6.3 (awareness, education and training), A.8.7 (protection against malware)Art. 20(2) separately requires members of management bodies to follow training; staff training under A.6.3 does not cover it. See NIS2 board training.
(h) Policies and procedures regarding the use of cryptography and, where appropriate, encryptionA.8.24 (use of cryptography), A.5.14 (information transfer)Largely covered. Check that the cryptography policy is documented and risk-based.
(i) Human resources security, access control policies and asset managementA.6.1 to A.6.6 (people controls), A.5.15 to A.5.18 (access control, identity, authentication, access rights), A.5.9 to A.5.11 (inventory and use of assets)Largely covered. Confirm the asset inventory includes the network and information systems relevant to the services in scope.
(j) Multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems, where appropriateA.8.5 (secure authentication), A.8.20 to A.8.22 (network security), A.5.14 (information transfer)A.8.5 does not mandate MFA as such. NIS2 expects MFA or continuous authentication where appropriate, plus secured emergency communications, which ISO 27001 does not name.

Other Annex A controls also help, for example A.5.7 (threat intelligence), A.5.5 (contact with authorities) and A.5.31 (legal, statutory, regulatory and contractual requirements). They do not replace the NIS2-specific obligations below.

What ISO 27001 does not cover for NIS2

  • Statutory incident reporting. Art. 23 requires an early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, and a final report within one month of the notification, plus an intermediate report if the authority asks. ISO 27001 requires a working incident process, not these deadlines. Details in our NIS2 Article 23 incident reporting timeline.
  • Management-body accountability. Art. 20 requires management bodies to approve the cybersecurity risk-management measures, oversee their implementation, follow training, and be answerable for infringements. Clause 5 of ISO 27001 asks for leadership commitment, which is related but weaker and carries no legal liability.
  • Entity classification and scope. Whether you are an essential or an important entity (Art. 3), and whether you are in scope at all, depends on sector, size and national law. An ISMS scope statement does not answer that question. See NIS2 essential entities and the NIS2 guide for manufacturers.
  • Supply chain depth. Art. 21(2)(d) and 21(3) go further than standard supplier controls, as the mapping table above shows.
  • Regulator supervision and registration. NIS2 gives authorities powers of supervision and enforcement (Arts. 32 and 33), and entities have registration and contact duties under national law. A certification body audit is not a regulatory inspection.
  • Proportionality is judged by the regulator. Art. 21(1) requires measures proportionate to risk, size, cost and the likelihood and severity of incidents. A certificate does not settle that judgement for you.

What about Spain? Transposition status

Spain missed the 17 October 2024 deadline for transposing NIS2. According to the trackers and law-firm notes we found, a draft law (anteproyecto) was approved by the Council of Ministers in January 2025 and, in the most recent sources available to us (spring to mid 2026), had not been published in the BOE as a final law; Real Decreto-ley 12/2018 continued to apply in the meantime. One source claims the law is already in force, which conflicts with the others. We could not verify the current status from an official source, so check the BOE and the competent authority before relying on any date. The Directive's requirements are fixed at EU level, so preparing now is low-regret.

How to use ISO 27001 as your NIS2 foundation

  1. Confirm whether you are an essential or important entity under your national transposition law.
  2. Check that your ISMS scope covers all the network and information systems used to provide in-scope services.
  3. Use the mapping table to tag each Annex A control and ISMS record with the Article 21(2) measure it supports.
  4. Close the gaps: a reporting workflow with 24h / 72h / one-month templates, management sign-off and training, deeper supplier assessments, a vulnerability disclosure process.
  5. Run an internal audit against both: use the ISO 27001 audit checklist and add the NIS2 gap items above.

Where IgeraIndustria fits

Evidence is only as useful as it is retrievable. When an inspector or customer asks which procedure covers supplier onboarding or incident escalation, your team needs the right paragraph fast. IgeraIndustria answers questions directly from your own compliance and quality documents (ISMS policies, procedures, risk registers, supplier contracts) and cites the exact source paragraph rather than producing a generic answer. See IgeraIndustria for ISO 27001 for how it works with the standard. It does not interpret the law or certify compliance.

Frequently asked questions

Is NIS2 the same as ISO 27001?

No. NIS2 is an EU directive that becomes binding law through national transposition, enforced by authorities with fines. ISO 27001 is a voluntary standard for an ISMS, audited by certification bodies. They overlap in subject matter but not in legal status.

Does ISO 27001 certification mean we are NIS2 compliant?

Not by itself. Certification shows your ISMS was independently audited, and it covers much of what Article 21 asks for. NIS2 compliance also requires meeting legal duties such as the Art. 23 reporting deadlines, management-body oversight under Art. 20 and the obligations under your national law.

How does ISO 27001 map to NIS2 Article 21?

Each of the ten Article 21(2) measures corresponds to ISO 27001 clauses and Annex A controls: risk analysis to clause 6.1, incident handling to A.5.24 to A.5.28, continuity to A.5.29 and A.5.30, supply chain to A.5.19 to A.5.23, cryptography to A.8.24, and so on. The mapping table above shows each pairing and the remaining gap. No official numbered mapping exists.

What does NIS2 require that ISO 27001 does not?

Mainly: reporting significant incidents to the authority within 24 hours (early warning), 72 hours (notification) and one month (final report); management-body approval, oversight, training and liability; entity classification and registration under national law; and regulator supervision with fines.

Should we get ISO 27001 certified before NIS2?

Not necessarily in that order. NIS2 duties follow their own legal timeline, so most organisations run both in parallel, using ISO 27001's structure for the technical and organisational work and handling the NIS2 legal obligations directly.

Has Spain transposed NIS2 yet?

We could not confirm an enacted Spanish law from official sources. Most sources describe a draft law approved by the Council of Ministers in January 2025 and still pending in 2026. Verify the current status in the BOE.

Next step: run an internal audit with the ISO 27001 audit checklist, then see how IgeraIndustria for ISO 27001 lets your team query your ISMS and NIS2 documents with exact citations.

Disclaimer: This article is provided for general informational purposes only and does not constitute legal or certification advice. The mapping is a conceptual practitioner guide, not an official correspondence. NIS2 transposition and enforcement vary by EU member state and continue to evolve, and ISO/IEC 27001 requirements are set by the standard and your certification body. Consult a qualified compliance consultant, certification body or lawyer before making compliance decisions.

Share this article

Help spread knowledge by sharing this content with your network