1. Why the supply chain is in scope
An organisation can have very well protected systems and still suffer an incident through a supplier. Management software with uncontrolled access, remote assistance that is always on, or a poorly configured cloud infrastructure are common entry points. NIS2 treats supply chain security as part of risk management, because the attack surface does not coincide with the boundaries of the organisation.
The contract is the tool that makes this responsibility concrete. A supplier with no written obligations on security, incident notification or cooperation during an audit is a blind spot, even if it is a reliable partner. For this reason the matter should be addressed before signing, and again at every renewal. The supplier, for its part, should know which requirements will be asked of it and what evidence it will have to produce.
2. What the rules require, in practice
The rules require you to consider the security of direct supplier relationships and of service providers, taking into account the specific vulnerabilities and the overall quality of suppliers' products and security practices. In practice this means knowing which suppliers are relevant, assessing them against written criteria, including requirements in contracts and checking that they are respected over time.
There is no model set of clauses imposed by the rules that you can copy without adapting it. The clauses must reflect the real risks of the relationship. Your legal adviser should verify their consistency with the national framework and with other obligations already in place, such as those on the processing of personal data. Use as a basis the security areas your sector considers critical, and adapt them to the service you are buying.
3. Clauses to include in contracts
The clauses below are a general starting point. They should be adapted to the type of service, to the criticality of the supplier and to the volume of data or systems it can access. A generic clause stating that the supplier complies with the law protects no one: you need a verifiable obligation. Choose the clauses that matter most for the service in question, without weighing every contract down with ten pages of requirements.
- Minimum security requirements described in a technical annex, updatable over time.
- Obligation to report incidents affecting your data or systems within timeframes compatible with your notification obligations.
- Right to obtain security evidence, such as test reports, certifications or completed questionnaires, and to request clarification.
- Conditions for the use of subcontractors, with prior approval or at least notification and the right to object.
- Management of the supplier's access to your systems, with access limited, logged and revoked at the end of the work.
- Continuity and exit: return or deletion of data at the end of the relationship and support in moving to another supplier.
- Cooperation in the event of an authority inspection or incident, with defined response times.
4. Assessing the supplier before signing
The assessment is not intended to exclude every supplier, but to understand what risk it brings and what must be protected in the contract. The table below proposes some questions and the evidence one can expect. If the supplier cannot answer, that is useful information: it means the risk must be managed with greater care or with stronger clauses. Use the table as a guide to the questions to ask in a meeting with the supplier present.
| Aspect | Question to ask | Evidence required |
|---|---|---|
| Security management | How is the supplier's internal security organised? | Policy document and designated lead |
| Incidents | How and how quickly does it notify customers of an incident? | Written procedure with communication templates |
| Access | Who can access our systems and how is that controlled? | Description of access and activity log |
| Subcontracting | Which third parties take part in the service and with what access? | List of subcontractors with role and contract |
| Continuity | What happens to the service if the supplier has a serious problem? | Continuity plan and test carried out |
5. The subcontractor risk
Many incidents pass through a supplier's subcontractor, which the organisation has never seen. A support provider may use one partner for infrastructure, another for maintenance and a third for night-time support. Each of these parties has access or data. The contract must know who they are, and the supplier must answer for them as it does for itself.
Ask for a list of subcontractors with their role, the type of access and the location of data, including the question of who may legally access it. This is not purely a geographical issue: the useful question is where the data is held and who can access it, including as a result of laws in other countries. These points should be clarified in writing. If a subcontractor has direct access to your data, ask to receive a copy of its security commitment.
6. Managing over time: review and monitoring
A signed contract is not enough. Conditions change, suppliers acquire other suppliers, and services expand. Managing suppliers is a periodic process, which should be planned like the other activities in this series. Use the sequence below as a routine, adapting it to the criticality of each relationship. Whoever keeps the register must have the time and the authority to ask for updates, otherwise the register loses its value within a few months.
- Maintain a register of relevant suppliers, with the service, data involved, internal owner and date of the last assessment.
- Check the security clauses at renewal and whenever the service changes.
- Request updated evidence, such as reports, questionnaires or attestations, on a defined schedule.
- Record and assess every incident reported by the supplier, with the response given and the actions required.
- Update the list of subcontractors when the supplier notifies changes.
- Prepare an exit plan for critical suppliers, with the information needed to change service.
7. When to involve legal counsel
Your legal adviser should review the contracts of critical suppliers, especially where they introduce security obligations, liability for incidents, transfers of data outside the European Union or limitations of liability that reduce your protections. A contract with technically correct clauses that are legally weak does not give the protection you expect. If the lawyer is not familiar with the subject, also provide a brief description of the services and the data involved.
The lawyer should also check consistency between the security clauses and those on the processing of personal data, because the supplier contract may need to contain specific provisions on that front. Give the lawyer the list of critical suppliers, the current clauses and the list of requests you want to include. Ask for the opinion to be in writing, because it will be the reference in case of dispute.
8. How to get started
The first action this week is to list the suppliers that have access to your systems or data, with one line for each and the internal owner of the relationship. This is an hour's work with administration and the IT manager, and it shows which contracts should be reviewed first. Involve administration, because contracts often have an expiry date that nobody has in mind.
Then choose the most critical supplier and compare its contract with the clauses in section three. Note the gaps and bring them to your legal adviser. This first exercise produces a template you can apply to other suppliers without starting from scratch. It also helps you estimate the time needed to review the other contracts, so that planning becomes realistic.
Frequently Asked Questions
Do I need to renegotiate all existing contracts?
Not necessarily. Focus on critical suppliers: those with access to the most sensitive systems or data, or that run services essential to your business. For the others, a lighter review is enough. Changes can be introduced at renewal, through a security annex, without reopening the whole contract if that is not necessary.
Can a large supplier refuse specific clauses?
It can happen, particularly with providers of standard services. In such cases, it is better to ask for equivalent evidence, such as security reports, written commitments on procedures and incident notification, rather than bespoke clauses. If the refusal concerns essential requirements, the choice of supplier should be reconsidered and the decision documented.
Must the supplier notify me of every incident?
It must notify incidents affecting your data or systems, within the timeframes agreed in the contract. The timeframe must be compatible with your notification obligations, which can be very tight. Also specify the minimum content of the notification, so that the information is useful from the first message.
Do I need a supplier certification?
A security management system certification, such as ISO/IEC 27001, can be a useful piece of evidence, but it does not replace contractual clauses or verification of the specific service you receive. Ask what scope the certification covers, because it may not include the very service you are buying.
What changes if the supplier is in another country?
The main change concerns who can legally access the data, which is distinct from where the data is stored. Ask the supplier to explain in writing where the data is held, which laws might apply and what guarantees it offers. Your legal adviser should assess the framework, because the answers depend on the specific case.