NIS2 (in Poland: the amended Cybersecurity Act, in force from 3 April 2026) imposes Article 21 obligations on essential and important entities, including supply-chain security. AI vendor choice and where data is processed fall directly under these requirements, and management is personally accountable for negligence.
This cluster maps NIS2 onto concrete AI decisions, not generalities. We show how Article 21(2) translates into technical controls and the artifacts you must show an auditor; why a public cloud LLM is a problem under Article 21(1)(d) (supply chain, sub-processors, processing location); and what personal board accountability means after the Cybersecurity Act amendment. This is the one bridge siloed competitors don't build: lawyers write about obligations without architecture, vendors about deployments without the law. We connect the two, always linking “how to meet this on-prem”. Deadlines shift (self-identification, the Digital Omnibus package), we date and update our content. Start with the Article 21 mapping cheat sheet, then measure readiness with the checklist.
By 3 October 2026, key and important entities must enter Poland's KSC register under the amended NIS2 law. The law runs on self-identification: you assess whether you are in scope and file the application yourself. How to do it, and what to tick off before the deadline.
NIS2 does not prescribe a topology, but it does require isolation. A minimum three-zone model for on-prem AI, and how each network boundary maps to Article 21. A practical layout you can defend to an auditor.
The amended Polish cybersecurity act shifts responsibility for cybersecurity oversight onto the management board personally. What that means for choosing an AI vendor and architecture, and the decision trail you need to be able to show. A mapping of duties, not legal advice.
Pillar. How to map an AI vendor onto NIS2 Article 21 (Polish transposition, 2026): supply chain, sub-processors, audit rights, management liability. A working guide for the CISO of an essential entity, with a risk-register skeleton and an audit-readiness checklist.
A technical note: one NIS2 article, one scenario. Does a ChatGPT Enterprise or Claude contract meet Article 21(1)(d)? Three areas where a standard public-cloud LLM relationship starts to drift from supply-chain compliance.
It doesn't ban it, but it requires supply-chain risk management, you must document data location, sub-processors, and contractual clauses. For the most sensitive data, on-prem is often the simplest answer.
After the amendment, responsibility sits with management, the board must knowingly approve and oversee decisions (including the AI vendor).
With an Article 21 map → controls → artifacts (we have a ready checklist) and a register of the AI systems in use (shadow AI).
Want to apply this to your case: architecture, compliance, and cost?
→ Book 30 min