- NIST CSF 2.0 is a voluntary framework any organisation can use; NIS2 imposes legal obligations on defined categories of EU entities through national law
- NIS2 does not apply in the UK, which has the NIS Regulations 2018 and the Cyber Security and Resilience Bill before Parliament; it matters to UK firms with EU operations, certain digital services in the EU, or in-scope EU customers
- 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
Two frameworks, one integrated programme
NIST published CSF 2.0 in February 2024. It is a voluntary framework: any organisation, of any size or sector, can use it to organise how it manages cybersecurity risk, and it does not prescribe how outcomes should be achieved. NIS2, Directive (EU) 2022/2555, is different in kind. It is EU law that imposes cybersecurity risk-management, incident reporting and governance obligations on defined categories of essential and important entities, through each Member State's national legislation.
Member States had to transpose NIS2 by 17 October 2024 and apply those measures from 18 October 2024. Several were late, so the obligations that actually apply to an organisation depend on the national law of each country where it operates and on how the entity is classified there. In the Netherlands, for example, NIS2 is implemented through the Cyberbeveiligingswet (Cbw), in force since 15 August 2026. In the UK, NIS2 does not apply at all: the NIS Regulations 2018 remain the domestic regime, and the Cyber Security and Resilience Bill is before Parliament.
Having EU customers does not bring an organisation into scope. NIS2 generally applies to medium-sized and large entities in the sectors listed in its Annexes I and II, but some entities are covered regardless of size, such as certain providers of public electronic communications networks, trust service providers, DNS service providers and top-level domain name registries, and national law can designate others. A UK company with EU clients is not an NIS2 entity for that reason alone.
Where an organisation is in scope, running two separate projects with separate assessments and remediation plans duplicates effort. A CSF 2.0 programme can organise the controls, owners and evidence, while a specific NIS2 assessment checks the legal requirements that apply. Relating each NIS2 provision to the CSF outcomes it touches lets you reuse controls and evidence, provided the legal requirements and the actual implementation are assessed in their own right.
What changed in NIST CSF 2.0
The original NIST Cybersecurity Framework had five functions: Identify, Protect, Detect, Respond, Recover. Version 2.0 adds a sixth: GOVERN.
GOVERN wraps around the other five functions. It addresses organisational context, risk management strategy, roles and responsibilities, policy, oversight and cybersecurity supply chain risk management. Where version 1.1 described what controls to implement, GOVERN addresses who is accountable for those controls, how risk appetite is set, and how cybersecurity connects to wider business strategy.
This addition is relevant to NIS2. Article 20 requires the management bodies of essential and important entities to approve the cybersecurity risk-management measures, oversee their implementation and follow training, and Member States must ensure that members of those bodies can be held liable for infringements under national law. GOVERN gives you a structure to document that governance (GV.RR, GV.PO, GV.OV), although it does not by itself show that the legal duties are met.
Version 2.0 also widened its intended audience beyond critical infrastructure operators to organisations of all sizes across all sectors.
The six CSF 2.0 functions in brief:
- GOVERN (GV): Organisational context, risk management strategy, roles, policy, oversight, supply chain
- IDENTIFY (ID): Asset management, risk assessment, improvement
- PROTECT (PR): Identity and access control, awareness and training, data security, platform security, infrastructure resilience
- DETECT (DE): Continuous monitoring, adverse event analysis
- RESPOND (RS): Incident management, analysis, reporting and communication, mitigation
- RECOVER (RC): Recovery plan execution, recovery communication
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.
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.
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.
Running one integrated programme
One possible implementation sequence, depending on your context:
- Confirm applicability. Establish whether NIS2 applies, in which Member States, as which entity category, and whether a sector-specific act such as DORA takes precedence. For UK organisations, start with the UK NIS Regulations and your EU footprint.
- Build a current profile. Use CSF 2.0 to record current and target outcomes across the six functions, with named owners.
- Relate NIS2 requirements to the CSF. Use the correspondences above to link each Article 21(2) measure area to CSF categories, then assess each requirement against its legal wording rather than assuming coverage.
- Assess the obligations not covered. Incident reporting, registration, management body duties, national supervision and any implementing act requirements.
- Prioritise remediation. Weigh legal obligation, operational risk, asset criticality, exploitability, business consequences and existing compensating controls, not only regulatory enforcement risk.
- Keep an integrated matrix of requirements, controls and evidence. Use one shared evidence repository, with references to the applicable requirements, so a control documented once can support both the CSF profile and the NIS2 assessment.
A CSF-based programme with a specific NIS2 assessment is usually more efficient than two separate projects. The saving comes from reusing controls and evidence, not from assuming that a CSF profile proves legal compliance.
A compliance assessment model
The matrix below keeps apart three things that are often merged. Mapping a requirement to the CSF shows relevance. Implementing a control shows that something exists and works. Legal conformity is a judgement on whether the specific requirement in the applicable national law is met. A mapping is not an implementation, and an implementation is not, by itself, legal conformity.
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.
What to do next
If you are in scope of NIS2 and have no working framework yet, NIST CSF 2.0 is a practical way to organise the programme. GOVERN gives a structure for the governance that Article 20 expects, and the correspondences to Article 21 show where controls and evidence can be reused. The legal requirements still need their own assessment.
If you already use CSF 1.1, moving to 2.0 is worthwhile for GOVERN alone. The changes are incremental rather than a rewrite, so the effort is manageable.
CSF profiles, which document current and target state separately, also work well as a board-level communication tool. Combined with documented approval and periodic reporting, they help evidence the management body oversight that Article 20 requires.
If you are unsure where to start, a CSF-based assessment combined with a specific NIS2 applicability and requirements check is an efficient first step. It sets your baseline, identifies priority gaps and produces a reusable evidence set, while keeping the legal questions separate.
NIST Cybersecurity Framework 2.0 documentation, including the full framework core, implementation tiers and profiles, is available at nist.gov/cyberframework. The full texts of the NIS2 Directive, Implementing Regulation (EU) 2024/2690 and DORA are published on EUR-Lex.