dutch-cybersecurity-actnis2cybersecurityboard-dutiesai-policy

Dutch Cybersecurity Act: In Scope, and What Changes for AI?

November 17, 20269 min readPixel Management

This article is also available in Dutch

Since 15 August 2026, a care provider, food wholesaler or machine builder in the Netherlands with 50 FTE or more has had to register with the NCSC, and nobody sends a letter first.

The Dutch Cybersecurity Act (Cyberbeveiligingswet, Cbw) is the Netherlands' implementation of the EU NIS2 Directive: a law that requires more than 8,000 organisations in 18 sectors to register, manage cyber risk, report serious incidents and make the board ultimately responsible. AI isn't in the law. Your AI use still runs through it, by way of the general duty of care.

This is a different thing from the directive we covered in April in NIS2 for SMBs. The Cbw is the Dutch statute that applies today, with its own article numbers, fines and an implementing decree. For how it sits next to the AI Act, see our overview of AI legislation in the Netherlands.

Does the Dutch Cybersecurity Act apply to your company?

Whether the Dutch Cybersecurity Act applies depends on your sector, the type of service and your size, and you decide that yourself. The NCTV, the Dutch national security coordinator, says many organisations fall under the law "van rechtswege", by operation of law. So don't wait to be designated.

The NCSC's size test is simple. You're large enough with 50 or more FTE, or with fewer than 50 FTE if both annual turnover and balance sheet total exceed €10 million. Partner and linked enterprises count too, so a 30 FTE operating company inside a 200 FTE group counts the group, not its own payroll.

Your situationUnder the Cbw?CategorySupervision
Annex 1 sector (healthcare, energy, rail, drinking water, managed ICT services, cloud), 250+ FTEYesEssentialProactive
Annex 1 sector, 50–249 FTEYesImportantReactive
Annex 2 sector (manufacturing NACE C26–C30, food, chemicals, waste, post), 50+ FTEYesImportantReactive
Listed sector, under 50 FTE and turnover or balance sheet up to €10 millionNo, except DNS, telecoms and trust services among othersNoneNone
Road haulier (no post or courier work)No: the annex lists only road authorities and ITS operatorsNoneNone
Supermarket or hospitalityNo: only wholesale and industrial production or processingNoneNone
Waste as a side activityNo: only if waste management is your main activityNoneNone
Construction, accountancy, law firms, non-food retailNo: sector isn't in the annexesNoneThrough customers

This follows the Cbw's annexes and the NCTV's explanation. Manufacturing is narrower than it sounds: only NACE divisions 26 to 30 (electronics, electrical equipment, machinery, motor vehicles, other transport equipment) plus medical devices. The chemicals row is wider than it sounds. It also covers companies producing articles from substances or mixtures in the sense of the EU's REACH regulation. If you make physical products outside divisions 26 to 30, take that row to your lawyer rather than ticking it off yourself.

Two AI traps in the scope test

A software company can enter the law through its own service. Annex 1 lists managed service providers, which the Cbw describes as parties that install, manage, operate or maintain ICT products, applications or systems, on site or remotely. If you run customers' AI environments with 50 or more FTE, read that definition carefully.

The same goes for a hosted AI product. Recital 33 of the NIS2 Directive counts Software as a Service among the cloud models. Whether your product meets the Cbw definition of a cloud computing service (on-demand, scalable, elastic, shareable computing resources) isn't always obvious and needs a legal check. The FAQ of the RDI, the Dutch digital infrastructure regulator, doesn't address it.

SMB and in scope: the blind spot in the Dutch threat report

The Cybersecuritybeeld Nederland 2026 (CSBN), the national threat assessment published on 6 November, contrasts the mkb, the Dutch SMB segment, with large companies under the Cbw since 15 August. That contrast doesn't work for a 120 FTE food wholesaler. The CSBN uses the RVO definition of the mkb, everything under 250 employees, and the Cbw starts at 50. Between those two lines you're both.

The sentence people will remember: "Kleine organisaties en het mkb kunnen hun weerbaarheid niet zelfstandig verhogen", small organisations and SMBs can't raise their resilience on their own. The report makes suppliers, regulators and government jointly responsible. For a company under the law, that changes nothing: the duty stays with you.

The figures the CSBN quotes from ABN AMRO research show the distance, though they cover all Dutch SMBs and not just firms under the Cbw. 26 percent of SMBs have a formal cyber incident response plan, against 49 percent of large companies. 78 percent of SMBs use AI to some degree, and only 9 percent have a formal policy for AI models, against 32 percent of large companies.

What the Dutch Cybersecurity Act requires

The Dutch Cybersecurity Act sets four duties, and the first is already running.

DutyWhat the law asks
RegistrationThrough Mijn.NCSC.nl with eHerkenning (Dutch business login) at level 3 or higher; report changes within two weeks
Duty of careAppropriate, proportionate measures on ten topics (art. 21(3)), detailed in arts. 5–18 of the Cybersecurity Decree
Incident reportingEarly warning within 24 hours, notification within 72 hours, final report within one month of the notification
BoardApprove measures, oversee them, demonstrable knowledge, training certificate (art. 24)

The RDI warns that failing to register, or registering incorrectly, can lead to a fine or a penalty order, and advises making someone such as the director or CISO responsible for keeping details current. Allow lead time if you don't have eHerkenning at that level yet.

The duty of care isn't a loose framework. The Cybersecurity Decree (Cyberbeveiligingsbesluit) asks for written, demonstrably applied policy on most topics, from a complete and current asset inventory (art. 16) to protected logs (art. 8) and tested recovery (art. 9). ISO 27001 and NEN 7510 aren't named in it. A certificate isn't a legal requirement, so if someone sells you one as a necessity, ask where it says so. The bar is proportionate: the NCSC names exposure to risk, size, likelihood of incidents and possible impact as the yardstick.

Only "significant incidents" are reportable. Under art. 25(2), that means incidents that cause or could cause serious operational disruption or financial loss, or considerable damage to others. Thresholds differ per sector. One report through MijnNCSC reaches both your CSIRT and the supervisor.

What's at stake for directors under the Cbw

A director can face a personal fine of up to €25,000 under the Cbw for missing the requirements on knowledge, keeping it current and the certificate. Company fines are higher, and the ceilings are set in the statute.

BreachEssential entity (art. 80)Important entity (art. 87)
Duty of care and reporting (arts. 21, 21a, 25–30)€10 million or 2% of worldwide turnover€7 million or 1.4% of worldwide turnover
Other breach€1 million€1 million
Board member, art. 24(2)–(6) (art. 93)€25,000€25,000

The higher amount applies, calculated on the undertaking the entity belongs to. Both percentages only overtake the fixed amount at €500 million in turnover (€10 million / 2% and €7 million / 1.4%), so for a company of 50 to 250 FTE the fixed ceiling is almost always the limit. It's a maximum, not a tariff.

Executive directors must have demonstrable knowledge no later than two years after commencement, so by 15 August 2028, and keep it current afterwards. Supervisory board members aren't covered by the training duty. The certificate states name, date, topics and provider, and the decree sets no number of hours. That deadline only covers knowledge and the certificate. Approving the measures is on the board's desk now.

Supervision differs per category. Under reactive supervision, the supervisor steps in after an incident or on signs of non-compliance, and the NCTV writes that enforcement can reach individual directors "in bepaalde gevallen", in certain cases. For companies under proactive supervision, the competent authority can ask a court to suspend a director if a decision isn't followed (art. 78). The RDI says it wants to get to know its sectors better in the first year, through letters, introductory meetings and questionnaires. That isn't a grace period, and we found none anywhere.

What does AI use change about the duty of care?

Legally, AI use changes nothing about the duty of care: the Cbw, the Cybersecurity Decree and the NCTV and RDI FAQs don't mention AI. There's no AI register under this law and no ban on any model. What follows is our reading of the general risk approach, not official guidance.

The clearest government signal isn't a law but a joint statement of 24 September 2026 from the Dutch intelligence services, the NCSC, the NCTV, the Public Prosecution Service, the government CIO and the police. It calls it necessary to include the risks of AI in cybersecurity policy, explicitly covering "het gebruik van AI-modellen binnen jouw organisatie", the use of AI models inside your own organisation.

Put that next to the decree and you get these questions, which a supervisor could plausibly ask after an incident.

Cybersecurity DecreeWhat it asksThe AI question for your board
Art. 16, assetsComplete, current inventoryWhich AI tools, integrations and agents are running, including ones a department switched on itself?
Art. 10, supply chainPeriodic checks of direct suppliersDoes your AI vendor meet your requirements, and when did you last check?
Art. 11, buying and changeProcurement policy, change managementWho approves a new model or integration?
Art. 15, accessPeriodic review of identities and rightsDoes each agent have its own identity with minimal rights?
Art. 8, incidentsDetection, protected logsCan you see afterwards what an agent read and did?
Art. 9, continuityRecovery plan, crisis planWhat happens to the process if the AI service is down for a day?
Art. 12, awarenessCyber hygiene and trainingDoes everyone know what can't go into a public chatbot?

That last row has a Dutch example. The CSBN cites the municipality of Eindhoven, where according to the local audit office, sensitive data on vulnerable residents was entered into public AI tools between September and October 2025. Controls around that flow are covered in AI and data security, and staff rules belong in an AI policy.

Agents get their own row because they act rather than talk. Art. 25 looks at an incident's effect, not its cause. An agent that takes down a process by mistake gets measured against the same yardstick as ransomware. Reducing that chance is the subject of securing AI agents. A data leak through an AI tool can also trigger a separate GDPR notification to the Dutch Data Protection Authority.

Service

Learn more about AI consulting?

View service →

What to arrange as a director this quarter

For the Dutch Cybersecurity Act, these are the six actions we'd plan first, in this order.

  1. Establish whether you're in scope. Run the RDI's NIS2 self-assessment and record the result and your reasoning. If you're out of scope, stop here and don't buy a Cbw programme.
  2. Register. Arrange eHerkenning level 3, register through Mijn.NCSC.nl and name an owner for changes.
  3. Table a board decision. Art. 24(1) requires approval of the measures. A risk analysis with no board decision doesn't meet that.
  4. Rehearse the 24 hours. Who reports on a Saturday evening, with which rights on MijnNCSC? The services' joint statement asks for a plan people have practised.
  5. Put AI in the inventory and the supplier list. Start with whatever touches customer data or production systems. Record security terms the way we describe in buying AI software.
  6. Plan the training. Book it for every executive director and keep the certificate. Anyone joining later has two years from appointment.

Out of scope, but in someone's supply chain

A supplier doesn't automatically fall under the Dutch Cybersecurity Act, the NCTV writes, but organisations under the law can set requirements for their direct suppliers. That's a contractual demand from your customer, not a legal duty on you. The decree forces that customer to check periodically (art. 10), and the RDI applies this to suppliers outside the EU too.

If you supply software, management or AI services to a hospital or machine builder, expect questionnaires and audit clauses. If you can show how you handle AI vendors, access and logs, you've got a sales argument. And if you build custom software for such customers, look at the Cyber Resilience Act as well, which sets its own rules for products with digital elements.

Curious how much time you could save?

Request a free efficiency audit. We'll analyze your processes and show you where the gains are, no strings attached.