NIS2 Management Body Training: What Article 20 Requires of Directors

A managing director signs off a £40,000 security budget in a two-minute call. Nobody records what she was shown, what she asked, or what she decided. Six months later a regulator asks one question: who approved your risk-management measures, and what did that person know?
That question comes straight from Article 20 of the NIS2 Directive. It is the shortest article in the governance chapter and the one MSPs most often leave out of a client's readiness plan.
What Article 20 of NIS2 actually says
Article 20(1) of Directive (EU) 2022/2555 requires Member States to ensure that the management bodies of essential and important entities approve the cybersecurity risk-management measures taken to comply with Article 21, oversee their implementation, and can be held liable for infringements of that Article. It is without prejudice to national liability rules for public institutions and officials.
Article 20(2) adds the training duty. Members of management bodies must be required to follow training, so they have enough knowledge and skills to identify risks and assess cybersecurity risk-management practices and their impact on the entity's services. Entities are also encouraged to offer similar training to employees on a regular basis.
Three verbs carry the article: approve, oversee, learn. Delegation to an IT manager or an MSP does not remove any of them.
Article 21 — 10 NIS2 Cybersecurity Measures
Article 21
10 Cybersecurity Measures
Governance & Strategy
Incident & Continuity
Supply Chain & Systems
Technical Controls
People & Assets
Who counts as the management body
The Directive does not define a single role. It speaks of "management bodies", and each Member State maps that onto its own company law: a board of directors, a Geschäftsleitung, a bestuur, a kierownik podmiotu. For your client the practical test is simple. Whoever has the legal authority to commit the organisation to spending and risk decisions is in scope.
That is why a CISO, however senior, is not enough. The CISO prepares and reports. The management body decides.
What "approve" means in an audit
The Directive does not prescribe a form. In practice an auditor looks for evidence that approval happened, was informed, and was recorded. A minute that says "security update noted" will not carry that weight.
Evidence that holds up:
- A dated decision record that names the risk-management measures approved, linked to the Article 21(2) areas.
- The risk assessment or summary the decision was based on.
- A budget line or resourcing decision that matches the measures.
- A review date, because approval at one point in time does not cover a changing environment.
Italy's regulator has been explicit about the level of this duty. Its published guidance, as reported in July 2026, treats approval as covering the overall framework rather than every technical control, and oversight as continuous rather than a one-off sign-off. That is a sensible reading anywhere: the board approves the framework and the risk appetite, not the firewall rules.
What "oversee" means between approvals
Oversight is the part that gets neglected. A board that approved a policy in January and never saw a metric afterwards has approved, but not overseen.
Give the client a short, recurring management report: open high risks, incident count and response times, patch and backup status, supplier issues, training completion. One page, reviewed quarterly, minuted. That single habit answers most of what a supervisor wants to see about Article 20(1).
Training: the obligation with a certificate attached
Article 20(2) sets no fixed frequency, and no training length. National laws fill that gap, and the detail differs enough to matter.
The Netherlands is the most concrete example. Its Cyberbeveiligingswet requires executive bestuurders of essential and important entities to follow training and receive a certificate stating the topics covered. The certificate may be in Dutch or English. The law gives them until two years after entry into force to have the required knowledge. Supervisory board members who are not executive directors are outside that training duty.
Germany's § 38(3) BSIG requires management to take part in training "regularly" so it can judge risks and their effect on the entity's services. The statute sets no interval. Poland's amended KSC Act, in force since 3 April 2026, requires annual documented training for the head of the entity.
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.
If you serve clients in several countries, do not promise one training standard. Offer one core programme and map it to each national rule.
What the training must cover
The Directive gives the outcome, not a syllabus. Build on that wording: identifying risks, assessing risk-management practices, and understanding their impact on services. A workable half-day programme for directors:
- The entity's risk picture: assets, dependencies, realistic incident scenarios.
- The Article 21 measures and what "approved" commits the board to.
- Incident reporting: what triggers the 24-hour early warning and who decides. See our guide to the significant incident threshold.
- Supplier risk and what the board must ask of vendors.
- Personal exposure: what liability means under the national law.
Keep it practical. Italy's guidance stresses that training must be substantive, not a formal briefing. A slide deck read aloud will not satisfy that.
Liability: what is and is not established
Article 20(1) says management bodies can be held liable. It does not create a uniform personal fine. Each country decides how liability works.
Germany routes it through company law: management that culpably breaches its duties answers to the entity for damage. Poland adds personal administrative fines for the head of the entity in its own act, although the main sanctions under the act can only be imposed after 3 April 2028. Spain has no transposing law yet, and France's transposition bill is still moving through parliament, so for those two the directive text is the only fixed reference today.
Stay calm in client conversations. Liability is real, but it is not automatic, and a documented process is the best protection. For the wider picture see NIS2 and personal board liability.
What MSPs should do this quarter
Treat Article 20 as a service line, not a footnote:
- Add a governance section to every readiness assessment: who approves, how it is recorded, when it is reviewed.
- Offer a director briefing and keep a signed training log per client.
- Provide the quarterly one-page management report as a managed deliverable.
- Check the national rule for each client's country before quoting a training frequency.
Clients who can show an approval record, a reporting rhythm and a training log have answered the three questions Article 20 asks. To see where a client stands on governance and the ten Article 21 measures, run a free readiness scan.
The management body does not need to become technical. It needs to decide knowingly, and be able to prove it.
NIS2 Penalty Escalation — Beyond the Fine
Trigger event
Non-Compliance Detected or Incident Occurs
A supervisory authority identifies a compliance gap or an organisation fails to meet NIS2 requirements
Compliance orders with binding deadlines
Mandatory security audits at your expense
Public disclosure of violations
Binding instructions on specific security measures
Suspension of certifications or operating licences
Temporary ban on management functions for individuals
Public naming of responsible natural persons
Still have a question?
Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.
