The short answer
NIS2 (EU Directive 2022/2555) widened EU cybersecurity rules to many more companies, including transport, postal and courier operators. Medium and large entities in these sectors that operate in the EU must register, manage cyber risk across their supply chain, report significant incidents within 24 hours, and make their management body accountable. North American logistics firms are affected through their EU entities and through supplier clauses from EU customers.
Who is in scope
| Sector under NIS2 | Examples | Category |
|---|---|---|
| Transport: air | Airlines, airports, air traffic control | Highly critical (Annex I) |
| Transport: rail | Infrastructure managers, railway undertakings | Highly critical |
| Transport: water | Shipping companies, ports, vessel traffic services | Highly critical |
| Transport: road | Road authorities, intelligent transport system operators | Highly critical |
| Postal and courier | Parcel and courier services | Other critical (Annex II) |
Size rule: generally medium (50+ staff or over €10 million turnover and balance sheet) and large organizations. Each EU country transposes NIS2 into national law and may add detail, so registration and reporting run through national authorities. Several countries finished transposing late, so check the law in each country where you operate.
The core duties
- Risk management measures covering risk analysis, incident handling, business continuity and backups, supply-chain security, secure development, vulnerability handling, cryptography, access control, MFA and staff training.
- Incident reporting: an early warning within 24 hours, a notification within 72 hours and a final report within one month.
- Management accountability: the management body approves and oversees measures and must take cybersecurity training.
- Registration with the national authority.
A 90-day NIS2 plan for logistics
Days 1–30: confirm scope and gaps
- Map your EU entities, sectors and sizes; confirm which national laws apply.
- Register where required.
- Run a gap assessment against NIS2 measures, reusing ISO 27001 or SOC 2 work where you have it.
Days 31–60: fix the urgent items
- Set up a 24-hour incident triage and reporting runbook.
- Make sure 24/7 monitoring covers TMS, WMS, port and fleet systems.
- Review your top suppliers: TMS vendors, telematics, EDI and cloud providers.
- Test backups and recovery for systems that keep freight moving.
Days 61–90: govern and prove
- Brief and train the management body; get formal approval of the measures.
- Run a tabletop exercise on a ransomware attack that stops warehouse operations.
- Plan the year's audits, testing and supplier reviews.
How Zuroth helps
- NIS2 gap assessments mapped to ISO 27001, with national-law differences flagged.
- 24/7 SOC as a Service and incident response support to meet the 24-hour early warning.
- Backup and disaster recovery for TMS, WMS and EDI systems.
- Supplier security reviews and contract clauses.
Next step: book a free consultation to confirm your NIS2 scope.
Related reading
- Logistics & Supply Chain
- AI for shipping documents
- ISO 27001 certification
- SOC as a Service
- Backup & disaster recovery
This article explains general practice and is not legal advice. Confirm your obligations under each national law with your counsel.
Frequently asked questions
Which logistics companies are in scope for NIS2?
NIS2 covers air, rail, water and road transport operators, including some port and traffic management entities, as highly critical sectors, and postal and courier services as other critical sectors. Generally, medium and large organizations, with 50 or more staff or more than €10 million in turnover, operating in the EU are in scope.
Does NIS2 apply to US or Canadian logistics companies?
It applies to their EU operations if those entities fall in a covered sector and meet the size rules, and national laws may require an EU representative. North American companies also feel NIS2 through supply-chain clauses from EU customers and partners that must manage their suppliers' cyber risk.
What are NIS2's incident reporting deadlines?
For significant incidents, entities must send an early warning to their national CSIRT or authority within 24 hours of becoming aware, an incident notification within 72 hours and a final report within one month. Some national laws add detail to these steps.
What are the fines under NIS2?
Member states must allow fines of up to €10 million or 2% of worldwide annual turnover for essential entities, and up to €7 million or 1.4% for important entities, whichever is higher. Management bodies can also be held responsible for failing to oversee cybersecurity measures.
Does ISO 27001 cover NIS2?
ISO 27001 covers most of NIS2's risk management measures, such as risk analysis, incident handling, business continuity, supplier security, access control and cryptography. You still need NIS2-specific items: national registration, the reporting timelines, management training and approval, and any national requirements.