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 NIS2 Guidance to Existing Security Frameworks
Implementing Regulation 2024 2690 / 2026-10-11

Mapping NIS2 Guidance to Existing Security Frameworks

Existing security frameworks such as ISO/IEC 27001, NIST CSF and CIS Controls can help providers implement Commission Implementing Regulation (EU) 2024/2690, but none replaces the legal requirements. A defensible crosswalk starts from each applicable provision in the regulation's Annex, maps relevant controls and evidence, and separately tests provider-specific incident criteria.

Start with the legal requirement

Determine whether the entity provides a service listed in Article 1 of Regulation 2024/2690. For each applicable numbered Annex requirement, write down the required result, any qualification and the affected service. The existing framework should be a tool for implementation, not the source of the legal obligation. NIS2 Article 21 and national implementation also require attention where relevant.

Compare frameworks without forcing one-to-one matches

ISO/IEC 27001 focuses on an information security management system, NIST CSF organises cybersecurity outcomes, and CIS Controls provide prioritised safeguards. One Annex obligation may depend on multiple existing processes; one established control may support several obligations. Record partial coverage and any framework differences rather than marking a requirement complete because a familiar label appears in both documents.

Check scope and practical operation

Framework adoption or certification may be limited to a subsidiary, service, location or selected systems. Compare that scope with the regulated provider's service inventory. Verify evidence such as access reviews, supplier assessments, restore tests, detection procedures and completed corrective actions. Policies without operational records should be identified as design evidence, not proof that controls work in production.

Keep legal incident criteria separate

Regulation 2024/2690 Articles 3 to 14 contain incident-significance conditions for specified providers. A framework-based incident severity matrix may help triage events but cannot replace those legal tests or the NIS2 Article 23 notification process. Create a separate mapping for threshold assessment, responsibility for decisions, authority contacts and records of what was known at each stage of an incident.

Maintain an evidence-based gap register

For each Annex requirement, record the mapped framework element, implemented measure, accountable owner, evidence, assessment outcome and remediation deadline. Explain any nonapplication of qualified requirements using the rationale called for by the regulation. Revisit mappings after changing a service, adopting a new framework version, receiving regulatory guidance or learning from an incident.

Points of clarification

Can ISO 27001 or NIST CSF substitute for Regulation 2024/2690?

No. They can support implementation, but legal obligations must be assessed separately.

Should every Annex requirement map to just one framework control?

No. A legal requirement may need several controls and evidence sources.

Do framework incident categories determine NIS2 reportability?

No. Apply the regulation's significance criteria and relevant NIS2 notification rules.

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.