NIS2 scope: the port as a high-criticality entity
The NIS2 Directive (Directive (EU) 2022/2555) replaced the first NIS Directive (Directive (EU) 2016/1148) and extended EU cybersecurity obligations across a broad set of sectors. Its Annex I, headed 'Sectors of high criticality', includes the transport sector, and within the water subsector it lists 'Managing bodies of ports as defined in Article 3, point (1), of Directive 2005/65/EC ... including their port facilities as defined in Article 2, point (11), of Regulation (EC) No 725/2004', alongside inland, sea and coastal water-transport companies. A seaport operator is therefore squarely within the material scope of the directive. Whether a specific organisation is caught, and in which category, follows from the national transposing law and the tests in Article 3: an entity of an Annex I type that exceeds the ceilings for medium-sized enterprises is an essential entity (Article 3(1)(a)), and an in-scope entity of an Annex I or II type that does not qualify as essential is an important entity (Article 3(2)). In the Netherlands the Cyberbeveiligingswet (Cbw; Stb. 2026, 187) applies since 15 August 2026: Annex 1 to the Cbw lists port managing bodies including their port facilities, a port managing body that is at least medium-sized is, by operation of law and without a decision by the supervisor, an essential entity if it exceeds the medium-size ceilings (Cbw Art. 8(1)(f)) or an important entity if it is medium-sized (Art. 12(1)(a)); a critical entity under the Wet weerbaarheid kritieke entiteiten is essential regardless of size (Art. 8(1)(i)). It provides its details for the national register itself (Art. 44). For transport the competent authority is the Minister of Infrastructure and Water Management (Cbw Art. 15(1)); officials of the Human Environment and Transport Inspectorate (ILT) are designated to supervise compliance (Cbw Art. 68(1); Stcrt. 2026, 24155, Art. 1). The distinction matters because it drives the supervisory and enforcement regime that applies to the entity.
NIS2 duties: governance, risk management and incident reporting
For a port in scope, NIS2 imposes three linked obligations. Under Article 20(1) of the Directive, Member States ensure that the management body approves the entity's cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements by the entity of Article 21; in the Netherlands, Cbw Article 24 requires approval by the management body and knowledge, skills and a training certificate for each board member. Article 21(2) sets a minimum baseline of measures on an all-hazards basis, including policies on risk analysis and information-system security, incident handling, business continuity (backup management, disaster recovery and crisis management), supply-chain security covering the relationship with direct suppliers and service providers, and security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure. Article 23 adds a phased reporting duty for significant incidents: an early warning within 24 hours of becoming aware of the incident, an incident notification within 72 hours, and a final report not later than one month after that notification. If the incident is still ongoing then, provide a progress report at that point and a final report within one month of handling the incident (Article 23(4)(d) and (e); Cbw Article 29(1) and (2)). The enforceable obligations for a port flow from its Member State's transposing law; in the Netherlands the Cbw sets the reporting duty in Articles 25 to 29.
The Cyber Resilience Act: securing the digital products in the chain
Where NIS2 regulates the organisation, the Cyber Resilience Act (Regulation (EU) 2024/2847) regulates the products. Article 3 defines a 'product with digital elements' as a software or hardware product and its remote data-processing solutions; under Article 2(1) the regulation covers such products whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. The regulation assigns obligations along the supply chain, with distinct duties for manufacturers (Article 13), importers (Article 19) and distributors (Article 20), and requires cybersecurity to be built in and vulnerabilities to be handled across the product lifecycle. It entered into force on 10 December 2024, the twentieth day after publication, and applies in phases: the main body of obligations from 11 December 2027, manufacturers' reporting duties under Article 14 from 11 September 2026, and the conformity-assessment provisions in Chapter IV (Articles 35 to 51) from 11 June 2026. For ports, the practical effect falls on procurement and operational technology: terminal-operating software, sensors, gate systems and industrial control equipment placed on the EU market as products with digital elements must, from 11 December 2027, meet the CRA's essential cybersecurity requirements and bear the CE marking.
How the two regimes interact
NIS2 and the CRA are designed to be complementary rather than duplicative, addressing different layers of the same risk. NIS2 obliges the port, as an entity, to manage its own cyber risk — including, through the supply-chain-security measure in Article 21(2), the security of its relationships with direct suppliers and service providers. The CRA raises the baseline security of the products themselves at the point they are placed on the market. A port operator within NIS2 scope can therefore treat a supplier's CRA conformity as one input into its own risk-management measures, but CRA-compliant products do not by themselves discharge the organisation's NIS2 duties, which remain broader and organisation-wide. Because the outcome for any specific port depends on its NIS2 classification, the national transposition of the directive and the CRA's phased timeline, the points above are general information rather than legal advice, and a definitive scoping should be confirmed against the applicable national law.
What to do
Determine whether your port entity is an essential or an important entity — in the Netherlands under Cbw Articles 8 and 12, without a confirmation by the supervisor — and provide its details for the national register (Cbw Art. 44). That classification sets the supervision and reporting duties and anchors the risk-management baseline you must maintain, including supply-chain security (Cbw Art. 21(3)(d); NIS2 Art. 21(2)(d)).
Sources
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