Define the assessment boundary
Identify the legal supplier, contracted service, relevant product and systems affected. Describe the service owner's dependence on the supplier and whether its staff or technology can access sensitive data, privileged credentials or production environments.
A cloud service used only for an internal newsletter should not automatically receive the same priority as a managed provider controlling essential infrastructure. However, shared authentication or network dependencies may change that conclusion.
Rank criticality using operational consequences
Consider service interruption, confidentiality and integrity exposure, degree of privileged access, recovery alternatives and how quickly the entity could switch providers. Record when several suppliers rely on a common subprovider.
Use a consistent rating method, but allow assessors to explain exceptional cases. A single composite score without the underlying reason makes later review and remediation harder.
Gather targeted security evidence
Request information tied to the risk: secure development and vulnerability disclosure, administrative authentication, incident handling, business continuity, data protection, subcontractor oversight and security assurance. Validate document dates and the actual scope of assurance.
Where a supplier cannot provide sensitive technical details, alternative evidence may still permit a proportionate decision. Record limitations rather than presenting unverified claims as confirmed safeguards.
Evaluate specific vulnerabilities and mitigations
Article 21(3) directs attention to the vulnerabilities specific to each direct supplier or service provider and the quality of its products and cybersecurity practices. Identify what could actually fail and whether the organisation can limit the resulting exposure.
Possible actions include restricting privileged access, testing restoration paths, requiring incident escalation, seeking software support commitments or developing a transition plan. Match the measure to the failure scenario.
Make the decision and follow up
Record whether the risk is accepted, reduced, transferred through suitable arrangements or avoided. Assign owners and review dates. Reassess critical relationships after security incidents, changes in supplier ownership, new subproviders or material changes to the supplied service.
Review findings with procurement and service owners so a commercial renewal does not bypass unresolved security requirements. A supplier assessment is useful only when its conclusions influence decisions.
Retain an auditable assessment record
Keep the supplier inventory, business dependency, evidence examined, identified gaps, mitigation status, decision authority and assessment date together. Distinguish planned checks from completed verification.
Check relevant national law and sector rules. The detailed requirements in Regulation (EU) 2024/2690 apply only to its specified categories; ENISA guidance on that regulation can inform assessments but is not universally binding.
Questions on the text
How often should NIS2 supplier risk assessments be repeated?
Article 21 does not set one universal assessment interval. Set risk-based review triggers and check any applicable national or provider-specific requirements.
Can a supplier questionnaire be enough?
A questionnaire may help gather information, but its claims should be judged against the relationship's risks and supported by appropriate evidence where feasible.