An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesContinuous Supplier Monitoring Under NIS2
Supply Chain Security / 2026-10-10

Continuous Supplier Monitoring Under NIS2

Continuous supplier monitoring means maintaining visibility of material cybersecurity risks throughout a supplier relationship rather than treating onboarding as the final assessment. Article 21(2)(d) and Article 21(3) of NIS2 place supply chain security and supplier-specific vulnerabilities within a covered entity's risk management duties. The intensity of monitoring should reflect the particular service and its risk.

Use criticality to determine monitoring depth

Start with a current inventory of direct suppliers and service providers, identifying the services they support, their access to systems and relevant dependencies. Critical providers may warrant closer observation than relationships with little operational security exposure.

Record why each supplier receives a particular monitoring level. A financial contract value is not a substitute for analysis of privileged access, service interruption or data integrity consequences.

Identify meaningful change signals

Review material events such as breaches, security advisories, end-of-support notices, subcontractor changes, ownership changes, expired assurance reports and persistent remediation delays. Combine supplier communications with appropriate independent sources when feasible.

Do not treat automated risk scores as definitive. A change may be relevant only to specific supplied products or environments, so confirm exposure before escalating or closing a finding.

Establish accountable review and escalation

Give each critical relationship a business owner and a security review contact. Define who evaluates changes, requests evidence, approves exceptions and escalates a threat to incident response or business continuity teams.

Agree with the supplier on incident communication and remediation cooperation. A supplier notification does not remove the covered entity's duty to assess any applicable Article 23 reporting requirement.

Connect monitoring to measurable corrective action

Track findings with severity rationale, scope, owner, agreed actions and due dates. Verify closure through updated evidence or technical checks where proportionate. Persistent weaknesses should inform contract renewal and future procurement decisions.

A calendar review without consequences is weak assurance. Reassess the exposure when the supplier changes technology, service delivery or critical subcontractors.

Keep records proportionate and review the legal basis

Useful records include assessment dates, evidence reviewed, material events, remediation outcomes and decisions to continue or change the relationship. Revisit the monitoring model after an incident or a major shift in business dependencies.

Member State transposition determines applicable legal duties, while Regulation (EU) 2024/2690 specifies additional requirements for certain digital and ICT providers. No single continuous scanning frequency is mandated for every NIS2 entity.

Questions on the text

Does NIS2 mandate daily monitoring of all suppliers?

No universal daily-monitoring frequency is stated in Article 21 for every supplier relationship. Monitoring should address risk and additional applicable requirements.

Is an annual questionnaire enough?

Not automatically. Material changes and incidents may require assessment between scheduled reviews, particularly for critical relationships.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.