Guide Compliance Cybersecurity

NIS2 and NIST CSF 2.0 control mapping: correspondences, gaps and sector notes

How each of the ten NIS2 Article 21(2) measure areas relates to NIST CSF 2.0 categories, which NIS2 obligations need a separate legal check, and what to consider in healthcare, financial services, hospitality and as a supplier to EU customers.

14 November 2026
9 min read
Key takeaways
  • Each of the ten Article 21(2) measure areas has thematic correspondences in CSF 2.0, but a correspondence is not legal equivalence
  • Incident reporting deadlines, entity classification, management body duties and national supervision need checking beyond the CSF mapping
  • Financial entities under DORA should assess DORA first, because NIS2 Article 4 gives precedence to equivalent sector-specific rules

This page covers the detailed mapping: how each NIS2 Article 21(2) measure area corresponds to NIST CSF 2.0, the obligations that need checking beyond it and notes for specific sectors. For how the two frameworks differ, what changed in CSF 2.0 and how to run one integrated programme, see our NIST CSF 2.0 and NIS2 guide.

NIS2 and NIST CSF 2.0 correspondences

The table relates each of the ten measure areas in NIS2 Article 21(2) to the CSF 2.0 categories that cover similar ground. These are selected category-level correspondences, not an exhaustive subcategory mapping: they show where to look, not what the law requires. Each row also names what you still need to verify against the legal text, national law and, where it applies, Implementing Regulation (EU) 2024/2690.

a
Art. 21(2)(a): policies on risk analysis and information system security
Relevant CSF 2.0 categories
GV.RMGV.POID.RA
Additional verification: the risk analysis follows an all-hazards approach covering the systems used to provide your services, and the management body approves the measures.
b
Art. 21(2)(b): incident handling
Relevant CSF 2.0 categories
RS.MARS.ANRS.CORS.MI
Additional verification: significant-incident criteria, the Article 23 reporting stages and the national reporting channel are built into the process.
c
Art. 21(2)(c): business continuity, such as backup management and disaster recovery, and crisis management
Relevant CSF 2.0 categories
PR.IRRC.RPRC.CO
Additional verification: crisis management is covered as well as IT recovery, and backups and recovery plans are tested.
d
Art. 21(2)(d): supply chain security
Relevant CSF 2.0 categories
GV.SC
Additional verification: security aspects of relationships with direct suppliers and service providers, plus any national or EU supply chain requirements that apply to you.
e
Art. 21(2)(e): security in acquisition, development and maintenance, including vulnerability handling and disclosure
Relevant CSF 2.0 categories
PR.PSID.RA
Additional verification: a documented process for handling and disclosing vulnerabilities, not only patching.
f
Art. 21(2)(f): policies and procedures to assess the effectiveness of risk-management measures
Relevant CSF 2.0 categories
GV.OVID.IM
Additional verification: effectiveness is measured and reported to the management body, not assumed from policy.
g
Art. 21(2)(g): basic cyber hygiene practices and cybersecurity training
Relevant CSF 2.0 categories
PR.ATPR.PS
Additional verification: training for members of the management body under Article 20(2) is a separate duty.
h
Art. 21(2)(h): cryptography and, where appropriate, encryption
Relevant CSF 2.0 categories
PR.DS
Additional verification: a documented policy on cryptography and key management, with encryption applied on a risk basis.
i
Art. 21(2)(i): human resources security, access control policies and asset management
Relevant CSF 2.0 categories
PR.AAID.AM
Additional verification: HR security (joiners, movers and leavers) is covered alongside access and assets.
j
Art. 21(2)(j): multi-factor or continuous authentication, secured communications and secured emergency communications, where appropriate
Relevant CSF 2.0 categories
PR.AAPR.DS
Additional verification: the risk-based decision on where these measures are appropriate is documented.

Most organisations already have partial controls in these areas. The usual gaps are controls that exist informally, undocumented processes and recovery plans that have never been tested. A correspondence in the table tells you that a CSF outcome is relevant to a NIS2 provision. It does not tell you that the control is implemented, that it works, or that it meets the legal requirement in your Member State.

NIS2 obligations that need checking beyond the CSF mapping

There is no fixed list of NIS2 requirements that sit outside the CSF. The differences depend on your entity category, the national law that applies, any implementing acts and how you have implemented the controls. The following areas usually need a specific legal check.

Incident reporting deadlines

CSF 2.0 covers incident management and communication (RS.MA, RS.CO) but sets no regulatory deadlines. NIS2 Article 23 applies to significant incidents: those that have caused or can cause severe operational disruption or financial loss for the entity, or considerable damage to others. For a significant incident, the entity must send an early warning to its CSIRT or competent authority within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report within one month of the incident notification. The authority can also request intermediate reports.

Your incident response plan should show who decides whether an incident is significant, who reports, and through which national channel. Triage should assess and document the classification from the start, without waiting for forensic analysis to finish. National law and, for certain digital providers, Implementing Regulation (EU) 2024/2690 set more detailed criteria.

Important

An early warning does not require a complete picture of the incident. It needs the information available at that point, including whether unlawful or malicious action is suspected and whether there could be a cross-border impact. Missing a deadline can amount to a breach of the reporting obligation that applies to you.

Entity classification, registration and supervision

NIS2 distinguishes essential and important entities (Article 3). Classification depends on sector, entity type, size and national designation, and it determines the supervisory regime rather than a uniform audit frequency. Essential entities are subject to ex ante and ex post supervision (Article 32). Important entities are supervised ex post, typically when there is evidence or an indication of non-compliance (Article 33). The maximum fines Member States must provide for are at least EUR 10 million or 2% of total worldwide annual turnover, whichever is higher, for essential entities, and at least EUR 7 million or 1.4% for important entities (Article 34). CSF 2.0 has no equivalent tiering.

You also need to check registration or identification duties in each Member State where you are in scope, and which authority supervises you. For certain digital providers, Article 26 assigns jurisdiction to the Member State of their main establishment in the EU.

Management body duties

CSF 2.0 GOVERN covers roles, responsibilities and oversight (GV.RR, GV.OV). NIS2 Article 20 is more specific: management bodies must approve the cybersecurity risk-management measures, oversee their implementation and follow training, and Member States must ensure that members can be held liable for infringements, in line with national law. For essential entities, Article 32(5) allows a temporary ban on a person exercising managerial functions, but only where earlier enforcement measures have proved ineffective and a deadline to remedy has passed. None of this creates automatic personal liability after an incident.

In practice, keep evidence of documented approval of the measures, periodic reporting to the management body, management review of effectiveness, and training records for its members. A CSF profile document on its own does not show this.

Other areas to check

  • Statutory supply chain requirements. What national law and implementing acts expect in supplier selection, contracts and monitoring, beyond good practice under GV.SC.
  • Documentation and evidence. For DNS, cloud, data centre, content delivery network, managed service, managed security service and trust service providers and certain online platforms, Implementing Regulation (EU) 2024/2690 sets detailed technical and methodological requirements for the Article 21(2) measures and criteria for significant incidents.
  • Supervision and enforcement. Inspections, audits, information requests and binding instructions under national law (Articles 31 to 33).
  • National additions. Member States can go further than the directive, so the national text is the reference.

Notes for healthcare, financial services, hospitality and suppliers

Healthcare

Not every healthcare organisation is an essential entity. Healthcare providers are listed in Annex I of NIS2, but whether a given organisation is in scope, and in which category, depends on the entity type, its size, any special rules and the national law of the Member State. NIS2 does not apply in the UK. Some UK health bodies may be designated under the NIS Regulations 2018, and NHS organisations work with the Data Security and Protection Toolkit (DSPT), which overlaps with several Article 21 themes such as incident handling, access control and data security. UK providers with EU operations need to check the national law of each Member State concerned. A CSF 2.0 programme gives a common baseline across these regimes, but each still needs its own legal check.

Financial services

For financial entities covered by DORA, Regulation (EU) 2022/2554, the starting point is DORA, not NIS2. NIS2 Article 4 provides that where a sector-specific Union legal act imposes cybersecurity risk-management or incident reporting requirements that are at least equivalent in effect, the corresponding NIS2 provisions, including supervision and enforcement, do not apply. Recital 28 of NIS2 identifies DORA as such an act. Building a NIST CSF and NIS2 programme first and adding DORA afterwards is therefore not the efficient default for these firms.

Assess DORA first: ICT risk management, classification and reporting of major ICT-related incidents, digital operational resilience testing, including threat-led penetration testing where required, and ICT third-party risk. CSF 2.0 can still serve as a complementary internal framework for organising controls. Our DORA gap analysis guide explains how to approach that assessment. UK firms are affected through EU-established group entities or as ICT third-party service providers to EU financial entities.

Hospitality

Hotels, resorts, restaurant chains and travel agencies generally fall outside the NIS2 Annex I and II sectors. They may still meet NIS2-derived requirements when they supply in-scope customers, who pass security clauses down to suppliers, or when they provide a digital service that is itself in scope. PCI DSS, already required for businesses that take cards, gives a head start: many of its controls correspond to PROTECT and DETECT outcomes in CSF 2.0. Areas worth attention are governance documentation (GOVERN), incident handling procedures and security clauses in contracts with property management system and payment platform providers.

UK suppliers to EU customers

A UK company that supplies an EU essential or important entity is not subject to NIS2 for that reason alone. It may, however, face contractual requirements derived from NIS2, because its customer must manage supply chain security under Article 21(2)(d): security clauses, incident notification to the customer, audit rights or evidence of controls. Certain non-EU providers of specific digital services in the EU, including DNS, cloud computing, data centre, content delivery network, managed service and managed security service providers, online marketplaces, online search engines and social networking platforms, are directly subject to NIS2 through the jurisdiction rules in Article 26 and must designate a representative in the EU. NIST CSF 2.0 is a sound way to organise and evidence controls for EU customers, but it does not by itself demonstrate NIS2 conformity.

Frequently asked questions

What are the ten NIS2 Article 21 measure areas?

Article 21(2) lists: (a) policies on risk analysis and information system security; (b) incident handling; (c) business continuity, such as backup management and disaster recovery, and crisis management; (d) supply chain security; (e) security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure; (f) policies and procedures to assess the effectiveness of cybersecurity risk-management measures; (g) basic cyber hygiene practices and cybersecurity training; (h) policies and procedures on cryptography and, where appropriate, encryption; (i) human resources security, access control policies and asset management; (j) multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communication systems, where appropriate.

How does DORA relate to NIST CSF 2.0 and NIS2?

DORA (the Digital Operational Resilience Act, Regulation (EU) 2022/2554) applies to EU financial entities and is a sector-specific act in the sense of NIS2 Article 4, as recital 28 of NIS2 confirms. For financial entities covered by DORA, its rules on ICT risk management, incident reporting, resilience testing and ICT third-party risk apply instead of the equivalent NIS2 provisions. Assess DORA first. NIST CSF 2.0 can be used as a complementary internal framework, but it does not replace DORA's specific requirements.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Talk to Cyvra

Need to align your NIS2 and NIST CSF programmes?

We run CSF-based gap assessments with a specific NIS2 applicability and requirements check, for organisations in the Netherlands and UK that want one integrated programme rather than two parallel workstreams.

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.