NIS2 guide · 7 min
Do your suppliers use AI? NIS2 supplier risk meets the EU AI Act
Under NIS2 you are accountable for the cyber risk your suppliers carry (Article 21(2)(d)). Increasingly that risk includes AI: suppliers embedding AI in the services you depend on, and their suppliers doing the same. The EU AI Act, now in phased enforcement, adds obligations for organisations that deploy or rely on AI systems, including ones provided by third parties. Most supplier assessments still do not ask about AI at all. This guide explains where supplier and nth-party AI creates risk under NIS2 and the AI Act, what to assess, and how to keep visibility as it spreads.
Key takeaways
- • NIS2 makes supplier cyber risk your responsibility; AI embedded by suppliers is now part of that risk.
- • The EU AI Act adds obligations when you rely on third-party AI, including high-risk systems.
- • Most questionnaires ignore AI; nth-party AI (your vendors' vendors) is the hardest blind spot.
Where AI enters your supply chain
AI reaches you through suppliers in three ways: a vendor uses AI inside a service you consume; a vendor processes your data with AI (training, inference, support tools); and your vendor's own vendors do the same (nth-party). Each adds attack surface (model and data exposure, prompt injection, new integrations) and regulatory exposure. NIS2 Article 21(2)(d) makes you responsible for the security of these relationships, and the EU AI Act adds transparency and risk-management duties when you deploy or rely on AI systems, including third-party ones.
Official sources: NIS2 Directive on EUR-Lex — Article 21(2)(d); plus the EU AI Act (Regulation (EU) 2024/1689) for AI-specific obligations.
What to assess about supplier AI
Add these to supplier assessment. They map to NIS2's supply-chain measures and to the AI Act's duties on those who rely on AI systems.
Where AI touches your data
Ask which parts of the service use AI, whether your data is used for training or inference, and where that processing happens. This determines both your NIS2 exposure and your AI Act and GDPR position.
Whether the AI is high-risk under the AI Act
If a supplier's AI falls in an AI Act high-risk category, you inherit transparency, human-oversight and record-keeping expectations when you rely on it. Confirm the classification and the supplier's conformity work.
Nth-party AI (your vendor's vendors)
Suppliers increasingly resell or embed third-party AI (foundation models, AI APIs). Require disclosure of these sub-providers, so a model outage, data incident or policy change does not blindside you.
AI-specific security controls
Prompt-injection and data-leakage protection, access control on model endpoints, logging, and human oversight of automated decisions. These are the AI-era extension of the Article 21(2) baseline.
AI incident notification
Extend your contract's incident-notification clause to AI-specific failures (data leakage through a model, harmful or manipulated output), so a supplier's AI incident reaches you in time for your own reporting.
See how your suppliers actually score
7-day free trial · no credit card · cancel anytime
How to keep visibility as AI spreads
AI adoption in your supply chain changes faster than an annual questionnaire: a supplier adds an AI feature, switches model provider, or a new sub-processor appears. Pair the questionnaire with continuous external monitoring and a live fourth-party inventory, so new AI dependencies and the sub-providers behind them surface as they appear, mapped to the NIS2 and AI Act obligations they trigger, instead of at the next review cycle.
Common mistakes
- ✕A supplier questionnaire that never asks about AI at all.
- ✕Assessing the direct supplier but ignoring the third-party model or AI API behind their service.
- ✕Treating AI purely as an innovation topic, not as supply-chain security and AI Act compliance.
- ✕No contractual duty to disclose AI use or to notify AI-specific incidents.
See how supplier and AI risk maps to NIS2
A sample supplier report (findings, NIS2 mapping and evidence) in two minutes.
7-day free trial · no credit card · cancel anytime
Related guides
How to comply with NIS2: a step-by-step roadmap
The steps to NIS2 compliance in order: confirm scope, register, management accountability (Art. 20), the Article 21(2) measures, supply-chain security, incident reporting (Art. 23) and continuous, evidenced assurance.
Who is in scope for NIS2? Essential vs important entities, sectors and size thresholds
Determine whether NIS2 applies to you: the two tiers, the Annex I/II sectors, the size thresholds, size-independent exceptions, and how the supply chain pulls you in even if you're not designated.
NIS2 for suppliers: you're not designated, but your customers are
Most companies are never designated under NIS2, yet many must comply anyway. How a covered customer's Article 21(2)(d) supply-chain duty flows down to you, what they'll ask for, and how to respond credibly.
NIS2 and the supply chain requirement: what it means in practice
NIS2 requires essential and important entities to assess their supply chain cyber risks. Supplier tiering, 4th-party risk, Art. 23 notification, and what auditors look for.
Supplier cyber risk assessment: what automated NIS2 monitoring checks
All check categories explained: ransomware, dark web leaks, TLS/DNSSEC, cookie security, CVE/EPSS, sanctions, MX blacklists and SAQ. Finding lifecycle and NIS2 article mapping.
NIS2 Art. 21(2): supplier security checklist
Checklist for procurement and security teams: what to ask, what evidence to collect, and how to respond when a supplier falls short. Includes suggested evidence documents.
NIS2 supplier questionnaire (SAQ): what to ask, how to score it, and a free template
What to ask suppliers under Art. 21(2)(d), how to score answers and respond to gaps, why self-attestation needs verification, and a free copy-paste questionnaire template.
NIS2 incident reporting: the 24- and 72-hour deadlines explained
What counts as a significant incident, the Article 23 timeline (24-hour early warning, 72-hour notification, one-month final report), and when a supplier's incident becomes your obligation.
NIS2 and management responsibility: what boards and leadership must know
What NIS2 expects of the management body: approval and oversight duties, personal liability (Art. 20), training, board reporting KPIs, and the penalties under Art. 34.
ISO 27001 and NIS2: what your ISMS already covers, and the gaps it doesn't
If you hold ISO 27001, what carries over to NIS2 and what does not: statutory incident reporting, management liability, registration, and continuous supply-chain assurance: plus how to close the gap.
NIS2 fines and penalties: how much, who is liable, and how to avoid them
What NIS2 penalties are: the Article 34 caps (€10M / 2% for essential, €7M / 1.4% for important entities), the management body's personal liability (Art. 20, Art. 32), non-monetary enforcement, and how to avoid them with continuous, evidenced diligence.
NIS2 vs DORA: how they differ, where they overlap, and which one applies to you
How the two EU regimes differ and overlap, why DORA is lex specialis for financial entities, which applies to you, and what both mean for third-party and supply-chain risk.
GDPR vs NIS2: how they overlap, where they differ, and when one incident triggers both
How GDPR and NIS2 differ and overlap, when one incident triggers both (GDPR Art. 33 72h to the DPA vs NIS2 Art. 23 24h/72h/1-month to the CSIRT), the Art. 35 cooperation and no-double-fine rule, and what both mean for supplier due diligence.
The EU Cyber Resilience Act (CRA): scope, timeline and what it means for your supply chain
What the CRA requires, its phased dates (in force 2024, reporting Sept 2026, full compliance Dec 2027), who is in scope and why pure SaaS often isn't, how it complements NIS2, and what it means for procurement and supplier due diligence.
The EU AI Act: risk tiers, the timeline, and what deployers must do (Article 26)
What the EU AI Act requires: the risk tiers, the phased dates (in force 2024, prohibited Feb 2025, GPAI Aug 2025, high-risk Aug 2026), the Article 26 deployer obligations, how it stacks with NIS2 and the GDPR, and what it means for AI procurement.
NIS2 transposition status: which EU countries have it in force
Which of the 27 EU Member States have written NIS2 into national law and which are still finalising it, and why the gaps reach your supply chain regardless.
NIS2 supplier contract clauses: what to require from your suppliers
The contract clauses that turn NIS2's supply-chain duty into something enforceable: security baseline, incident-notification window, evidence and audit rights, subcontractor flow-down, and how to verify them continuously.
Your external security posture under NIS2: what suppliers and customers can see
The publicly visible signals customers assess under NIS2 Art. 21(2)(d): email spoofability (SPF/DMARC), certificate hygiene, internet-exposed systems and leaked credentials, why each matters and how to check and fix them.
Vendor impersonation and CEO-fraud (BEC): email spoofing, DMARC and NIS2
One of the most common supply-chain attacks needs no breach: spoofed email that redirects a payment or steals data. How BEC and vendor impersonation work, the SPF, DKIM and DMARC settings that stop them, and how it fits NIS2 Art. 21(2)(d).
Last reviewed: 19 June 2026
This guide is general information about EU law, not legal advice. NIS2 takes effect through each EU Member State's national transposition law, which can differ in detail. Verify the obligations that apply to you with your competent authority or legal counsel.