Skip to main content
OkayLoop
Buying & Implementation

NIS2 Management Body Training: What Boards Should Expect

NIS2 requires management body members to follow cybersecurity training. Here is what that training should cover, how to evidence it, and how to extend it to staff.

Sweeping orange and blue ribbons rising in layers, suggesting oversight from the top of an organization
By

Marcus Reed is a fictional OkayLoop editorial persona representing the recurring perspective of executives and software buyers. Articles are reviewed by the OkayLoop editorial team.

The EU’s NIS2 Directive moved cybersecurity from the IT agenda to the boardroom. Under Article 20, the management bodies of essential and important entities must approve cybersecurity risk-management measures, oversee their implementation, and can be held liable for failures. The same article requires members of those management bodies to follow cybersecurity training.

For many executives, that last requirement is the most personal part of NIS2. It is also the one most often handled as a one-off briefing. A better approach treats director training as part of how the board governs cyber risk, not as a certificate on file.

This article is practical guidance, not legal advice. NIS2 is a directive, so the binding obligations sit in each member state’s national law. Check the Directive text on EUR-Lex and the national rules that apply to you.

Where things stand

Member states had until 17 October 2024 to transpose NIS2. Progress has been uneven, and the European Commission tracks it on its NIS2 transposition page. Some national laws add specifics on training format, frequency, or documentation; others mirror the Directive closely.

On 20 January 2026, the Commission also proposed targeted amendments to NIS2 aimed at legal clarity and lighter compliance for smaller companies. Until any amendment is adopted and transposed, plan against current national law.

What the Directive actually asks for

Three provisions shape training expectations:

ProvisionWhat it requiresWho it touches
Article 20(1)Management bodies approve risk-management measures, oversee implementation, and can be held liableBoard and executive leadership
Article 20(2)Management body members must follow training; entities are encouraged to offer similar training to employees regularlyDirectors first, then staff
Article 21(2)(g)Basic cyber hygiene practices and cybersecurity training are part of required risk-management measuresThe whole organization

The purpose of Article 20(2) training is specific: management body members should gain enough knowledge and skills to identify risks and assess cybersecurity risk-management practices and their impact on the entity’s services. That is a governance capability, not technical expertise.

1. Confirm scope before designing anything

Ask legal and security to answer four questions in writing:

  • Is the organization an essential entity, an important entity, or out of scope?
  • In which member states is it established or providing services?
  • Which national laws apply, and what do they add on training?
  • Who counts as a member of the management body under those laws?

The last question matters more than it seems. Depending on the corporate structure, it can include executive committees, supervisory boards, or managing directors of local subsidiaries.

2. Define what directors must be able to do

Write outcomes as governance decisions, not topics.

  • Approve: judge whether proposed risk-management measures are proportionate to the entity’s risks and services.
  • Challenge: ask useful questions about security reports, metrics, and exceptions.
  • Escalate: understand NIS2 incident reporting stages—an early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours, and a final report within one month—and the board’s role in them.
  • Oversee suppliers: understand supply-chain risk and what assurance the entity relies on.
  • Fund: connect budget decisions to risk reduction and residual risk the board is accepting.

These outcomes give a training provider a concrete brief and give the board a way to judge whether the training worked.

3. Design training for how boards work

Directors have little time and high context. Long technical courses waste both.

FormatBest forExample
Short briefingShared baseline on NIS2 duties and liability30-minute session with counsel and the CISO
Scenario exerciseIncident escalation and decision-makingTabletop on a ransomware event affecting a core service
Focused micro-lessonsRetaining specific concepts between meetingsReporting timelines, supplier assurance, risk acceptance
Annual refreshChanges in law, threats, and the entity’s risk profileUpdate tied to the yearly risk assessment

Tabletop exercises deserve a regular place. They show directors what an incident feels like in practice and expose unclear escalation paths before a real event does.

4. Keep evidence a supervisor can follow

A competent authority may ask how management body members were trained and how the board exercised oversight. Keep a record that connects the two:

  • the legal basis and scope determination;
  • which members were trained, when, and on which version of the materials;
  • what the training covered, mapped to the outcomes above;
  • comprehension or exercise results, and follow-up actions;
  • board minutes showing approval and oversight of risk-management measures; and
  • the refresh schedule and triggers.

Attendance alone is thin evidence. The approach in how to prove employees understood a policy applies to directors as much as staff.

5. Extend training to the organization

Article 21(2)(g) makes cyber hygiene and training part of the entity’s risk-management measures, and Article 20(2) encourages regular training for employees. Directors who approve those measures should know what employees are actually taught and how well it works.

6. Ask providers the right questions

If you are buying board or staff training, ask:

  1. Is the content mapped to NIS2 and to the national laws that apply to us?
  2. Can scenarios reflect our sector, services, and incident procedures?
  3. How is content reviewed and updated when laws or guidance change?
  4. What evidence do we receive, and can we export it?
  5. How do director and staff programs connect?

The enterprise compliance training platform evaluation checklist offers a fuller framework for the staff-facing side.

A board-ready checklist

Before the next board meeting, the chair or company secretary should be able to confirm:

  • scope and applicable national laws are documented;
  • every management body member has completed training appropriate to their role;
  • at least one incident scenario has been exercised at board level;
  • the board has approved current risk-management measures and receives regular reporting;
  • staff training is role-based and its results are reported upward; and
  • refresh dates and triggers are set.

For leadership teams modernizing how they govern policy and security learning, see how founders and executives use OkayLoop, or book a demo to walk through a board and staff training plan.

Reviewed by OkayLoop Editorial.

Bring one policy and one training goal.

See how the policy-to-learning workflow fits your audience, review process, and program requirements.

Book a Demo