Does the Cbw apply to you?
The Dutch Cybersecurity Act (Cyberbeveiligingswet, or Cbw) took effect on 15 August 2026. It puts the EU's NIS2 directive into Dutch law. Whether it covers you depends on your sector and size. Below: who it covers, what it requires, and where we can help.
Background
NIS2, the EU's directive on network and information security, took effect in January 2023 and raised security requirements across 18 sectors. Member states had until October 2024 to turn it into national law. The Netherlands missed that deadline.
The Tweede Kamer passed the Cyberbeveiligingswet (Cbw) on 15 April 2026 and the Eerste Kamer followed on 7 July. The law has applied since 15 August 2026. It makes the board responsible for cyber risk, sets strict deadlines for reporting incidents, and covers managed service providers directly.
- Jan 2023
NIS2 takes effect across the EU
It replaces the first NIS directive and widens the scope to 18 sectors.
- Oct 2024
The Netherlands misses the deadline
No national law yet, so companies in scope are left waiting.
- May 2025
The European Commission steps in
Infringement procedures against the Netherlands and other member states that hadn't acted.
- Apr and Jul 2026
Both chambers pass the Cbw
Tweede Kamer on 15 April, Eerste Kamer on 7 July.
- 15 Aug 2026
The Cbw applies
Registration, reporting and the other obligations can now be enforced.
Who it applies to
Organisations have to work out for themselves whether they're in scope. It depends on your sector and your size.
Sectors of high criticality
- Banking and finance
- Energy
- Transport
- Healthcare
- Digital infrastructure
- Public administration
Other critical sectors
- Postal and courier
- Waste management
- Food production
- Manufacturing
- Online marketplaces
- Research
Size: 50 or more employees, or more than €10 million turnover or balance sheet total
An organisation in one of these sectors that passes either threshold is in scope. Some digital providers are in scope whatever their size. Below the threshold, larger customers and investors may still ask for the same controls, and suppliers to in-scope companies are often asked to show them.
IT providers are covered too
Managed service providers, including IT outsourcing partners, fall under the law themselves once they pass the size thresholds. And because the law covers your supply chain, your provider's security becomes part of your own.
of the EU cyber incidents ENISA recorded in 2025 hit sectors covered by NIS2. ENISA Threat Landscape 2025
What the law requires
A risk assessment and duty of care
Write down your cyber risks, keep the assessment current, and take measures that fit your size and exposure. This duty of care is the basis for everything else.
The board is responsible
The board approves the security measures, oversees how they're carried out and completes training on them. Under NIS2, board members can be held liable for failures, and for essential entities a supervisor can temporarily bar a director from a management role.
Report incidents fast
For a significant incident: an early warning within 24 hours, a notification within 72 hours and a final report within a month. Reporting late is a breach in itself.
Supply chain security
You answer for the security of critical suppliers: IT providers, SaaS tools and MSPs. Contracts need to reflect that, and you need to keep the evidence.
Identity and access controls
MFA, least privilege and regular access reviews are now the minimum. Identity governance becomes the centre of how you show compliance.
Register with the NCSC
Organisations in scope register in the national register kept by the NCSC and keep their details up to date.
How we help
Compliance baseline
A two-week gap analysis mapped to the NIS2 and Cbw articles. You get a costed plan with the most important fixes first.
Identity and access
Okta or JumpCloud set up for governance from day one: single sign-on, MFA, role-based access and joiner, mover and leaver controls.
Evidence pack
Control mappings, screenshots, policies and reports, ready for auditors, investors and the regulator.
Incident readiness
Tested runbooks for the 24-hour window, with a documented chain of custody for the logs.
Ongoing monitoring
Quarterly access reviews, anomaly alerts and SaaS discovery, so compliance stays current between audits.
Who does what
Compliance is shared work. We agree the split up front so nothing falls between two chairs when the auditor arrives.
What Skales takes on
Full technical ownership of your workplace: devices, identity and SaaS settings.
Device security
Managed Mac, Windows and mobile devices: disk encryption, OS updates, firewall, remote wipe and live compliance reporting.
Identity and access
Central identity provider, phishing-resistant MFA, single sign-on, role-based access and provisioning logs.
Joiners and leavers
Accounts closed as soon as HR offboards someone, with time-stamped logs that show it happened.
SaaS settings
Google Workspace hardening, DKIM, SPF and DMARC, data retention, and exportable baseline reports.
Access governance
Access matrices for quarterly reviews and user lists your auditor can sign off.
AI tools at work
Single sign-on and MFA on AI tools, an approved-tool list and written guardrails for what staff can share with them.
What stays with your team
Business operations and company governance.
Production and cloud
We don't configure or secure your AWS, GCP or Azure environments, and we don't audit or review your code. Production cloud and code review stay with your engineers.
Policies
We provide the technical evidence. Your ISMS, business continuity plan and disaster recovery policy are yours to write.
HR and physical security
We automate the technical side of onboarding. Background checks, NDAs, keycards and CCTV stay with HR.
24/7 monitoring and reporting
We are not a 24/7 security operations centre. If there's an incident we provide the technical logs, but reporting to your CSIRT and supervisor within 24 hours is your obligation.