Why the supply chain is the real perimeter of NIS2
The statistics of recent years — from the SolarWinds and Kaseya compromise chains to attacks on cloud providers and MSPs — have made one fact clear: most significant incidents in large organisations do not start inside the traditional perimeter, but at a supplier. European legislators have taken note: NIS2 treats supply chain security as one of the 10 families of mandatory measures under Art. 21.
For organisations within the scope of NIS2, this means two things. First, they need to know who their critical suppliers are, what they do and what impact their compromise would have on essential processes. Second, they need to be able to demonstrate to ACN (Italy's National Cybersecurity Agency) that supplier security is the subject of a structured process, not of informal assessments.
Step 1 — Mapping critical suppliers
The first step is to identify which suppliers are "critical" for NIS2 purposes. A supplier is critical if its compromise (confidentiality, integrity or availability) could have a significant impact on the delivery of the organisation's services. Typically these include:
- Cloud service providers (IaaS, PaaS, SaaS) hosting critical data or services;
- Managed Service Providers (MSPs) and IT outsourcing providers;
- Managed Security Service Providers (MSSPs), external SOCs, EDR/XDR;
- Suppliers of business-critical software and of the related updates;
- Telecommunications and connectivity providers;
- Suppliers with privileged access to systems (remote maintenance, administrative management).
The output of this step is a register of critical suppliers, with a risk classification and a mapping of the impact on essential processes. It must be updated at least once a year and whenever a new critical supplier comes on board or the scope of an existing one changes significantly.
Step 2 — Vendor risk assessment and due diligence
A structured risk assessment must be carried out for each critical supplier. The typical tools are:
- Due diligence questionnaire on security posture (aligned with frameworks such as SIG, CAIQ, ISO/IEC 27036);
- Verification of certifications (ISO/IEC 27001, ISO/IEC 27017/27018, SOC 2 Type II, sector certifications);
- Analysis of security reports published by the supplier (transparency reports, white papers, any penetration tests made available);
- Background checks on any past incidents and how they were handled.
The outcome of the due diligence must be documented and becomes an integral part of the decision to onboard the supplier. For suppliers with a high risk score, compensating measures can be applied (network segregation, reduced privileges, enhanced monitoring) or, in the most serious cases, the supplier can be excluded.
Step 3 — NIS2-compliant contractual clauses
The contract is the main tool for governing supplier security. For critical suppliers, the contract must include — at the very least — clauses on:
- Minimum security measures to be met (referring to a recognised standard such as ISO/IEC 27001 or to the requirements of Art. 21);
- Incident notification obligations: timing (ideally within 24-48 hours), minimum content of the notification, contact channel;
- Right to audit: the organisation (or a third party it designates) may carry out security checks at the supplier;
- Transparency obligations on the second-tier supply chain (critical sub-suppliers);
- Security SLAs: patching times for critical vulnerabilities, mandatory MFA for privileged access, backup and disaster recovery with defined RPO/RTO;
- Reversibility clauses: on termination of the relationship, return and/or certified deletion of data;
- Express termination clauses in the event of serious breaches of the security measures.
Step 4 — Continuous monitoring
A supplier's compliance is not a static state: it changes as threats evolve, with internal reorganisations and as certifications are renewed. An NIS2-compliant vendor risk management programme provides for continuous monitoring, at different intervals according to risk level:
- Annual: renewal of the due diligence questionnaire, verification that certifications are valid, review of the supplier's security plan;
- Six-monthly or quarterly: for the most critical suppliers, regular security governance meetings and reviews of shared security KPIs;
- Event-driven: whenever the supplier suffers a significant incident, changes core technology or significantly changes its scope.
Step 5 — Integration with incident response and notification
When an incident involves the supply chain, two parallel procedures are triggered: internal incident management (Art. 21) and notification to ACN (Art. 25). The vendor management programme must be integrated with both, so that the flow of information from supplier to organisation and from organisation to authority is fast, complete and traced.
Contractual clauses on supplier notification (ideally within 24-48 hours) are what make it possible to meet the 24-hour early warning required by Art. 25. Without a contractual obligation on the supplier to notify promptly, the risk of "discovering the incident days late" is real — and by then the NIS2 clock is already well and truly running.
Common mistakes to avoid
- Simply asking "are you ISO 27001 certified?": certification is important, but it is no substitute for a risk analysis specific to how you use the service;
- Using the same questionnaire for every supplier: due diligence must be calibrated to the type of service and the level of risk;
- Leaving notification clauses out of the contract: without a formal obligation, the supplier may delay informing you;
- Ignoring the second-tier supply chain: your SaaS supplier may host data with a cloud provider that is the real critical supplier;
- Treating vendor management as a Procurement activity: without the involvement of the CISO and Information Security, the risk of underestimation is high.
Related resources
For the regulatory framework: NIS2: the complete guide to Legislative Decree 138/2024. For the full checklist of technical measures: NIS2: the technical measures of Art. 21 — the CISO's checklist. For technical training of your IT team on supply chain security: NIS2 Course for IT Technicians.