NIS2 and management liability: what your board doesn’t know
NIS2 management liability is what surprises boards most: cybersecurity stops being an IT matter and becomes a legal duty of the management body. That is why management must approve the measures, oversee them and follow training. In addition, its members can answer personally if they fail to do so.
In 30 seconds: NIS2 management liability starts with Article 20, which requires management to approve the Article 21 measures, oversee their implementation and follow training. Article 32(6) allows Member States to hold the people who run the entity liable, and Article 33(5) extends this to important entities. In essential entities, Article 32(5) even allows a temporary ban on the chief executive or legal representative. Finally, in Spain the transposition law is still pending.
What Article 20 requires: approve, oversee and train
Article 20 of Directive (EU) 2022/2555 is short, but it reshapes who does what. It covers the management bodies of essential and important entities and gives them three duties:
- Approve the cybersecurity risk-management measures the entity takes to comply with Article 21.
- Oversee their implementation, rather than signing them off once.
- Train to identify risks and assess risk-management practices and their impact on the services.
Moreover, the same article provides that the management body can answer for the entity’s breaches of Article 21. The directive also asks entities to offer similar training to their staff on a regular basis. As a result, cybersecurity moves up to the board and stays there.
So, before anything else, confirm whether your company is in scope: we explain how to tell if NIS2 applies to you.
NIS2 management liability, article by article
Article 20 sets the duties, but the consequences sit in Articles 32 and 33, which cover supervision and enforcement. They deserve a careful read, because people often quote them wrongly.
Liability of natural persons (Article 32(6))
First, Member States must ensure that whoever represents an essential entity, takes decisions for it or controls it has the power to ensure its compliance. In turn, it must be possible to hold that person liable for breaching this duty. In other words, NIS2 management liability goes beyond a fine that the company pays. However, the exact form (civil, administrative or other) will depend on each country’s law.
Temporary ban in essential entities (Article 32(5))
This is the toughest measure, and therefore it has clear limits. First, it only comes into play when earlier measures, such as warnings, binding instructions or orders to remedy, have failed. Then the authority sets a deadline to fix the problem. Finally, if the entity misses it, the authority can ask the competent bodies or courts to bar the person acting as chief executive or legal representative from managerial functions. Also, the ban lasts only until the entity remedies the deficiencies, and it requires procedural safeguards.
What changes for important entities (Article 33)
On the other hand, supervision of important entities happens after the event, when there are signs of non-compliance. However, Article 33(5) applies Article 32(6) here too, so personal liability exists all the same. By contrast, the temporary ban on managers does not apply to them.
| Measure | Essential entities | Important entities |
|---|---|---|
| Approve, oversee and train (Art. 20) | Yes | Yes |
| Liability of the people who run the entity (Art. 32(6)) | Yes | Yes, via Art. 33(5) |
| Temporary ban from managerial functions (Art. 32(5)(b)) | Yes, as a last resort | No |
| Maximum fine on the entity (Art. 34) | A maximum of at least EUR 10m or 2% of worldwide turnover (the higher) | A maximum of at least EUR 7m or 1.4% of worldwide turnover (the higher) |
NIS2 management liability: what the board should do
The board shows it takes NIS2 management liability seriously through its paperwork. You can delegate technical execution but not governance; so, after an incident, the authority will look at what the board approved, oversaw and knew. These seven steps leave a trail for each duty:
- Approve in a board meeting the policy and the Article 21 measures, with the resolution in the minutes.
- Request regular reports with a few business-language indicators: top risks, incidents, plan progress and critical suppliers.
- Train through a programme for directors and keep the attendance record.
- Appoint a security lead with authority and enough budget.
- Oversee the supply chain, because many incidents come in through a supplier.
- Rehearse a major incident with the board present, including the 24-hour, 72-hour and one-month reporting deadlines.
- Review everything at least once a year, or sooner if the business or the threat changes.
Finally, if you need a timetable, our 90-day NIS2 implementation plan spreads these steps across phases.
The situation in Spain (October 2026)
Spain has not transposed NIS2, although the deadline passed on 17 October 2024. That is why, in July 2026, the Commission referred Spain to the Court of Justice of the EU. In addition, Royal Decree 806/2026 dissolved Parliament and called elections for 29 November, so the law will not pass in 2026. Meanwhile, Royal Decree-law 12/2018 remains in force.
For example, that decree-law requires operators of essential services to appoint an information security officer. However, its fines, of up to one million euros, fall on the entity rather than on its managers. Even so, the board already has a general duty today: Spain’s Companies Act requires directors to act with the diligence of an orderly business person (Article 225). It also makes them answer for damage caused through wilful misconduct or negligence (Article 236). Therefore, Spanish authorities cannot yet enforce NIS2 management liability as such. We go deeper in the state of NIS2 transposition in Spain.
NIS2 and DORA: management liability compared
By contrast, if your entity is a financial one, DORA takes precedence as the sector-specific law. Its Article 5 goes even further than NIS2. So NIS2 management liability and the DORA rules look alike, but they are not identical. We also summarise DORA in what DORA is and who it affects.
| Aspect | NIS2 (Arts. 20, 32 and 33) | DORA (Arts. 5 and 50) |
|---|---|---|
| Type of law | Directive: depends on national law | Regulation: applies since 17/01/2025 |
| What management approves | The Article 21 risk-management measures | The whole ICT risk framework, the resilience strategy, continuity, audits and the third-party policy |
| Degree of responsibility | The management body can answer for breaches of Article 21 | «Ultimate responsibility» for managing ICT risk (Art. 5(2)(a)) |
| Training | Mandatory for members of the management body | Specific, regular training to keep up to date (Art. 5(4)) |
| Budget | Not mentioned explicitly | Allocate and review the resilience budget (Art. 5(2)(g)) |
| Penalties on individuals | Personal liability (32(6)) and ban in essential entities (32(5)) | Penalties applicable to management body members under national law (Art. 50(5)) |
Frequently asked questions on NIS2 management liability
Can authorities sanction a director personally?
Yes, if national law provides for it, because the directive requires that possibility. In fact, Article 32(6) requires that whoever runs or represents the entity can answer for failing to ensure compliance. However, each country will decide how and before whom.
Can authorities bar a director from office?
Only in essential entities, as a last resort and temporarily. Also, it only affects the person acting as chief executive or legal representative, and it lasts until the entity fixes the deficiencies.
What training must management receive?
Enough to identify risks and assess cybersecurity risk-management practices. You need not become a technical expert, but you must understand enough not to approve blindly.
Does NIS2 management liability already apply in Spain?
Not yet, because the transposition law is missing. Even so, directors’ duty of diligence already exists. Also, if you operate in countries that have transposed NIS2, their rules may apply to you there.
Is delegating to the security officer enough?
No. You can delegate execution, but approving, overseeing and understanding remain the board’s job. In fact, «IT was handling it» does not clear you: it shows the duty you failed.
Reviewed on 14 October 2026. For information only, not legal advice.
How Atalaya GRC helps with NIS2 management liability
Atalaya GRC gives the board a clear view of the real status, service by service, in business language. It also records approvals, reviews and training as dated evidence. In addition, with «one control, many regulations» you reuse work done for ISO 27001, ENS or DORA. Finally, the regulatory clock warns you before deadlines, and incident management guides the 24- and 72-hour notifications. See our NIS2 guide or request a demo.

