Begin with the actual relationship
Identify the contracted service, connected systems, sensitive information, privileged access and operational dependencies. A corporate security statement may say little about the specific product being supplied.
Use the assessment to determine which controls deserve examination. A software developer and a managed network operator present different types of exposure.
Check the scope of assurance evidence
Evaluate independent audit reports, certifications, documented controls and material remediation findings where appropriate. Note dates, exclusions and whether the examined environment matches the service being purchased.
A certificate does not necessarily cover every service or facility. Where detailed evidence cannot be supplied, record limitations and consider suitable alternative assurance.
Review vulnerability and development practices
Ask how security defects are reported, triaged, corrected and communicated; assess supported software versions and the integrity of update delivery. For software vendors, secure development practices are relevant under Article 21(3).
Distinguish published promises from observed remediation and update history. Avoid treating a single questionnaire answer as proof of operational effectiveness.
Assess incident handling and resilience
Understand who receives incident notifications, how compromised access can be disabled and how the supplier restores dependent services. Consider material subcontractors and concentration risks.
A contractual supplier notification is different from the entity's own decision about significant-incident reporting under Article 23.
Decide and monitor proportionately
Document findings, evidence gaps, mitigation owners and residual risk decisions. Reassess after incidents, material service changes or significant control failures.
Regulation (EU) 2024/2690 provides more detailed requirements for specified provider categories; do not present those provisions as universal obligations for all NIS2 entities.
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.