Guide Compliance Cybersecurity

NIST CSF 2.0 and NIS2: how they differ and how to implement both

NIST CSF 2.0 and the NIS2 Directive can be used together, but they are different in nature. The CSF is a voluntary framework for organising cybersecurity risk management, while NIS2 sets legal obligations for certain entities in the European Union. NIS2 does not apply in the UK, but it matters to UK organisations with EU operations or in-scope EU customers. By relating regulatory requirements to CSF outcomes, an organisation can reuse controls and evidence, as long as it assesses the legal requirements and their actual implementation separately.

13 May 2026
Updated 19 November 2026
8 min read
Key takeaways
  • 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.

6
CSF 2.0 functions, up from five in version 1.1. GOVERN is new.
10
measure areas listed in NIS2 Article 21(2)
Oct 2024
NIS2 transposition deadline (17 October), with measures to apply from 18 October

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

The correspondence table for the ten Article 21(2) measure areas, the NIS2 obligations that need checking beyond it and notes for healthcare, financial services, hospitality and suppliers are on our companion page, NIS2 and NIST CSF 2.0 control mapping.

Running one integrated programme

One possible implementation sequence, depending on your context:

  1. 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.
  2. Build a current profile. Use CSF 2.0 to record current and target outcomes across the six functions, with named owners.
  3. Relate NIS2 requirements to the CSF. Use the correspondence table to link each Article 21(2) measure area to CSF categories, then assess each requirement against its legal wording rather than assuming coverage.
  4. Assess the obligations not covered. Incident reporting, registration, management body duties, national supervision and any implementing act requirements.
  5. Prioritise remediation. Weigh legal obligation, operational risk, asset criticality, exploitability, business consequences and existing compensating controls, not only regulatory enforcement risk.
  6. 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.
Practical note

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.

1
Legal provision
The specific article or national provision, for example Article 21(2)(b) or its national equivalent.
2
Applicability
Whether and how the provision applies to this entity, and in which Member States.
3
CSF mapping
The related CSF 2.0 categories or subcategories.
4
Control implementation
The control in place, its scope and how it operates.
5
Evidence
Documents, records, logs or test results that show the control operating.
6
Coverage
Full, partial or none, judged against the specific requirement rather than the CSF category.
7
Gap
What is missing to meet the requirement.
8
Owner
The person accountable for closing the gap.
9
Remediation
The planned action, deadline and status.

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.

Frequently asked questions

Does NIST CSF 2.0 automatically meet NIS2?

No. NIST CSF 2.0 is a voluntary framework, while NIS2 is EU law applied through national legislation. Every Article 21(2) measure area has related CSF 2.0 categories, but a correspondence is not legal equivalence. You still need to confirm applicability and entity classification, meet the Article 23 deadlines for significant incidents, evidence the management body duties in Article 20, and check national law and any implementing acts. Implementing CSF outcomes well puts you in a good position; it does not prove conformity.

Does NIS2 apply to UK organisations?

Not as UK law. The UK regime is the NIS Regulations 2018, and the Cyber Security and Resilience Bill is before Parliament. NIS2 can still reach UK organisations in three ways: through group entities established in an EU Member State that fall within its scope; directly, for certain digital service providers offering services in the EU, which must designate an EU representative under Article 26; and indirectly, through contractual security requirements from EU customers that are in scope.

Is NIST CSF mandatory in the Netherlands or UK?

No. NIST CSF is a voluntary framework published by the US National Institute of Standards and Technology. It is not required under Dutch or UK law. Regulators assess whether the applicable legal requirements are met, not which framework you used to organise your controls. NIST CSF is widely used as a working framework because it is flexible, sector-agnostic and well documented, not because it is mandatory.

Can we use ISO 27001 instead of NIST CSF 2.0 for NIS2?

Yes. Both ISO 27001 and NIST CSF 2.0 can support the NIS2 Article 21 measures. ISO 27001 is more prescriptive and certification-focused, which some organisations prefer for supplier assurance. NIST CSF is more flexible as an internal working framework. Many organisations use both: CSF for internal programme management and ISO 27001 for external certification. Whichever you use, the NIS2-specific obligations, such as incident reporting, classification and registration, management body duties and national supervision, still need a separate legal check.

What is the GOVERN function in NIST CSF 2.0?

GOVERN is the function added in NIST CSF 2.0, published in February 2024. It addresses organisational context, risk management strategy, roles and responsibilities, policy, oversight and cybersecurity supply chain risk management. It was added because CSF 1.1 covered operational and technical controls but did not clearly address governance and board-level accountability. For NIS2, GOVERN is the function most relevant to the Article 20 management body duties, although meeting those duties requires documented approval, oversight and training.

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.