NIS2 Netherlands: healthcare and labs under the Cbw
In the Netherlands, the question "are we in scope?" is settled faster than in most sectors: a care provider with 50 FTE is in, and there is no transition period. Here are the exact thresholds, the regulator, the sector CSIRT, and the five actions to take this week.
The short answer
Yes, in the large majority of cases. On NIS2 Netherlands healthcare, Dutch law is blunter than in most sectors: the Cyberbeveiligingswet (Cbw) has been in force since 15 August 2026 and covers roughly 8,000 organisations in the Netherlands[1]. A care provider (zorgaanbieder) reaching 50 full-time equivalents is in scope[4].
Two Dutch specifics matter more than the European text. First, there is no transition period: the regulator takes the view that the sector should already be compliant, because NEN 7510 has been legally required for years for anyone processing health data[2]. Second, healthcare is the only sector with its own ministerial regulation, the Cyberbeveiligingsregeling voor de Zorg, published in the Staatscourant on 14 August 2026[3].
The trap: a laboratory is not in scope merely because it is a laboratory. The law names "EU reference laboratories", not ordinary diagnostic labs[4]. A Dutch lab falls under the Cbw if it is itself a care provider in the legal sense. Otherwise it gets the obligations second-hand, as a supplier to a hospital that will push them down by contract.
Are you in scope? The Dutch criteria
The Cbw names five healthcare categories[4]: care providers (zorgaanbieders), EU reference laboratories, entities carrying out R&D on medicinal products, manufacturers of basic pharmaceutical products and preparations, and manufacturers of medical devices.
Then comes the size threshold, which the Dutch call the size cap:
- at least 50 full-time equivalents; or
- failing that, annual turnover above 10 million euros and a balance sheet total above 10 million euros[4].
Three Dutch exceptions are worth knowing, because they pull in organisations that thought they were out:
- a manufacturer of medical devices is always an important entity, whatever its size[4];
- an organisation designated by the Ministry of Health (VWS) automatically becomes an essential entity, even below the threshold; the same applies if it is designated a critical entity under the Wet weerbaarheid kritieke entiteiten[4];
- youth care providers (jeugdhulpaanbieders) are outside the Cbw: they are held to ISO 27001 or an equivalent standard through the Jeugdwet[2].
Essential or important: what actually changes
| Criterion | Important entity | Essential entity |
|---|---|---|
| Size | 50+ FTE, or turnover and balance sheet above 10 M€ | More than 250 FTE, or turnover above 50 M€ and balance sheet above 43 M€ |
| Substantive duties | Identical | Identical |
| IGJ supervision | Ex post, on a signal or after an incident | Ex ante and ex post, with no incident or signal needed |
Thresholds and supervisory regime: Ministry of Health and IGJ[4][5]. Every provision of the Cbw applies to both categories; the difference is how the inspectorate comes knocking[4]. A general hospital is therefore almost certainly essential. A 60-person independent clinic will be important: same duties, but supervision triggered by a signal.
What the law requires in the Netherlands
The IGJ (Inspectie Gezondheidszorg en Jeugd) is the supervisory authority for healthcare, and Z-CERT is the sector CSIRT, formally designated by an order published in the Staatscourant on 5 October 2026[6]. The inspectorate lists five duties, plus one right[5]:
- Registration: register with the national NCSC portal and keep your details current[5].
- Duty of care (zorgplicht): a risk assessment you perform yourself, then proportionate measures, supply chain included[4].
- Board accountability: the board is ultimately responsible and must take appropriate training to be able to judge risks and measures[5].
- Incident reporting: a significant incident must be reported within 24 hours via MijnNCSC. The NCSC automatically forwards every health-sector report to the IGJ and to Z-CERT[5].
- Duty to inform: tell the people affected — patients, staff, chain partners — about the consequences and what they can do[5].
The right is support from Z-CERT before and during an incident[4]. Note that a Cbw report does not replace a personal data breach notification to the Autoriteit Persoonsgegevens. The IGJ works with the AP on privacy matters, and with nine other Dutch regulators under a joint cooperation protocol[5].
The Dutch shortcut: NEN 7510
The Cbw duty of care largely overlaps with NEN 7510, already mandatory for care providers through the Wabvpz[2]. Since 31 March 2026, Annex E of NEN 7510-2:2024+A1:2026 contains an explicit mapping between the standard and the Cyberbeveiligingswet — previously it referred to NIS2[7]. So an organisation genuinely working to the standard has done most of the distance. What remains separate: NCSC registration, incident reporting, and formal board responsibility[8]. Certification is not mandatory, but the standard does require regular independent assessment[9].
One calendar deadline to diarise: existing NEN 7510 certificates must be converted to NEN 7510:2024 by 20 February 2027[10].
What the inspectorate actually finds
This is not theory. In late 2025 the IGJ examined information security at 87 Dutch mental health organisations (ggz). Findings published on 27 May 2026: the inspectorate says it is concerned, and expects those not yet working to the standard to commission at least one independent, competent assessment within the year[9]. It had already run the same exercise with hospitals, GP out-of-hours posts, independent clinics and elderly care organisations[9].
In other words: in the Netherlands, sector supervision of NEN 7510 existed before the Cbw and continues. What the law mainly adds is registration, the 24-hour clock, and a board that is named as responsible.
The first five actions
- Settle scope, in writing. Download the decision tree (beslisboom) published by the Ministry of Health and keep the dated outcome[4]. Every organisation must assess applicability itself[8]; under inspection, that record is what speaks.
- Register with the NCSC portal if you are in scope, and name the person who keeps the entry current[5].
- Write the 24-hour procedure. Who decides an incident is "significant", who files on MijnNCSC at night and at weekends, who calls Z-CERT, who notifies the AP if personal data is involved. Run it once as a dry run.
- Bridge NEN 7510 to the Cbw. Take Annex E of NEN 7510-2:2024+A1:2026 and mark, line by line, what is in place and what is missing[7].
- Train the board and date the session. Management training is an obligation in the law, not a recommendation[5].
For a cross-border comparison, the Belgian version of this exercise is covered in our guide on NIS2 in Belgium for healthcare, hospitals and laboratories, where the authority and the timetable differ. For another sector under the same Dutch law, see NIS2 in the Netherlands for transport and logistics. The Dutch healthcare scope is summarised on our NIS2 Netherlands healthcare page.
At CyberNovaLabs.io
We start with scope and evidence, not with a tool. The two-minute NIS2 check is free and places you. After that, two things are usefully delegated: training for the board and management, which the Cbw requires, and preparing the evidence the IGJ will ask for. Our work is quoted per engagement, with no minimum term. We promise no compliance outcome: the applicability decision stays yours, and this guide is not legal advice.
Sources
- Digitale Overheid — Cyberbeveiligingswet (NIS2-richtlijn)
- IGJ — Vragen over cyberbeveiliging
- Data voor gezondheid (VWS) — Cyberbeveiligingsregeling voor de Zorg gepubliceerd in de Staatscourant
- Data voor gezondheid (VWS) — De zorgsector onder de Cyberbeveiligingswet
- IGJ — Toezicht op cyberbeveiliging
- Staatscourant 2026, 28763 — aanwijzing Z-CERT als CSIRT voor de zorg
- NEN — NEN 7510-2 geactualiseerd met amendement (31/03/2026)
- NEN — Cyberbeveiligingswet van kracht: bouw voort op uw NEN 7510-aanpak
- IGJ — Inspectie maakt zich zorgen over informatiebeveiliging in de ggz (27/05/2026)
- NEN — NEN 7510: informatiebeveiliging in de zorg
Qualified meetings, no lock-in.
Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.
Read next
Critical PHP flaws: your website is affected (21/10/2026)
Two critical vulnerabilities in PHP, the engine under most small-business websites, allow unauthenticated remote code execution. Patches shipped on 21 October 2026. What to check this week, and what will never be fixed.
Read the article →October 22, 2026 · 9 min readNIS2 Netherlands: are software vendors and IT providers in scope?
Publishing software is not a listed category in Dutch law. Running a client's infrastructure, hosting it, monitoring it, is. Here is how to settle your own case in ten minutes, with the Dutch dates, the right regulator and the main-establishment rule that decides who inspects you.
Read the article →October 13, 2026 · 7 min readB2B appointment setting for manufacturing and industry
In manufacturing, a meeting is not won by a better script. It is won by reaching the right role in the decision chain, hitting the right window in the plant calendar, and having your supplier qualification file ready before the first call.
Read the article →October 12, 2026 · 7 min readFlink data breach: an ex-employee login was enough (05/10/2026)
A former employee's login was enough to get into Flink on 25 September 2026. The criminals first asked each affected person for about 10 euros, then 235,000 euros from the company; nobody paid, so the file went up for sale on 5 October. Three lessons any SME in the Netherlands, Belgium, France or Luxembourg can copy.
Read the article →October 11, 2026 · 7 min readNIS2 France: are transport and logistics firms in scope?
A road haulier is not in NIS2 scope because it moves freight. But two regimes already bind French operators today, and a third arrives through their customers. The texts, the dates and the figures, with no invented fines.
Read the article →October 10, 2026 · 8 min readNIS2 Belgium: are software vendors and IT providers in scope?
Software publishing is not listed in the Belgian NIS2 law. Managed services, hosting and SaaS are. Here is how to settle your own case in ten minutes, with the Belgian dates, the CyberFundamentals framework, and what still reaches you if you are out of scope.
Read the article →