vendorapp logo

Docs

Does NIS2 require sanctions screening?


Short answer. No. NIS2 contains no sanctions screening obligation — that duty comes from EU restrictive measures regulations, which apply directly to you regardless of sector or size. Screening still belongs in a NIS2 supplier programme, because it is one of the few risk signals that does not depend on the supplier's own answers.

Last reviewed: 31 July 2026.

Does NIS require sanctions screening

It does not. Article 21(2) lists ten measures and sanctions compliance is not among them. Anyone telling you that NIS2 mandates screening is conflating two separate regimes.

The conflation is understandable, because both bear on the same question — who are you doing business with — and both are usually implemented by the same team using the same supplier list.

Where the legal obligation actually comes from

EU restrictive measures are imposed by Council regulations, which are directly applicable in every member state. They prohibit, among other things, making funds or economic resources available directly or indirectly to designated persons and entities.

Their scope is much broader than NIS2's:

  • EU nationals and EU-incorporated companies, wherever in the world they operate;
  • any person within EU territory;
  • any business done in whole or in part within the Union;
  • on board EU-flagged aircraft and vessels.

There is no sector list and no size threshold. A ten-person consultancy has the same obligation as a grid operator. Breach is a criminal matter in most member states, not an administrative one.

The practical point: if you are reading this to decide whether to screen suppliers, NIS2 is the wrong reason to reach a decision. You are almost certainly already obliged.

Why screening still belongs in the programme

Three reasons it earns its place in a NIS2 supply chain programme even though the directive does not require it.

1. It is independent evidence. Most supplier assurance is self-reported: questionnaires, policy statements, certificates the supplier chose to obtain. Screening, ownership data and adverse media come from outside the relationship. When Article 21(3) asks you to take account of a supplier's specific risk, independent inputs are worth more than assertions.

2. It surfaces the facts that drive supply chain risk. Screening properly done resolves the legal entity, its ownership and its jurisdiction. Those are exactly the non-technical risk factors Article 22 coordinated assessments consider, and they are the facts most often wrong in a supplier register built from invoices.

3. It runs continuously. Designations happen without notice. A supplier screened clean at onboarding may be designated a year later, and you will not hear about it from them. Continuous screening is one of the few controls that meaningfully covers the gap between periodic reassessments — see How often do you have to reassess suppliers?

What NIS says that points this way

Two hooks, neither of which names sanctions:

  • Article 21(3) requires taking account of the vulnerabilities specific to each direct supplier and the overall quality of their products and cybersecurity practices. Ownership and control are legitimate inputs to that judgement.
  • Article 22 provides for Union-level coordinated risk assessments of critical supply chains taking account of technical and, where relevant, non-technical risk factors. The recitals are clear that non-technical factors include undue influence by a third country over suppliers.

So NIS2 does not ask "is this supplier designated?" It asks a broader question — who ultimately controls this supplier, and from where — to which screening data supplies part of the answer.

What to screen and when

  • Who: the contracting legal entity, its parent and ultimate beneficial owners where obtainable, and for higher-risk relationships its directors and officers.
  • Against what: consolidated EU, UN and relevant national lists. Which lists apply depends on where you operate and where your customers are.
  • When: at onboarding, before contract signature, on ownership change, at reassessment, and continuously in between.
  • What to keep: the screening date, the lists covered, the result, and the disposition of any match. A screening you cannot evidence is not a control.

Name matching produces false positives — common names, transliterations, similar entities in different jurisdictions. Screening without a documented adjudication process produces either alert fatigue or unrecorded dismissals; both fail on inspection.

What a hit means

A potential match is not a designation. The process should be:

  1. Freeze the decision, not the supplier. Do not onboard, sign or pay pending review.
  2. Adjudicate. Confirm identity against additional identifiers — registration number, address, date of birth for individuals.
  3. Escalate confirmed matches immediately to legal and compliance. There are reporting obligations to national competent authorities under sanctions law that are separate from anything in NIS2.
  4. Record the outcome with the reviewer, evidence and date, whether the conclusion is a match or a dismissal.
  5. Re-screen on any change of ownership or corporate structure.

Note that this sits outside the NIS2 incident-reporting path entirely. A sanctions match is not a "significant incident" under Article 23 — it is a different regime with different authorities.

Screening in Vendorapp

Vendorapp screens vendors against consolidated global sanctions and watchlists automatically as part of pre-screening and assessment, so the check happens at intake rather than as a separate manual task, and the result is held against the vendor record with the rest of the assessment evidence.

Screening is a supporting control in a NIS2 programme, not the programme. Pair it with the assessment, contract and monitoring work in the NIS2 supply chain compliance checklist.

Frequently asked questions

Does NIS2 require sanctions screening?
No. NIS2 contains no sanctions screening obligation. The requirement to avoid dealings with designated persons comes from EU restrictive measures regulations, which apply directly and independently of NIS2 and of sector or size.
Why include sanctions screening in a NIS2 programme?
Because Article 21(3) asks you to take account of supplier-specific risk, and screening is one of the few inputs that does not depend on the supplier answering a questionnaire. It also surfaces ownership and jurisdiction facts relevant to supply chain risk.
Who has to comply with EU sanctions?
EU sanctions regulations bind EU nationals and companies wherever they are, any person within EU territory, and business done in whole or in part within the Union — regardless of sector, size or NIS2 status.