Define the relevant service dependency
Map the services covered by NIS2 to ICT systems, external providers, licences and communications paths needed to operate them. Include shared identity, hosting and security monitoring platforms where applicable.
A supplier's criticality depends on the consequences of an outage or compromise. Even an inexpensive vendor can be critical when it controls privileged access or an essential integration.
Evaluate impact of losing the supplier
Analyse how long the supported service could operate without the supplier, which data could be exposed or corrupted and which critical activities would stop. Consider the availability of alternatives and the time required to switch.
Review confidentiality, integrity and availability separately. A software update provider may create an integrity risk even when its service does not require continuous connectivity.
Identify shared and hidden dependencies
Direct suppliers may rely on cloud infrastructure, subcontractors or specialist support. Where those dependencies are known and material, record how their failure could affect several ostensibly independent services.
Concentration risk can be missed when teams procure tools separately. Assess the consequences of a shared provider's failure across the portfolio.
Rank and document supplier criticality
Record service owners, systems accessed, administrative privileges, data handled, impact rating and rationale. Use consistent criteria while documenting exceptions where actual risk differs from the standard rating.
Review the classification after major supplier changes, migrations or incidents. Supplier criticality helps prioritise risk reviews and assurance activities; it is not a label of supplier security quality.
Connect classification to NIS2 obligations
Article 21(2)(d) addresses security-related aspects of direct supplier and service-provider relationships. Article 21(3) refers to supplier-specific vulnerabilities and the quality of products and security practices.
Check applicable Member State law and additional rules for specific digital and ICT providers. The Directive does not prescribe a universal list of critical suppliers for every entity.
Questions on the text
Does NIS2 impose the same supplier security method on every entity?
No. The Directive requires proportionate measures and attention to the specific supplier relationships and risks, alongside applicable national requirements.
Should this assessment be revisited?
Yes. Material service changes, incidents and new dependencies can affect the adequacy of existing controls.