NIS2 Article 21(2)(d) supply chain security, explained
Short answer. Article 21(2)(d) requires every in-scope entity to implement "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers". Article 21(3) then requires you to take account of each supplier's specific vulnerabilities, the quality of their products and cybersecurity practices, and their secure development procedures.
Last reviewed: 31 July 2026.
What the supply chain measure says
The operative text of Article 21(2)(d) is one line:
supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers
That is the whole obligation as drafted. Everything else — assessments, questionnaires, contract clauses, monitoring — is what it takes to deliver it defensibly.
Reading it clause by clause
"supply chain security" — the object is your supply chain as a whole, not individual purchases. It sits alongside nine other minimum measures, so it inherits the Article 21(1) standard: appropriate, proportionate, all-hazards, state of the art, sized to your exposure.
"including security-related aspects concerning the relationships" — the focus is the relationship, not just the product. How the supplier connects to you, what access they hold, how you exchange data, how you are told when something goes wrong. This is why a security questionnaire alone is insufficient: it describes the supplier, not the relationship.
"between each entity and its" — each. This is per-relationship, not portfolio-level. A generic supply chain policy with no per-supplier record does not satisfy the text.
"direct suppliers or service providers" — the perimeter is your first tier, and it covers services as well as goods. Cloud platforms, MSPs, contractors, consultancies, maintenance providers, logistics and facilities all count where relevant to security. See Who counts as a direct supplier under NIS2?
The extra duties in paragraph three
Article 21(3) is where the assessment obligation actually lives. Entities shall take into account:
- the vulnerabilities specific to each direct supplier and service provider — supplier-specific, not sector-generic;
- the overall quality of the products and cybersecurity practices of their suppliers and service providers, including their secure development procedures — an explicit nod to software supply chain risk;
- the results of the coordinated security risk assessments of critical supply chains carried out under Article 22.
"Take into account" is a demonstrable act. In practice it means the supplier-specific information exists, someone reviewed it, and the outcome influenced a decision — accept, remediate, condition, or exit.
Coordinated risk assessments of critical supply chains
Article 22 creates a Union-level layer: the Cooperation Group, with the Commission and ENISA, may carry out coordinated security risk assessments of specific critical ICT services, systems or products supply chains, taking account of technical and, where relevant, non-technical risk factors.
Two things follow for an individual entity:
- Where such an assessment exists for a technology you depend on, ignoring it is not defensible — Article 21(3) tells you to take its results into account.
- Non-technical factors are explicitly in play. Ownership, jurisdiction, and undue influence by a third country are legitimate inputs to a supplier decision, not merely commercial preferences.
What the implementing regulation adds
Commission Implementing Regulation (EU) 2024/2690, adopted on 17 October 2024, sets technical and methodological requirements for the Article 21(2) measures for a specified set of digital entities — DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online marketplaces, online search engines and social networking platforms, and trust service providers.
Its supply chain section expects, in substance:
- a supply chain security policy governing relationships with direct suppliers and service providers;
- criteria for selecting and contracting suppliers, factoring in cybersecurity practices, secure development, and the ability to meet the entity's security requirements;
- security requirements written into contracts, including incident notification, personnel security, access control, and handling at termination;
- a directory of direct suppliers and service providers, kept current;
- monitoring and review of supplier performance against the requirements at planned intervals;
- factoring the results of Article 22 coordinated risk assessments into supplier decisions.
If you are not one of the listed entity types, this is not binding on you. It is still the most concrete official statement of what "supply chain security" means under NIS2, and it is a sensible design target.
Turning the article into controls
A minimal control set that maps cleanly to the text:
How supervisors test it
From supervisory practice in early-transposing member states, the questions tend to be concrete rather than conceptual:
- Show me your supplier register. How is it kept current, and reconciled against what?
- Pick a supplier — show me the assessment, its date, and what you did with the result.
- Which suppliers can reach your production environment? How was that list produced?
- Show me a contract for a critical supplier. Where are the security and notification obligations?
- What happened the last time a supplier had an incident? When did you learn, and from whom?
- What in your programme changed as a result of anything you found in the last 12 months?
The last question is the one that separates a live programme from a documented one. Continue to What supply chain evidence do regulators expect?
Frequently asked questions
- What does NIS2 Article 21(2)(d) say?
- It lists as a minimum cybersecurity risk-management measure "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers".
- What does Article 21(3) add?
- It requires entities to take into account the vulnerabilities specific to each direct supplier and service provider, the overall quality of their products and cybersecurity practices including secure development procedures, and the results of coordinated security risk assessments of critical supply chains under Article 22.
- Does Article 21(2)(d) apply to important entities too?
- Yes. The ten minimum measures in Article 21(2) apply identically to essential and important entities. Only supervision intensity and maximum penalties differ between the two categories.
- Is there official guidance on implementing Article 21(2)(d)?
- Commission Implementing Regulation (EU) 2024/2690 sets detailed technical requirements for specified digital entities, including a supply chain security policy, supplier selection criteria, security requirements in contracts, and review at planned intervals. Many organisations use it as a template even where it does not bind them.