vendorapp logo

Docs

How often do you have to reassess suppliers under NIS2?


Short answer. NIS2 sets no interval. Article 21 requires measures that are and remain appropriate, so the defensible pattern is risk-tiered periodic review — annual for critical suppliers, 12–24 months for significant, renewal-triggered for low risk — combined with event-driven reassessment and continuous monitoring in between.

Last reviewed: 31 July 2026.

How often to reassess suppliers

This is the most frequently asked NIS2 supply chain question and the one with no clean answer in the text. What the directive does provide is a standard: your measures must be appropriate to the risk. A supplier assessment that no longer describes the supplier is not an appropriate measure.

Commission Implementing Regulation (EU) 2024/2690, for the digital entities it covers, requires supplier arrangements to be monitored and reviewed at planned intervals. "Planned" is the operative word — the interval is yours to set, but it must be set, written down, and followed.

Why there is no fixed interval

A single mandated frequency would be simultaneously too much for a stationery supplier and too little for the identity provider guarding every login. The proportionality standard in Article 21(1) does the work instead: exposure, size, likelihood and severity of incidents.

The corollary is that you must be able to explain your cadence. "Annual for everyone" is a policy; "annual for tier 1, biennial for tier 2, renewal-based for tier 3, because tier is derived from access, data sensitivity and substitutability" is a defensible policy.

A defensible cadence

TierPeriodic reviewContinuous signalsTypical triggers
CriticalEvery 12 monthsSanctions, ownership, adverse media, breach and stability signals, monitored continuouslyAny event in the list below
SignificantEvery 12–24 monthsSanctions and adverse-media screening at least quarterlyIncident, ownership change, service change, renewal
LowAt contract renewal, or every 36 monthsSanctions screening at onboarding and renewalIncident, escalation into a higher tier

Two calibration notes. First, if a critical supplier's assessment is more than 12 months old at the moment a supervisor asks, expect a finding. Second, tiering is not permanent — a "low risk" marketing tool that gets an API integration into your CRM has just changed tier, and the trigger for noticing that is a change process, not the calendar.

Event driven triggers

Periodic review catches drift. Triggers catch the things that actually cause incidents:

  • A security incident at the supplier, disclosed or publicly reported.
  • Change of ownership or control, including private equity acquisition or a change in ultimate beneficial owner. This can change jurisdiction and risk appetite overnight.
  • A sanctions or watchlist hit on the entity, its parent, or its officers.
  • Change of subcontractors, sub-processors or hosting location.
  • Material change to the service — new architecture, new integration, new data categories, new access.
  • Change in your dependency — the supplier now supports an in-scope service they did not support before.
  • Financial distress signals — filings, late accounts, adverse credit movement, insolvency proceedings.
  • A relevant Article 22 coordinated risk assessment at Union level touching their technology.
  • Contract renewal, which is the natural moment to reprice risk as well as commercials.
  • Failure to meet a contractual security obligation, including missed notification windows.

Write these into the policy. A trigger list that exists only in someone's head is not a control.

Continuous monitoring between reviews

The gap between periodic reviews is where NIS2 programmes actually fail. Three signal types are worth automating because they change without warning and do not depend on supplier cooperation:

  1. Sanctions and watchlists. Designations happen overnight and carry immediate legal consequences beyond NIS2. See Does NIS2 require sanctions screening?
  2. Corporate and ownership changes. Acquisitions, restructurings and changes of ultimate parent.
  3. Financial stability. A supplier heading for insolvency is a continuity risk long before it is a security one.

Breach and adverse-media monitoring sits alongside these. In Vendorapp, screening and risk ratings refresh as part of the assessment lifecycle rather than as a manual annual exercise — see Vendorapp Intelligence and managing alerts and notifications.

What a reassessment should actually do

A reassessment that re-sends the original questionnaire and files the response has added nothing. A useful one:

  • Confirms the dependency is still what you think it is — same services, same data, same access. This is usually where the surprises are.
  • Closes or re-ages open findings from last time, with evidence.
  • Re-verifies expiring evidence — certifications lapse, audit reports go stale, scope statements change.
  • Checks the contract still matches reality, including notification windows and subcontractor lists.
  • Re-runs independent signals rather than relying on the supplier's account of itself.
  • Restates the risk decision with a date and an owner.

Making the cadence hold

The cadence fails for mundane reasons: nobody owns the supplier, the due date lives in a spreadsheet, the reviewer left. Countermeasures:

  • Assign a named internal owner per supplier, and treat ownership transfer as part of leaver handling.
  • Drive due dates from the record, with automated reminders ahead of expiry, not a quarterly manual sweep.
  • Track coverage as a metric — percentage of critical suppliers with a current assessment — and report it to the management body under Article 20 oversight.
  • Make overdue a visible state, not an invisible one.

Coverage trending in the right direction, with a documented cadence and honest overdue reporting, is a far stronger supervisory position than a claim of full compliance nobody can substantiate.