NIS-2: a preview of 2026

Tom de Wit

We previously wrote a blog about the implementation of NIS-2 in Dutch legislation. Although NIS-2 should have been implemented in Dutch legislation by October 2024, this is still not the case. The current legislative proposals are expected to come into force at the end of June 2026, at which point the current Network and Information Systems Security Act (the implementation of NIS-1) will be repealed. 

The implementation of NIS-2 will take place through the Cybersecurity Act (‘Cyberbeveiligings wet’ or Cbw), for which the proposal was sent to the House of Representatives (‘Tweede Kamer’) in the summer of 2025. The obligations included in the Cbw are elaborated in lower legislation and regulations, including the Cybersecurity Decree (‘Cyberbeveiligingsbesluit’ or Cbb) and various ministerial regulations for different sectors. These lower regulations contain elaborations of the duty of care and the reporting obligation.

The Cbw distinguishes between important and essential entities. To this end, the Cbw contains appendices listing sectors that are considered essential or important. This distinction is particularly important for monitoring compliance by the authorities, proactively for essential entities and reactively for important entities. It is important for organizations to determine the sector in which they operate. Not only to distinguish between essential and important, but also because the lower sectoral regulations may have different implications for issues such as duty of care and duty to report.

A special regime applies to entities operating in the digital sector, such as cloud or SaaS service providers or data storage services. For these entities, the duty of care and reporting obligations are included in a special European implementing regulation (EUR 2024/2690).

Under NIS-2 and its implementation in national regulations, cybersecurity also becomes an explicit administrative responsibility: the board must approve risk management measures, supervise their implementation, and have sufficient knowledge and expertise, demonstrated through demonstrable education and training.

Duty of care

The most important obligation for entities is the duty of care included in the regulations. The Cbw sets out the basic principle for this: entities must take security measures consisting of appropriate and proportionate technical, operational, and organizational measures to manage the security risks of their network and information systems. This is intended to prevent the risk of incidents, but also to limit the consequences for customers and other parties involved in the event of a possible incident.

As in NIS-2, the Cbw (Article 21(3)) sets out the minimum duties of care that every entity must comply with:

  • policy on risk analysis and security of information systems
  • incident handling
  • business continuity, such as backup management and emergency contingency plans, and crisis management
  • supply chain security, including security-related aspects concerning the relationships between the entity and its direct suppliers or service providers
  • security in the acquisition, development, and maintenance of network and information systems, including vulnerability response and disclosure
  • policies and procedures to assess the effectiveness of cybersecurity risk management measures
  • basic cyber hygiene practices and cybersecurity training
  • policies and procedures on the use of cryptography and, where appropriate, encryption
  • security aspects relating to personnel, access policies, and asset management

These basic measures are further elaborated in the Cbb and subsequently also in underlying ministerial regulations. 

Four ministries opted for a joint ministerial regulation, namely Economic Affairs (EA), Climate and Green Growth (KGG), Agriculture, Fisheries, Food Security and Nature (AFFN), and Infrastructure and Water Management (IenW).

This joint ministerial regulation contains a uniform generic elaboration of the duty of care for the aforementioned sectors. The first version of the ministerial regulation of IenW, EA, KGG, and AFFN on the duty of care was drawn up jointly and made available for consultation in February 2025. Subsequently, joint amendments were made and each ministry incorporated the rules on the duty of care into its own ministerial regulation, in which they also separately regulated the reporting obligation.

This is what the Ministry of Infrastructure and Water Management did, for example, with a further elaboration of the threshold values for reporting within the sub-sectors of IenW (such as transport, drinking water, and wastewater).

In addition, the Ministries of the Interior and Kingdom Relations (IKR) and Health, Welfare and Sport (HWS) have also further elaborated both the duty of care and the duty to report in a separate ministerial regulation (which has been submitted for consultation) for the government and healthcare sectors. The Ministry of Education, Culture and Science (ECS) will not present  its ministerial regulation for the education sector until a later date. 

The ministerial regulations for HWS and IKR differ from other ministerial regulations in that parties to whom the ministerial regulation HWS applies can comply with the duty of care under the Cbw by having a NEN 7510 (version 2024) certificate, an IS0 27001 or ISO 27002 certificate (version 2022) or meet an equivalent level of protection. For government entities falling under the ministerial regulation of IKR this will be ISO 27001: 2023, ISO 27002: 2022 in combination with the Baseline informationsecurity for governmental organizations.

Due to the layered regulations, it is quite a puzzle to determine which requirements entities must meet on the basis of the duty of care. This depends in particular on the sector in which an entity operates and on the basis of which the ministerial regulation for that sector further elaborates the duty of care in relation to the Cbw and the Cbb.

All in all, the table below provides an overview of the ministerial regulations as they are currently known.

Ministerial regulationMinistryDuty of care and/or reporting obligation?
Cybersecurity regulation for the government sector[1]Ministry of the Interior and Kingdom RelationsDuty of care and duty to report
Cybersecurity regulations for the Ministry of Economic Affairs[2]Ministry of Economic AffairsDuty of care and reporting obligation
Cybersecurity regulations IenW[3]IenWDuty of care and reporting obligation
Cybersecurity and resilience regulations for critical entities in the energy sector[4]KGGDuty of care and reporting obligation
Cybersecurity regulation for the food sector[5]AFFNDuty of care and reporting obligation
Cybersecurity Regulations in Healthcare[6]HWSDuty of care and reporting obligation
–Ministry of Education, Culture and Science–

Duty to report

In addition to the duty of care mentioned above, entities are required to report any significant incidents that occur. This must be done within the time limits and to the authorities specified in the Cbw, Cbb, and the underlying ministerial regulations. 

The Cbw specifies the deadlines for reporting and subsequent reports. There are short reporting deadlines of 24 hours (early warning) and 72 hours (reporting). The entity must then report and submit a report on the incident within a specified period. However, the underlying ministerial regulations also impose additional requirements with regard to reports and reports on incidents.

The definition of what is considered a significant incident is included in the various sectoral ministerial regulations that contain threshold values (whereas the Cbw only describes what is considered a significant incident at a high level of abstraction). For example, the IenW ministerial regulation includes separate thresholds for each subsector (such as transport, drinking water, and wastewater) to determine what qualifies as a significant incident, and for the healthcare sector, these thresholds are included in the ministerial regulation for healthcare. 

The Cbw stipulates that a significant incident must be reported to both the relevant Computer Security Incident Response Team (CSIRT) and the competent supervisory authority for the sector concerned. For the Netherlands, the National Cyber Security Center (NCSC) is in principle the CSIRT. However, depending on the sector, a different CSIRT may be designated. For example, Z-CERT is designated in the ministerial regulation for the healthcare sector.

In addition to reporting to the CSIRT and the supervisory authority, entities are also obliged to inform customers about significant incidents that could have adverse consequences for the provision of services.

As with the duty of care, the reporting obligation is also subject to a patchwork of regulations. As an entity, it is important to find out which ministerial regulation applies. In the area of reporting obligations, the standards for what constitutes a significant incident vary, but there are also minor differences in the procedures for reporting obligations and subsequent reports and statements.

Preparation for NIS-2

Now that the regulatory landscape for NIS-2 is becoming clearer, it is important not to wait until the end of June 2026. Entities can already start taking the necessary preparatory measures based on the interaction between Cbw, Cbb, and the various ministerial regulations.

These include:

  • Conducting a risk assessment
  • Drawing up and adapting the necessary policy documentation
  • Inventorying suppliers and amending supplier contracts that are relevant to (cyber) security
  • Drawing up training and awareness programs in the field of (cyber) security
  • Drawing up or amending (existing) reporting procedures to the authorities and incident handling

So don’t wait until June 2026, take action sooner and ensure that, as a (critical or important) entity, you have already taken the necessary steps to comply with the NIS-2 regulations.


[1] Concept, consultation closed 12/23/2025, https://www.internetconsultatie.nl/cyberbeveiligingsregelingoverheid/b1

[2] Concept, consultation closed 21-12-2025, https://www.internetconsultatie.nl/regelingcyberbeveiligingez/b1

[3] Draft, consultation closed 22-12-2025, https://www.internetconsultatie.nl/cyberbeveiligingsregeling_ienw/b1

[4] Draft, consultation closed 21-12-2025, https://www.internetconsultatie.nl/cyberbeveiligingweerbaarheidkritiekeentiteiten/b1

[5] Draft, consultation closed 12/21/2025, https://www.internetconsultatie.nl/regelingcyberbeveiliginglevensmiddelensector/b1

[6] Draft, consultation closed 22-12-2025, https://www.internetconsultatie.nl/cyberbeveiligingsregelingzorg/b1v