What NIS2 requires for supply chain security
Article 21(2)(d) expressly includes supply chain security and security-related aspects of relationships with direct suppliers and service providers. Article 21(3) addresses consideration of supplier-specific vulnerabilities, the overall quality of products and suppliers' cybersecurity practices, including secure development. These duties form part of the broader requirement for appropriate and proportionate measures.
The text does not establish a single standard questionnaire, certification or contractual clause that every supplier must use. National transposition matters, and Commission Implementing Regulation (EU) 2024/2690 adds more detailed requirements for specified digital and ICT providers.
Map suppliers to critical services
Begin with the covered entity's services and systems. Identify providers with access to production environments, sensitive operational data or components whose failure could interrupt delivery. Include hosting, identity, managed security, software updates, connectivity and key equipment where relevant.
Record the service owner and what would stop working if a supplier became unavailable or compromised. A low-spend vendor with administrative access may present more immediate risk than an expensive supplier with no access to critical systems.
Assess security practices and concentration risk
Use evidence appropriate to the relationship: incident response and notification arrangements, access security, vulnerability handling, secure development where relevant, subcontractor dependencies and continuity capabilities. Examine the scope and currency of certifications or assurance reports rather than treating a logo as sufficient.
Consider whether several apparently independent services rely on the same infrastructure provider. Geographic concentration, exclusive proprietary interfaces and difficult migrations can affect the impact of supplier disruption.
Use procurement and contracts to manage identified risks
Specify meaningful security expectations before onboarding a supplier, then reflect agreed responsibilities in appropriate contract clauses and operating procedures. These may cover access privileges, vulnerability communications, incident escalation, subcontractor changes, data return and termination.
Contract wording alone cannot establish the operational capability of a provider. Check that the organisation can receive useful alerts, revoke access and exercise recovery alternatives when necessary.
Monitor and respond during the relationship
Set review intervals based on criticality and material change rather than reviewing all suppliers mechanically. Reassess after incidents, major acquisitions, changes in service scope or new external dependencies. Give findings an owner and record accepted residual risks.
An effective process links supplier risk to business continuity and internal incident handling. Where a supplier incident affects a covered service, assess the entity's own NIS2 reporting obligations separately from any contractual supplier notification.
Keep evidence and distinguish applicable rules
Useful records include a dependency inventory, criticality criteria, assessments, contracts, remediation tracking, review decisions and offboarding evidence. The specific documentary burden follows the risk and applicable jurisdiction.
ENISA's 2025 technical implementation guidance addresses providers covered by Regulation 2024/2690. Its examples can be informative beyond those providers, but should not be presented as additional binding rules for all NIS2 entities.
Questions on the text
Does NIS2 require organisations to assess every supplier identically?
No. Measures must be appropriate and proportionate, with attention to the particular risks, vulnerabilities and role of each supplier.
Does outsourcing transfer NIS2 responsibility to the supplier?
An entity should not assume that contracting out a service removes its own applicable NIS2 duties. The precise legal position depends on scope, the national law and the obligations of each party.