Skip to main content
Back to overview

NIS2 Waste Management and Postal Services: Who Is In Scope

By NIS2Certify
nis2waste-managementpostal-servicescourierannex-iiscopemsp
NIS2 Waste Management and Postal Services: Who Is In Scope

A regional waste collector with 90 employees runs its fleet routing, weighbridge and invoicing on three connected systems. A courier depot next door depends on one parcel-sorting platform and a cloud tracking portal. Neither owner has ever filed a cybersecurity report. Both now sit in a sector the EU calls "critical", and both get asked about it by customers.

This is the NIS2 waste management and postal question. Both sectors are listed in Annex II of Directive (EU) 2022/2555, the "other critical sectors". The wording is narrower than most clients fear, and wider than most clients hope.

What Annex II actually covers

Item 1 of Annex II is postal and courier services: "postal service providers as defined in Article 2, point (1a), of Directive 97/67/EC, including providers of courier services". Courier firms are named explicitly. Parcel networks, last-mile couriers and traditional postal operators all fall into the same entry.

Item 3 is waste management: undertakings carrying out waste management as defined in Article 3, point (9), of Directive 2008/98/EC. Under that definition, waste management means the collection, transport, recovery and disposal of waste. A collector, a transporter, a sorting plant and a landfill operator can all qualify.

The carve-out that decides most waste cases

The waste entry excludes "undertakings for whom waste management is not their principal economic activity". That is the single most useful sentence for your client conversations.

A manufacturer that handles its own production scrap is not in scope for that reason. A scrap-metal trader whose main business is collecting and processing waste may be. Ask one question: is waste management the main thing this company earns its money from? Document the answer, and the evidence behind it.

The postal entry has no equivalent carve-out. If a company provides postal or courier services as a business, test it against the size rule.

The size rule: medium and above

NIS2 applies to medium-sized and large entities in the listed sectors. In practice that means at least 50 staff or more than €10 million in annual turnover or balance sheet. Micro and small firms are generally outside the baseline, although Member States can add exceptions for specific situations.

Annex II entities are classed as important entities, not essential ones. That affects supervision. Authorities can act after an incident or a complaint, rather than running routine inspections. It does not reduce the obligations.

What an important entity must do

The duties are the same as for every in-scope organisation. Article 21 requires appropriate and proportionate risk-management measures across ten areas: risk analysis policies, incident handling, business continuity, supply chain security, secure acquisition and maintenance, assessing effectiveness, cyber hygiene and training, cryptography, access control and asset management, and multi-factor authentication or secured communications. See our guide to the ten Article 21 measures.

Management bodies must approve those measures and answer for them. They also need training. For a family-owned haulier or a regional postal operator, this is often the first time a director has been formally accountable for IT risk.

Where these sectors are exposed

Operational technology in waste handling is easy to overlook. Weighbridges, compactor controls, landfill gas monitoring and fleet telematics are all networked. A ransomware event that stops weighbridge invoicing stops collection revenue the same day.

In postal and courier operations, the pressure point is the sorting and tracking platform. Many couriers run on a single SaaS provider. If that provider fails, so does the depot. That is a supply chain question under Article 21(2)(d), and it is the first thing a customer questionnaire will probe.

Both sectors also depend on subcontractors: owner-driver couriers, haulage partners, third-party route-planning tools. A written inventory of those suppliers, with security terms in the contract, is cheap and rarely exists. Our post on NIS2 supply chain security shows how to build it.

Incident reporting works the same way

A significant incident triggers an early warning within 24 hours, an incident notification within 72 hours, and a final report within one month under Article 23. Clients usually have no process for the first hour, never mind the first day. The reporting deadlines are where a short tabletop exercise pays off.

NIS2 Incident Reporting Timeline

24h

Early Warning

Notify the competent authority (CSIRT/NCA) within 24 hours of becoming aware of a significant incident.

72h

Incident Notification

Submit a detailed notification within 72 hours with an initial assessment of severity, impact and indicators of compromise.

1mo

Final Report

Deliver a comprehensive final report within one month covering root cause, remediation taken and cross-border impact.

Penalties for important entities

Article 34 sets maximum administrative fines for important entities of at least €7 million or at least 1.4% of total worldwide annual turnover, whichever is higher. These are ceilings set by the Directive. National law sets the final figures. We cover the full picture in NIS2 fines.

Transposition differs by country

The Directive is the same everywhere, but the obligations your client faces depend on the national law and regulator. Some Member States have transposed NIS2 and are registering entities. Others are still behind, and the Commission has referred several to the Court of Justice. Check the live position before you advise a cross-border client. The EU implementation timeline is a good starting point.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity Β· Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) Β· Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) Β· Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) Β· Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS Β· Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government Β· Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department Β· Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE Β· Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KΓΌTS) amendment
    • Registration within 3 months

    Authority: RIA Β· Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI Β· Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security Β· Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV Β· Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority Β· Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) Β· Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH Β· Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC Β· Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority Β· Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB Β· Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) Β· Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN Β· Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre Β· Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) Β· Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI Β· Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE Β· Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland Β· Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

A practical order of work for these clients

Start with scope. Write a one-page memo that states the sector entry, the principal-activity test for waste, the size figures and the conclusion. Regulators and customers both ask for exactly this.

Then run a gap analysis against the ten measures, and prioritise supplier inventory, incident contacts and backup testing. Most waste and postal clients are weakest on those three. If you want a fast baseline, the NIS2Certify quick scan gives you a readiness assessment you can walk through with the client in one meeting.

Finally, put the incident clock on paper: who decides what is significant, who calls the authority, and who writes the 72-hour notification. A tested one-page plan beats a 40-page policy nobody has read.

Scope depends on the entity, the country and the facts. Your job is to make the decision defensible. If the chemical sector taught consultants anything, it is that Annex II scope questions are won on documentation, not assumption. For a general first check, see does NIS2 apply to my organisation.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.