What NIS2 requires of directors and senior management
Short answer. Article 20 obliges management bodies to approve the entity's cybersecurity risk-management measures, oversee their implementation, and follow training on cyber risk. Member states must make management liable for infringements, and for essential entities a supervisor can temporarily bar a senior manager from exercising managerial functions.
Last reviewed: 31 July 2026.
What NIS requires of management
The single biggest cultural change NIS2 introduced is that cybersecurity stopped being purely a delegated technical matter. Article 20 puts named duties on the management body — the board, or its equivalent in the entity's governance structure.
This is deliberate. The directive's recitals are explicit that member states should ensure management bodies of essential and important entities have a sufficient level of knowledge and skill to identify risks and assess cybersecurity risk-management practices.
The three duties in Article twenty
- Approve the cybersecurity risk-management measures taken to comply with Article 21.
- Oversee their implementation.
- Follow training, and offer similar training to employees on a regular basis.
Underpinning all three: management bodies can be held liable for infringements by the entity.
What approval actually means
Approval is a decision, and a decision needs a record. In practice, boards that are comfortable on this point have:
- A written set of risk-management measures mapped to the ten Article 21(2) headings — not a strategy deck, a description of what is in place.
- A dated board or committee resolution approving them, with the version approved identified.
- A standing agenda item for oversight — typically quarterly — covering measure effectiveness, incidents, and material changes.
- A named accountable executive with the authority and budget to deliver the measures.
- A re-approval trigger: material change to the risk profile, a significant incident, or an annual review at minimum.
The commonest gap is not the absence of security work but the absence of evidence that the management body approved it. Supervisors can ask for the minute.
The training obligation
Article 20(2) is short and often skipped. Two distinct requirements sit inside it:
- Members of management bodies must follow training enabling them to identify risks and evaluate cybersecurity risk-management practices and their impact on the entity's services.
- The entity must offer similar training to employees on a regular basis.
"Regular" is not defined. Annual, with role-based additions for staff in higher-risk functions, is the common interpretation. Keep attendance records — this is a question that is easy for a supervisor to ask and awkward to answer retrospectively.
Note that basic cyber hygiene and training is separately a minimum measure under Article 21(2)(g), so training appears twice in the directive: once as a governance duty and once as a control.
What liability looks like
The directive does not create a single EU-wide personal liability. It requires member states to ensure liability exists, and the shape varies:
- In several states, liability runs through existing company-law duties of care — a failure to approve or oversee becomes a breach of directors' duties.
- Some transposing laws add explicit statutory liability for named officers.
- Article 32(5)(b) adds the supervisory sanction: for essential entities, where other measures have proved ineffective, a temporary ban on a person at CEO or legal-representative level from exercising managerial functions in that entity.
Insurance and indemnity arrangements should be reviewed against the national position, because a regulatory ban is not something a D&O policy responds to.
What boards should ask for
A workable standing board pack for NIS2 covers:
- Scope — which group entities are in scope, in which member states, in which category, and when that was last reviewed.
- Measures — status against each of the ten Article 21(2) headings, with owner and evidence location.
- Incidents — significant incidents in the period, reporting timeliness against the 24/72-hour and one-month deadlines, and lessons implemented.
- Suppliers — coverage of the vendor register, assessment currency, contract remediation progress, and open high-risk findings.
- Effectiveness — results of the Article 21(2)(f) testing that assesses whether the measures work.
Supply chain questions for the board pack
Supply chain is where board oversight most often has nothing concrete to look at. Five questions that surface the truth quickly:
- How many suppliers do we have, and what proportion of them have been risk-assessed within the last 12 months?
- Which suppliers have access to our network, our data, or our production systems — and is that list derived from systems or from memory?
- What proportion of our supplier contracts contain security, incident-notification and audit clauses? What is the remediation plan for the rest?
- If a critical supplier were breached tomorrow, how would we learn about it, and how fast?
- Can we produce, today, the evidence a supervisor would ask for on any named supplier?
If the answers require a project to find out, that is itself the finding. How to build a NIS2 vendor register is where to start.