1. Why the supplier chain has become a compliance issue
The NIS2 Directive (EU) 2022/2555 requires organisations within its scope to manage the security of networks and information systems, including the risk that comes from suppliers. A company may have strong defences on its own premises and still be compromised by a software or support supplier with poorly protected access. For this reason, supply chain security is no longer a matter to be left to the goodwill of the procurement department.
In cross-border supply chains the problem multiplies. A supplier may be in one country and the customer in another, with data travelling between sites that use different national rules. The transposition of NIS2 is not identical across Member States: in Italy it took place through D.Lgs. 138/2024, while France, Germany and Spain are following their own routes. Always check the rules of the country in which you operate, not only those of the supplier's country.
2. Working out whether your business is in scope
The first step is to establish whether your organisation falls within the scope of the directive, and in which category. This depends on the sector of activity, the size and the services provided. It is not something to settle with a quick reading: it is best done with a legal adviser or whoever manages compliance, and the conclusion reached should be documented.
Even companies that are not directly in scope can be affected, because their customers subject to NIS2 request contractual guarantees from their suppliers. In practice the scope extends along the supply chain. If you receive security questionnaires from large customers, treat them as a signal: they are already applying the rules to their own chain. Answering in an orderly way is also a commercial advantage, because it shows that your organisation is reliable.
3. Requirements to pass on to suppliers
A supply chain audit is not a one-off check but a process that links requirements, contracts and evidence. The table summarises the most recurring requirements and how to turn them into concrete requests to suppliers. There are no universal thresholds: the level of detail depends on the criticality of each supplier and the data it handles. Start with the suppliers that have access to your systems and to your most sensitive data.
Evidence counts for more than declarations. A supplier that says it has access controls must be able to show the list of privileged accounts, its credential rotation policy and the logs. Certifications such as ISO/IEC 27001, or the TISAX framework, which is widespread in the automotive supply chain, are useful elements but do not replace verification of the perimeter that concerns you. Always ask exactly what the certification covers and when it was last verified.
| Requirement | What to ask the supplier | How to verify it |
|---|---|---|
| Risk management | Up-to-date risk analysis of the services provided | Review of the document and comparison with the actual scope |
| Access control | List of privileged accounts and multi-factor authentication | Extract of logs and testing on a sample of access events |
| Incident management | Detection and communication procedure with defined timescales | Simulated incident with a written response |
| Business continuity | Recovery plan and tests carried out in the last year | Test report with results and corrective actions |
| Supply chain security | List of sub-suppliers and obligations passed on to them | Signed declaration and contract clauses |
4. Managing incident notification along the supply chain
Incidents do not stop at the supplier's boundary. If an attack hits a partner's system, your organisation may have to react within the timescales set by the regulation. NIS2 provides for an early warning within 24 hours of becoming aware of a significant incident, followed by a notification within 72 hours. The contract with the supplier must allow you to meet these timescales, so it must provide for rapid and complete communication.
In practice many contracts say only that the supplier will 'inform promptly'. That is a vague formula. It is better to define who calls whom, through which channels, which information is needed in the first hours and who approves external communications. Also ask for the plan to be tested with a simulation at least once a year. The result should be written down and shared with the security manager, along with the corrective actions required.
5. Clauses and checklist for the audit
Contract clauses are the tool that makes the audit binding. They do not need to be long, but they do need clear, measurable and verifiable obligations. It is advisable to include the right to request evidence, notification of sub-suppliers and cooperation during inspections. Each item in the list below should have a named owner and a review date. The same list is also useful for responding quickly to requests from large customers.
For the first review there is no need to complete everything at once. Start with the suppliers that have access to your systems or personal data, then extend the analysis to the others. Document every response received, including negative ones, because they form the basis for deciding subsequent actions. A missing answer is data like any other and should be recorded with the date of the follow-up.
- Inventory of suppliers with access to systems, networks or sensitive data.
- Incident notification clause with timescales compatible with NIS2.
- Right to request evidence of controls and access logs.
- Obligation to disclose sub-suppliers and to pass the same rules on to them.
- Continuity plan with documented tests and the date of the last exercise.
- Procedure for returning or deleting data at the end of the contract.
- Internal owner for each supplier, with at least an annual review.
6. Common mistakes in supply chain reviews
The first mistake is collecting questionnaires without ever verifying them. A 'yes' ticked on a form proves nothing if nobody asks for the log, the test or the contract that supports it. The second is treating all suppliers in the same way. A stationery supplier and a supplier that runs your invoicing system do not require the same level of control.
The third mistake is forgetting sub-suppliers. The supplier that answers you may rely on another entity for hosting or support, and that entity has not been assessed. Always ask for the map of the chain. The fourth is confusing certification with compliance: a certification covers a perimeter, and it must be read carefully. A valid certificate does not rule out a single service remaining outside the perimeter.
7. How to start: the first concrete step
The first step is to build a list of suppliers with the type of access they have: systems, networks, personal data, customer data or essential services. Next to each, note the contact person and the contract that governs it. In many businesses this list does not exist, and creating it brings to light forgotten suppliers and access that has been active for years.
Then choose the three most critical suppliers and send them the requirements table as a formal request, with a response deadline and a request for evidence. With the results in hand you can decide which clauses to update at the next contract renewal and which controls to run first. Keep track of responses and deadlines in a single shared document with management.
Frequently Asked Questions
Does NIS2 also apply to suppliers of smaller companies?
It depends on the role they play. The directive applies to entities within its scope, but customers subject to NIS2 can request contractual guarantees even from their smaller suppliers. In practice the obligation arrives through contracts. Check with your adviser which requirements your customer actually requires.
Is a supplier's ISO/IEC 27001 certification enough?
It helps, but it is not enough on its own. What matters is the scope of the certification: which sites, which services and which processes are covered. Ask for the certificate with its scope statement and check that it includes the service you use. Then assess the aspects that are not covered, such as sub-suppliers and incident management.
What is the difference between an early warning and a notification?
The early warning is a rapid first communication, designed to flag that a significant incident is suspected or in progress. The subsequent notification contains a fuller picture of the incident, with the information available at that point. The contract with the supplier must provide for both communications, with agreed timescales and content.
How do I manage suppliers operating in different countries?
Start from the map of suppliers and the countries in which they operate, then check which national rules apply to your organisation. The transposition of NIS2 varies from one Member State to another, so a requirement may be worded differently. Draft the clauses so that they work in all the countries involved, and get local legal advice for complex cases.
How often should supplier audits be repeated?
There is no universal interval. For critical suppliers an annual review at least is advisable, plus a check whenever their services, sub-suppliers or corporate structure change. For suppliers with limited access, a lighter documentary review may suffice, provided it is recorded and signed by the internal owner.