An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesMapping ENISA NIS2 Guidance to ISO 27001
Implementing Regulation 2024 2690 / 2026-10-11

Mapping ENISA NIS2 Guidance to ISO 27001

An ISO/IEC 27001 information security management system can support implementation of Regulation (EU) 2024/2690, but certification does not automatically prove that every applicable Annex requirement has been met. A useful mapping links the regulation's precise duties, ENISA's practical explanations, relevant ISO controls and actual evidence, then highlights uncovered obligations.

Keep legal requirements separate from the ISO standard

Regulation 2024/2690 contains mandatory technical and methodological requirements for specified providers. ISO/IEC 27001 is a management-system standard whose applicability, control selection and certification scope may differ. Map from the regulation outward instead of assuming that a certificate covers the legal text. ENISA guidance can explain implementation options but cannot replace either the regulation or the organisation's scope determination.

Use a requirement-level crosswalk

Create a row for each relevant Annex requirement, including its subparagraph and any qualifier. Record the corresponding ISMS process, relevant ISO/IEC 27001 clause or Annex A control, responsible owner and operating evidence. Where one security control supports several requirements, retain separate assessments of the legal outcomes. Where a legal obligation has no adequate existing control, record a gap instead of forcing a superficial match.

Review scope and operational coverage

An ISO certificate can apply to a limited business unit, service or location. Compare the certified scope with the legal entity and service covered by Regulation 2024/2690. Review outsourced operations, cloud infrastructure, incident notification processes and operational continuity that fall outside a narrow ISMS scope. A familiar policy name is not enough to establish that the control covers the relevant systems.

Evaluate incident and governance differences

ISO risk-management processes are useful, but regulation-specific incident significance tests in Articles 3 to 14 and the NIS2 Article 23 reporting framework demand separate attention. Check management responsibilities, competent-authority contacts and reporting escalation alongside the technical controls. ENISA examples can suggest supporting evidence, but do not replace legal analysis of provider-specific thresholds.

Use the mapping for continuous improvement

Assign remediation owners to gaps, schedule tests and attach evidence of implementation. Update the crosswalk after significant changes to ISO controls, the entity's services or ENISA guidance. Maintain the distinction between a standard requirement, a legal requirement and a suggested implementation measure. That distinction helps management review actual compliance risks rather than a single percentage score.

Points of clarification

Does ENISA guidance create additional legally binding duties?

No. The regulation is binding; ENISA guidance helps interpret and implement it.

Does ISO 27001 certification automatically establish compliance?

No. Legal scope, provider-specific obligations and actual controls need separate assessment.

How should implementation evidence be organised?

Link every applicable Annex requirement to its control, owner, dated operational evidence and outstanding gaps.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.