Skip to content

Knowledge base · Cbw/NIS2 for transport and logistics

Must you have a policy on cryptography and encryption under the Cbw (NIS2 21(2)(h))?

Yes. You record policy and procedures on the use of cryptography: when you use it, which encryption you use, and who is responsible for implementation and key management (Cbw 21(3)(h), Cbb 13).

In force now (since 15 August 2026)Trusq editorial · checked against the official textLast verified:

Next step: Set up the Cbw duties in Trusq

What the act requires

Policy and procedures for cryptography and, where appropriate, encryption are point h [1]. The NIS2 directive names the same topic [2].

How the Cyberbeveiligingsbesluit elaborates this

The Cbb requires established, written policy with processes on cryptography. It states at least in which cases you use cryptography, which types of encryption you use, and who is responsible for implementation and key management [3].

What you record in practice

  • where you use encryption: connections with on-board computers, customer portals, laptops, backups
  • which types of encryption and how you apply them
  • who manages the keys and certificates

Does this also apply to cloud and IT service providers?

If your company falls under Cbb Article 4 (among others cloud, data centres and managed (security) services), Cbb Articles 6 to 18 do not apply [4] and Implementing Regulation (EU) 2024/2690 elaborates this measure. The obligation under Cbw Article 21 remains.

What Trusq bases this on

These released rules are in Trusq and are read again with every publication; if a rule changes, this page changes with it.

  • Organisation: Maintain policies for cryptography and, where appropriate, encryption. NIS2 21(2)(h), Cbw 21(3)(h)
  • Per ICT system: Apply your cryptography policy to this ICT system, including encryption where appropriate. Cbw 21(3)(h), NIS2 21(2)(h)

Sources

  1. [1] Cbw Art. 21(3)(h) (Dutch Cyberbeveiligingswet (Cbw); Dutch law, unofficial translation). Cbw Article 21(3)(h). Original Dutch text:
    3. De maatregelen, bedoeld in het eerste lid, zijn gebaseerd op een benadering die alle gevaren omvat en tot doel heeft netwerk- en informatiesystemen en de fysieke omgeving van die systemen tegen incidenten te beschermen, en omvatten ten minste het volgende: […] h. beleid en procedures inzake het gebruik van cryptografie en, in voorkomend geval, encryptie;
    Source, retrieved on 2 October 2026.
  2. [2] NIS2 Art. 21(2)(h) (Directive (EU) 2022/2555 (NIS2)). The NIS2 counterpart: Article 21(2)(h).
    2. The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the following: […] (h) policies and procedures regarding the use of cryptography and, where appropriate, encryption;
    Source, retrieved on 2 October 2026.
  3. [3] Cbb Art. 13 (Dutch Cyberbeveiligingsbesluit (Cbb); Dutch law, unofficial translation). Cbb Article 13: the policy covers use, type of encryption and responsibility for implementation and key management. Original Dutch text:
    3. In het beleid en de processen en procedures, bedoeld in het eerste en tweede lid, worden in ieder geval uitgewerkt: a. in welke gevallen cryptografie ingezet wordt; b. in voorkomende gevallen, welke typen encryptie worden gebruikt en de wijze waarop deze worden toegepast; c. wie binnen de entiteit verantwoordelijk zijn voor de implementatie van cryptografie; en d. wie binnen de entiteit verantwoordelijk zijn voor het sleutelbeheer.
    Source, retrieved on 2 October 2026.
  4. [4] Cbb Art. 4 (Dutch Cyberbeveiligingsbesluit (Cbb); Dutch law, unofficial translation). Cbb Article 4 excludes Articles 6 to 18 for, among others, cloud, data centre and managed service providers. Original Dutch text:
    Gelet op artikel 1 van de Uitvoeringsverordening (EU) 2024/2690 zijn de artikelen 6 tot en met 18 niet van toepassing op de volgende essentiële entiteiten en belangrijke entiteiten: a. DNS-dienstverleners; b. registers voor topleveldomeinnamen; c. aanbieders van cloudcomputingdiensten; d. aanbieders van datacentrumdiensten; e. aanbieders van netwerken voor de levering van inhoud; f. aanbieders van beheerde diensten; g. aanbieders van beheerde beveiligingsdiensten; h. aanbieders van onlinemarktplaatsen; i. aanbieders van onlinezoekmachines; j. aanbieders van platforms voor socialenetwerkdiensten; en k. verleners van vertrouwensdiensten.
    Source, retrieved on 2 October 2026.

Related questions

What does the Cbw require on personnel, access management and an inventory of assets (NIS2 21(2)(i))?Is multi-factor authentication mandatory under the Cbw (NIS2 21(2)(j))?What does the duty of care of the Cyberbeveiligingswet involve?Does the Cbw duty of care also apply to your TMS, WMS or telematics in the cloud?

Next step

Register your organisation and your Cbw sector. Trusq sets up the duty of care, the reporting duty, the tasks of the management body and the registration as actions, each with the evidence that is expected and the article it rests on.

Set up the Cbw duties in Trusq

Not sure whether the Cbw applies to your business? Take the Cbw check (in Dutch).

Looking for a specialist? We will look with you for a suitable specialist; mediation is not guaranteed.

This page gives general information based on the text of the law. It is not legal advice for your situation.