GUIDE · NIS2 SECTORS

NIS2 and logistics: how relationships with carriers and third-party warehouses change

After this guide you will be able to tell which transport activities fall within NIS2 and which logistics work is only indirectly affected. You will know which clauses to include in contracts with carriers and third-party warehouses, how to check that suppliers can handle supply chain risk, and which list of systems to start from.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Transport in Annex I, logistics not always

Transport appears in Annex I of Directive (EU) 2022/2555 in its modes: air, rail, water and road. Not all logistics is the same, however. An operator that runs transport fleets or infrastructure has a different scope from a company that organises shipments or runs a warehouse on behalf of others, and the difference must be checked item by item, reading the definitions in the applicable text.

For many logistics companies the point is not to be directly included, but to be suppliers of entities that are. A manufacturer or distributor within scope depends on its partners for deliveries and storage, and will ask them for assurances on security, access and incident notification. The practical result is the same: requests travel along the supply chain, even when your company is not classified as a direct entity.

2. Where the data lives: warehouse, transport and tracking

In logistics there are many systems, and they are often interconnected. There are warehouse management systems, transport planning systems, vehicle telematics, shipment tracking platforms and data exchanges with customers and carriers. Each connection is a possible point of access, and many are configured once and never reviewed again, even when staff or the supplier changes.

Before discussing contracts, draw a simple map: which systems support orders, which support stock levels and which support deliveries, which data flows outwards and in what format. Also note who has remote access and with which account. This map is the basis for understanding which suppliers really matter, and for distinguishing a partner that touches your data from one that merely carries the goods.

3. What changes in contracts with carriers and warehouses

A standard transport or storage contract deals with timeframes, responsibility for goods and rates. Under NIS2, the security of systems that exchange data and orders also comes into play. You do not need to rewrite everything: you need to add precise clauses, proportionate to the supplier's role and to what it can do on your systems. A separate security annex is often the cleanest way to do this without reopening the entire agreement.

The clauses must be realistic. A small warehouse does not have the same procedures as a structured operator, but it can still guarantee controlled access, backups of its own systems and a clear channel for communications. Ask the supplier to state in writing what it does today, not only what it promises to do, and attach that statement to the contract as a reference. A signed statement carries more weight than an answer given verbally.

  • Minimum security requirements for the supplier's systems and access
  • Obligation to report incidents affecting it, within timeframes compatible with the 24-hour and 72-hour deadlines
  • List of sub-suppliers that process data or access systems
  • Right to verify, including through questionnaires or documentation
  • Management of remote access, with personal accounts and rapid revocation
  • Return or deletion of data at the end of the relationship
  • Shared responsibility for service continuity

4. Supply chain risk: a generic example

Imagine a distributor that uses an order management platform connected to a third-party warehouse's systems. For the integrations, the warehouse uses a shared support account. The theft of that account's credentials blocks goods from leaving for an entire shift, and the distributor only realises when customers call. Neither party had planned who had access or how they would alert each other.

The example is deliberately generic, but it illustrates the point. Supply chain security depends on each party knowing its own access points and having an agreed way to report a problem. Without this, the consequences fall on whoever notices last, even when the problem originated with a supplier. The contract should provide for exactly this scenario, with a named contact on each side.

5. How to assess logistics suppliers

Not all suppliers require the same assessment. Focus on those that have access to your systems, process personal data or are essential to delivery. The method below is simple and repeatable, and can be applied with the same template to every new supplier, without reinventing it each time. Simply keep the completed form with the contract, so that whoever reads it later knows on what basis the choice was made.

  1. List your logistics suppliers and mark those with access to systems or data.
  2. Ask each of them for a document describing the security measures applied to its systems.
  3. Check how the supplier manages access for its employees and sub-suppliers.
  4. Ask what its timeframes are for alerting you in the event of an incident.
  5. Check that the supplier has a continuity plan and can operate in manual mode.
  6. Record the result and schedule a review when the contract, systems or volumes change.

6. Common mistakes

The first mistake is to trust a generic statement. A document saying the supplier takes security seriously does not tell you which accesses exist or who controls them. The second is forgetting decommissioned systems: credentials of former staff members or integrations never switched off remain active for years, often with nobody remembering them. A quarterly check of active accounts, compared with the staff list, catches most of these cases.

The third is not having an operational contact. If the first warning of an incident arrives at a generic mailbox, it may be a long time before anyone reads it. Define a named contact for each critical supplier and verify that the contact actually works, with a simple test every year. The fourth is treating the subject as purely legal, without involving the people who run the warehouse and transport systems.

7. How to get started

By next week, list the three logistics suppliers with the most access to your systems, and for each one check who holds active credentials and who can alert you if something goes wrong. With this list you can open a concrete conversation with suppliers and, if necessary, with your adviser. There is no need to wait for a new contract to begin: often a security annex to existing relationships is enough.

Frequently Asked Questions

Are third-party warehouses directly covered by NIS2?

It depends on the activity and the size. Storage for third parties does not appear as such among the transport categories. It may, however, fall under other categories or be involved as a supplier to an entity that is in scope. Have your adviser confirm the classification and, in the meantime, treat the warehouse as a critical supplier if it handles your data or your orders.

Do I need to change all my transport contracts?

Not necessarily. You can add a security annex or an addendum that introduces the relevant clauses, applied to suppliers with access to your systems or data. For occasional suppliers or those with no access, a simpler statement is enough. Priority goes to those that affect the continuity of deliveries.

Can a carrier ask for access to my management system?

Yes, this often happens for order or tracking integration. Before granting access, ask which user accounts are needed, with what permissions and for how long. Prefer personal accounts and access limited to the functions required. Document the grant and plan for revocation when the relationship ends.

How long do I have to notify a customer of an incident?

For entities within scope, the directive provides for an early warning within 24 hours and a more detailed notification within 72 hours of becoming aware of a significant incident. Your contracts should provide for compatible timeframes, so that your customer can meet its own deadlines. Verify your specific obligations with your adviser.

Is a warehouse management software provider an ICT supplier?

It can be, depending on the type of service. If the provider runs systems for you on an ongoing basis, its position may fall within the management of ICT services. This is not something to settle with a label: ask the provider how it classifies its service and which measures it applies, and record the answer in the contract.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →