Skip to main content
Back to overview

NIS2 Supplier Risk Assessment: What Article 21(3) and Article 22 Actually Require

By NIS2Certify
nis2supply-chainsupplier-riskarticle-21article-22msp
NIS2 Supplier Risk Assessment: What Article 21(3) and Article 22 Actually Require

A client's IT director sends you a 94-question supplier security questionnaire and wants it back by Friday. Her company is a NIS2 entity, you are one of her suppliers, and she has a gap in her file: no evidence that she assessed you. Whether 94 generic questions amount to a NIS2 supplier risk assessment is a different matter. The directive asks for something narrower than most questionnaires, and in one respect wider.

This article covers what Article 21(3) and Article 22 actually say, what you can reasonably show an auditor, and how to run the process without a 200-row spreadsheet per client.

NIS2 supplier risk assessment starts with Article 21(3)

Article 21(2)(d) lists "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers" among the minimum risk-management measures. Article 21(3) then says how to judge whether those measures are appropriate. Entities must take into account:

  • the vulnerabilities specific to each direct supplier and service provider;
  • the overall quality of products and cybersecurity practices of those suppliers, including their secure development procedures;
  • the results of the coordinated security risk assessments of critical supply chains carried out under Article 22(1).

Read the first point again. The text says vulnerabilities specific to each direct supplier. A questionnaire sent unchanged to every vendor does not show that. A short record of why this supplier, with this access, carries this risk, does.

Article 22 is two paragraphs, and most checklists skip it

Article 22(1) says the Cooperation Group, in cooperation with the Commission and ENISA, may carry out coordinated security risk assessments of specific critical ICT services, ICT systems or ICT products supply chains, taking into account technical and, where relevant, non-technical risk factors. Article 22(2) says the Commission, after consulting the Cooperation Group and ENISA, identifies which services, systems or products may be assessed.

That is the whole article. Two points matter for your clients.

First, it is permissive. Nothing in Article 22 forces an assessment of any particular product. Do not tell a client that "the EU has assessed" their cloud or RMM vendor unless you have seen the published result.

Second, Article 21(3) pulls the outcome into every entity's own process. Once a coordinated assessment exists for something your client uses, they must take its results into account. Recitals 90 and 91 describe the logic, name non-technical factors such as undue influence by a third country on suppliers, concealed vulnerabilities or backdoors, and technological lock-in or provider dependency, and point to the 5G coordinated risk assessment under Recommendation (EU) 2019/534 as the precedent.

I could not verify a dated list of completed Article 22 assessments this week. Check the NIS Cooperation Group and ENISA publications before you cite one to a client.

What an auditor can reasonably ask for

The directive does not publish an evidence list for suppliers. The following is practical reading of Article 21(2)(d) and 21(3), not legal text:

  • a supplier inventory that identifies which suppliers touch the entity's network and information systems;
  • a record of how each supplier was rated, and why;
  • the supplier-specific vulnerabilities or quality concerns you considered;
  • contract terms that carry security requirements. Recital 85 encourages entities to build cybersecurity risk-management measures into contracts with direct suppliers and service providers;
  • evidence that findings were followed up.

Our guide on supervisory audit evidence shows how auditors tend to sequence these requests, and your supplier contracts covers the clause side in more detail.

Article 21 — 10 NIS2 Cybersecurity Measures

Article 21

10 Cybersecurity Measures

Governance & Strategy

1Risk analysis & information security policies
6Effectiveness assessment of security measures

Incident & Continuity

2Incident handling & notification
3Business continuity & disaster recovery

Supply Chain & Systems

4Supply chain security
5Security in network & information systems development

Technical Controls

8Cryptography & encryption
10Multi-factor authentication & secure communications

People & Assets

7Cyber hygiene & training
9HR security & access control

Tier suppliers before you question them

The fastest way to fail Article 21(3) is to treat the payroll tool and the identity provider alike. Use three tiers.

Tier 1: suppliers whose failure stops the service, or who hold privileged access. Think identity provider, backup platform, remote monitoring and management tool, core cloud tenant. Collect evidence, not answers: a current certificate and its scope, a recent penetration test summary, the incident notification terms in the contract. For an MSP, the RMM vendor is Tier 1 for every client you manage, so assess it once and reuse the result.

Tier 2: suppliers who process the entity's data or connect to its systems without being critical. A short questionnaire of 15 to 20 questions, matched to what the supplier actually touches.

Tier 3: everyone else. A standard security clause in the contract and a line in the inventory. Nothing more.

A mid-sized logistics client might have 120 suppliers. Roughly eight land in Tier 1, thirty in Tier 2. That is a workable review, where 120 identical questionnaires are not.

Write down the reasoning, not only the result

Article 21(3) uses the words "take into account". An auditor cannot test what you thought. They can read what you recorded. For each Tier 1 supplier, keep one page: what the supplier does for the entity, what access it holds, what you reviewed, what concern you found, and what you decided. If a supplier refuses to share evidence, record that and the compensating control you chose.

Also record the date. Supplier posture changes, and a review from 2024 will not satisfy an auditor in 2027.

National law adds specifics, and the picture is uneven

NIS2 is a directive, so the binding wording sits in national law. The detail differs:

  • Germany: the BSI cites § 30(2) sentence 2 no. 4 BSIG for supply chain security and, in its guidance, says entities should oblige suppliers to meet appropriate security requirements. BSI also points to Implementing Regulation (EU) 2024/2690 for supply-chain concepts.
  • Netherlands: the Cyberbeveiligingswet (Cbw) is administered with registration through the NCSC's MijnNCSC portal. I could not verify the article that carries the supplier duty.
  • France: ANSSI describes the NIS 2 framework as part of the "projet de loi Résilience" and published a draft Référentiel Cyber France (ReCyF) on 17 March 2026, which is not mandatory by default.
  • Spain, Italy, Poland: I could not verify article-level supplier provisions this week. Where a national text is unclear or still pending, the directive itself is the benchmark.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity · Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) · Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) · Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) · Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS · Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government · Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department · Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE · Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KüTS) amendment
    • Registration within 3 months

    Authority: RIA · Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI · Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security · Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV · Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority · Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) · Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH · Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC · Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority · Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB · Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) · Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN · Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre · Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) · Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI · Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE · Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland · Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

What to do on Monday

  1. Export the client's supplier list from accounts payable, not from IT. Shadow SaaS shows up in the payments.
  2. Tier it. Aim for under ten Tier 1 suppliers.
  3. For each Tier 1 supplier, write the one-page record.
  4. Add one standard security clause to every new and renewing contract.
  5. Diary a yearly re-tiering.

A NIS2Certify readiness assessment shows where a client's supplier management sits against Article 21 before an auditor does. Run a quick scan on your next client and bring the supplier findings to the conversation. For the wider list of measures, see the ten Article 21 measures and the older overview of NIS2 supply chain security.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.