In the Netherlands, NIS2 compliance means meeting the Cyberbeveiligingswet (Cbw), the Dutch act that transposes the directive. It asks four things of an organisation in scope: register, take appropriate security measures, report significant incidents on time and have the board formally own the approach.
The act has applied since 15 August 2026, and plenty of organisations are still working through their gap analysis. That is understandable. Two parts of the job, though, should not wait for the wider programme.
Does the Dutch Cybersecurity Act apply to you?
It covers organisations that provide essential or important services across 18 sectors. Energy, transport, banking, healthcare, drinking water, digital infrastructure, managed ICT services and public administration are the obvious ones, but waste management, chemicals and manufacturing are in there too.
Nobody will write to tell you. The Dutch government is clear that organisations must establish for themselves whether the act applies. The self-assessment tool from the RDI, the Dutch digital infrastructure inspectorate, gives a first indication. Where a subsidiary or an unusual service leaves room for doubt, get a lawyer's view and keep it on file. That record is your first piece of evidence.
The four obligations
Registration
Organisations in scope register in the national entity register run by the NCSC, the Dutch National Cyber Security Centre, through its mijn.ncsc.nl portal. You supply your name, address, contact details including IP ranges, your sector and subsector, and the EU member states where you provide services. The NCSC reckons it takes no more than ten minutes.
Keeping it current takes more thought. Who updates those IP ranges when the network changes, and who looks after the account once the named contact moves on?
Duty of care
The duty of care requires appropriate and proportionate measures to manage the risks to your network and information systems. The NCSC sets out ten required measures: risk analysis, policies on personnel, access and assets, a business continuity plan, incident response, cyber hygiene, network security policy, supply chain security, cryptography, multi-factor authentication and an assessment of whether the measures actually work.
This is where most of the effort goes. It is also where you have room to prioritise, because what counts as appropriate depends on your risk profile. If continuity planning is a gap, see how to write a business continuity plan.
Incident reporting
Significant incidents go to your CSIRT and your supervisory authority. The NCSC describes a phased reporting duty: an early warning as soon as possible and within 24 hours at the latest, an incident notification within 72 hours, and a final report within one month. If the incident is still running at that point, a progress report will do until the final report follows. Reports go through the central portal on mijn.ncsc.nl.
What makes an incident significant is set out in sector-specific regulations. For healthcare, for example, the Cyberbeveiligingsregeling voor de zorg defines the thresholds and names the IGJ, the health inspectorate, as supervisor. Check which regulation and which supervisor apply to your sector.
Board accountability
The board carries final responsibility and can be held liable if the duty of care is not met. In practice that means the board approves the measures, oversees how they are implemented and takes part in training. A CISO running the programme without formal board sign-off leaves the organisation exposed.
My advice: start with registration and reporting
I would not open with a large programme that tackles all ten measures at once. Start with the two things a supervisor can check tomorrow, and that you can sort out in weeks rather than months: your registration and a reporting process that works.
Registration is binary: you are on the register or you are not. Reporting runs against the clock. A 24-hour early warning leaves no time to work out on a Saturday night who has the authority to call an incident significant. Settle these points in advance:
- who decides whether an incident is significant, using your sector's thresholds;
- who has access to mijn.ncsc.nl, and who covers for them;
- how you reach those people out of hours;
- who briefs the board, and at what point.
Then run one exercise with a realistic scenario and check whether the early warning could have gone out within a few hours. If it could not, you know where to put capacity first. For how to handle the first days of a real incident, read incident response retainer or interim DFIR specialist.
Build out the wider programme after that. By then the foundations a supervisor looks at first are in place, and the remaining measures can be prioritised on risk.
Who you need
The act does not prescribe job titles. In practice someone has to lead the work and keep the board involved, usually a CISO or information security officer. A GRC specialist often joins to get the risk analysis and the evidence in shape. The reporting process belongs with someone who has incident response experience, in-house or on retainer.
Much of this work is temporary: set it up, prove it works, then hand it over to your own team. For a fuller look at the profiles involved, see demonstrating NIS2 compliance: checklist and talent.
Need a hand?
We supply interim and permanent specialists for Cyberbeveiligingswet programmes, from GRC and compliance specialists to an interim CISO. Our NIS2 page explains how we work.
Need your reporting process in place quickly, or someone to get the registration and board decision done this month? Call or email me through the contact page.

