In the Netherlands: the Cyberbeveiligingswet
In the Netherlands NIS2 applies through the Cyberbeveiligingswet (Cbw; Stb. 2026, 187), which entered into force together with the Cyberbeveiligingsbesluit (Stb. 2026, 189) on 15 August 2026 (Article 35 of the Besluit). The Cbw uses the same two tests as the Directive: an entity type listed in Annex 1 or 2 to the Cbw, whose transport entries follow Annex I of the Directive, and size under Recommendation 2003/361/EC. An Annex 1 entity that exceeds the ceilings for medium-sized enterprises is an essential entity (Cbw Article 8(1)(f)); a medium-sized Annex 1 entity, and an Annex 2 entity that is medium-sized or larger, is an important entity unless it qualifies as an essential entity (Article 12(1)(a) and (b)). The minister concerned designates an entity listed in Annex 1 or 2 as essential where one of the criteria in Article 9(1) applies, for example where it is the only provider in the Netherlands of a service essential for critical societal or economic activities. Entities in scope provide their details for the national register (Article 44); take appropriate and proportionate measures to manage the risks to their network and information systems (Article 21(1)), including supply-chain security (Article 21(3)(d)); have those measures approved by the management body, whose members must meet the knowledge and skills requirement by 15 August 2028 if they were in office on 15 August 2026, or within two years of appointment if appointed later, and hold a training certificate (Article 24(1) to (5)); and report significant incidents: an early warning without undue delay or, if that is not possible, within 24 hours of becoming aware (Article 26(1)), a notification without undue delay or, if that is not possible, within 72 hours of becoming aware (Article 27(1)), an intermediate report on request (Article 28) and a final report no later than one month after the notification (Article 29(1)); if the incident is still ongoing then, a progress report at that point and the final report within one month after handling the incident (Article 29(2)). A board member who breaches Article 24(2) to (6) can be fined up to EUR 25,000 (Article 93). For transport the competent authority is the Minister of Infrastructure and Water Management (Article 15(1)).
Coverage is two tests: listed entity type, then size
Article 2(1) applies the directive to public or private entities of a type referred to in Annex I or II that qualify as medium-sized enterprises under Recommendation 2003/361/EC or exceed the medium-size ceilings, and that provide services or carry out activities in the Union. Under that Recommendation, medium-sized means fewer than 250 staff and an annual turnover not exceeding EUR 50 million and/or a balance-sheet total not exceeding EUR 43 million; the practical entry floor is therefore roughly 50 staff or more than EUR 10 million in annual turnover and balance-sheet total. The size test has exceptions: regardless of size, an Annex I or II entity can be brought in scope if it is, for example, the sole provider in a Member State of a service essential for critical societal or economic activities, if disruption of its service could significantly affect public safety, security or health, or if it is designated as a critical entity under Directive (EU) 2022/2557 (Article 2(2)–(3)). Within scope, Article 3 splits entities into two categories: Annex I entities that exceed the medium-size ceilings are essential entities; most other in-scope entities — including medium-sized transport entities and Annex II types — are important entities, although an entity designated as critical under Directive (EU) 2022/2557 is an essential entity regardless of size, and a Member State can classify an entity it brings in scope under Article 2(2)(b)–(e) as essential (Article 3(1)(e)–(f)). The category determines the supervision regime and the fine ceiling, not the substance of the duties.
What Annex I lists for transport — and what it does not
Annex I point 2 names the transport entity types per subsector. Air: air carriers used for commercial purposes, airport managing bodies and airports including entities operating ancillary installations within airports (a heading that can capture cargo-handling operations on airport grounds), and air traffic control operators. Rail: infrastructure managers and railway undertakings, including operators of service facilities. Water: inland, sea and coastal passenger and freight water transport companies (not the individual vessels), managing bodies of ports including their port facilities and entities operating works and equipment contained within ports — a heading that can capture cargo and container terminals inside a port area — and vessel traffic services. Road is narrower than often assumed: only road authorities responsible for traffic-management control and operators of intelligent transport systems are listed; commercial road hauliers are not. Annex II adds postal service providers including courier services, and — relevant for distribution-heavy shippers — food businesses engaged in wholesale distribution and industrial production and processing. Freight forwarding and warehousing do not appear as entity types in either annex.
Not listed does not mean untouched: the supply-chain pull-through
Article 21(2)(d) obliges every in-scope entity to address supply-chain security, including the security-related aspects of its relationships with direct suppliers and service providers. Article 21(3) sharpens this: entities must take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of their products and cybersecurity practices, including secure development procedures. A freight forwarder, warehouse operator or logistics IT provider that serves an in-scope carrier, terminal, port or manufacturer can therefore expect NIS2-derived requirements from that customer — security questionnaires, contractual clauses, audit rights — even though the law imposes no direct statutory duty on a forwarder or warehouse operator as such. The obligation sits with the in-scope customer (Cbw Article 21(3)(d) and (4)). A logistics IT provider that manages or operates ICT for customers can itself be in scope as a managed service provider (Cbw Annex 1, ICT service management (business-to-business)).
The duties: ten minimum measures and fixed reporting clocks
In-scope entities must take appropriate and proportionate technical, operational and organisational measures, based on an all-hazards approach, covering at least ten areas listed in Article 21(2): policies on risk analysis and information-system security; incident handling; business continuity including backup management, disaster recovery and crisis management; supply-chain security; security in acquisition, development and maintenance of systems including vulnerability handling and disclosure; procedures to assess the effectiveness of the measures; basic cyber hygiene and cybersecurity training; policies on cryptography and, where appropriate, encryption; human-resources security, access control and asset management; and, where appropriate, multi-factor or continuous authentication and secured communications. Proportionality is explicitly scaled to the entity's risk exposure, its size, and the likelihood and severity of incidents (Article 21(1)). Reporting follows fixed clocks under Article 23: an incident is significant if it has caused or can cause severe operational disruption or financial loss, or considerable damage to other parties; a significant incident triggers an early warning within 24 hours of awareness, an incident notification within 72 hours, an intermediate report on request, and a final report no later than one month after the incident notification or, if the incident is still ongoing then, a progress report at that point and the final report within one month of handling the incident (Article 23(3) and (4)(a)–(e)). Where relevant, recipients of the services may also need to be informed.
Board accountability, supervision, and where implementation stands
Article 20 of the Directive places compliance at the top: Member States ensure that management bodies approve the cybersecurity risk-management measures, oversee their implementation and can be held liable for infringements by the entity of Article 21, and that their members follow training (Article 20(1) and (2)). In the Netherlands, Cbw Article 24 requires approval by the management body and knowledge, skills and a training certificate for each board member. Supervision differs by category: essential entities face proactive oversight including on-site inspections, regular and targeted security audits and security scans (Article 32), while important entities face ex post supervision triggered by indications of non-compliance (Article 33). For infringements of Article 21 or 23, fine ceilings are set at a maximum of at least EUR 10 million or 2% of total worldwide annual turnover for essential entities, and at least EUR 7 million or 1.4% for important entities, whichever is higher (Article 34). The transposition deadline was 17 October 2024, with application from 18 October 2024, and Member States were to list essential and important entities by 17 April 2025 based on information the entities themselves must submit (Articles 41, 3(3)–(4)). National implementation remains uneven: the Commission sent reasoned opinions to 19 Member States on 7 May 2025 and on 8 July 2026 referred Ireland, Spain, France and the Netherlands to the Court of Justice for failing to notify transposition measures. The Netherlands has since transposed the directive: the Dutch Cyberbeveiligingswet (Cbw; Stb. 2026, 187) and the Cyberbeveiligingsbesluit (Stb. 2026, 189) entered into force on 15 August 2026. For operations in other Member States, the national law of that Member State applies.
What to do
Map each activity of your organisation against the entity types in Annex 1 and 2 to the Cbw (which follow Annex I point 2 and Annex II of Directive (EU) 2022/2555), apply the size test from Recommendation 2003/361/EC, and record a written conclusion per activity — essential (Cbw Article 8), important (Article 12), out of scope, or indirectly exposed via customer contracts. That conclusion decides registration (Article 44), supervision and every later step.
Sources
Cyberbeveiligingswet, Stb. 2026, 187: Art. 8(1)(f) and 12(1)(a)-(b) (essential and important entities), Art. 9 (designation), Art. 15(1) (competent authority), Art. 21 (duty of care, incl. 21(3)(d) supply chain), Art. 24 (management body), Arts 26-29 (early warning 24 hours, notification 72 hours, intermediate report, final report one month, progress report while the incident is ongoing), Art. 44 (register), Art. 93 (fine for a board member up to EUR 25,000); entry into force 15 August 2026 under Art. 35 of the Cyberbeveiligingsbesluit, Stb. 2026, 189. ↗ Directive (EU) 2022/2555 (NIS2), Art. 2(1): "This Directive applies to public or private entities of a type referred to in Annex I or II which qualify as medium-sized enterprises ... or exceed the ceilings for medium-sized enterprises"; Art. 3 (essential/important entities, incl. Art. 3(1)(e)–(f) essential status for CER-designated and Member State-designated entities, and 17 April 2025 listing); Annex I point 2 (Transport: air, rail, water, road entity types), Annex II point 1 (postal service providers including courier services); Art. 20 (management bodies approve, oversee, can be held liable, training), Art. 21(2)(a)–(j) (ten minimum measures, incl. (d) supply-chain security), Art. 23(3)–(4) (significant incident; 24h early warning, 72h notification, final report within one month, progress report while the incident is ongoing), Art. 32–33 (supervision), Art. 34(4)–(5) (fines: at least EUR 10 million/2% and EUR 7 million/1.4%), Art. 41 (transposition by 17 October 2024, application from 18 October 2024). ↗ Last verified against the primary sources: 2026-11-08
More on Cyber & resilience
Follow this topic
Get an email whenever something changes here. No account needed; confirm by email (double opt-in).
We use your email address only to send updates about this topic. You can unsubscribe at any time. See our privacy policy.
← All transport & logistics topics