Founders tend to treat these as three separate problems: pass an audit, satisfy an investor, comply with a new Dutch law. They share one answer. The IT and security foundation that satisfies one satisfies all three, and building it once costs far less than reacting to each request as it lands.
Does the Cbw apply to you?
The Cyberbeveiligingswet, the Dutch version of NIS2, was passed by the Eerste Kamer on 7 July 2026 and applies from 15 August 2026. Whether it covers your company depends on your sector and your size.
Essential entities are large companies (250 or more employees, or more than €50 million in turnover and a balance sheet above €43 million) in the high-criticality sectors of Annex I: energy, transport, banking, financial market infrastructure, health, drinking water, digital infrastructure and a few others.
Important entities are medium-sized companies (50 or more employees, or more than €10 million in turnover or balance sheet total) in a wider set of sectors across Annex I and II. That adds postal services, waste management, chemicals, food, manufacturing, digital providers and research, among others.
Some digital infrastructure and trust service providers are in scope regardless of size, because their sector counts as systemically important. If you run DNS services, a cloud platform or a qualified trust service, a small headcount doesn't take you out.
For companies of 10 to 200 people, the important-entity threshold is the one to watch. Plenty of well-funded young companies cross 50 employees, or €10 million in turnover or balance sheet total, well before they think of themselves as regulated.
Your customers and investors will ask anyway
Enterprise buyers and institutional investors stopped waiting for regulation years ago. Investor due diligence often asks for SOC 2-style controls before a Series A or B. An enterprise procurement team sends a security questionnaire before signing, whatever the Cbw says about your headcount. Once your buyer or investor expects proper identity management, device control and incident response, the legal threshold barely matters, because the commercial one already applies.
That's what we tell founders who say they're not in scope yet. Even if the law doesn't cover you, the buyers and investors it was written for will still ask.
What needs to be in place
Article 21(2) of NIS2 lists the minimum security measures. Nearly every point maps onto IT basics a growing company should have anyway.
Identity. A real identity provider with single sign-on and phishing-resistant MFA, not a spreadsheet of shared logins. Article 21(2)(j) names access control policies and asset management as required measures.
Devices. Enrolled, managed, patched and encrypted by default. A laptop that leaves the company without being wiped is an incident that hasn't been found yet.
Joiners and leavers. Automated from your HR system, so access is granted and removed on the day someone starts or leaves, not whenever IT gets to it.
Incident response. This is where the Cbw is strict: an early warning to the authorities within 24 hours, a notification within 72 hours and a final report within a month. You can't build that process after an incident has started.
Governance and evidence. Policies that are written down, reviewed and followed, with a record that proves it. Auditors and regulators ask the same thing: show me the evidence.
Supply chain. Article 21(2)(d) requires supply chain security. You need to know what your vendors and SaaS tools can reach, and what happens if one of them is breached.
Build it in the right order
Treat this as an architecture, not a shopping list you tick off once, because the order matters. Identity comes before device management, because a device is only as trustworthy as the accounts on it. Joiner and leaver automation comes before incident response, because you can't respond well to an incident involving an account that shouldn't have existed. Governance and evidence sit on top, because an auditor or investor can't see any of the other layers unless you can prove them.
Build it in that order, once, and you give the same answer to an auditor, a funding round or a regulator: here's what we have, here's how it works, here's the evidence. Build it tool by tool, for whichever deadline is loudest this quarter, and you'll pay more for a weaker version of the same thing.
Sources
- Opsio: NIS2 size threshold explained
- Kiteworks: NIS2 applicability
- Houthoff: Dutch Cybersecurity Act (Cyberbeveiligingswet) enters into force 15 August 2026
- Rijksoverheid: Cyberbeveiligingswet en Wwke vanaf vandaag van kracht
Want to know where your company stands?
Book a free call