NIS2 and DORA: what management bodies must approve, oversee and learn
Under NIS2 Article 20, the management bodies of essential and important entities approve the cybersecurity risk-management measures, oversee their implementation, can be held liable for infringements and must follow training. NIS2 management liability is then shaped by national law. DORA Article 5 gives the management body of a financial entity ultimate responsibility for ICT risk, plus strategy, budget and training duties.
WebThreat Research · Published · 6 min read
Current as of · Editorial policy
What NIS2 and DORA require of management bodies
This article summarizes what two EU laws say about the people at the top of an organization: Directive (EU) 2022/2555 (NIS2) and Regulation (EU) 2022/2554 (DORA). It quotes the articles that set duties for management bodies and gives their numbers so you can read them in full on EUR-Lex.
It is general information, not legal advice. It does not tell you whether your organization is covered. NIS2 scope is set by Articles 2 and 3 and by the national law of each Member State; DORA scope is set by its Article 2. Ask counsel to apply them to your facts.
NIS2 Article 20: approve, oversee, be held liable
Governance sits in Article 20 of NIS2. Paragraph 1 reads:
"Member States shall ensure that the management bodies of essential and important entities approve the cybersecurity risk-management measures taken by those entities in order to comply with Article 21, oversee its implementation and can be held liable for infringements by the entities of that Article."
The sentence gives the management body three positions: it approves the measures, it oversees how they are implemented, and it can be held liable when the entity infringes Article 21. The same paragraph adds that this is "without prejudice to national law as regards the liability rules applicable to public institutions, as well as the liability of public servants and elected or appointed officials."
Two points are easy to get wrong. The directive is addressed to Member States, so how liability works in practice comes from each national transposing law. And the verbs are "approve" and "oversee": read them as written before relying on a summary that goes further.
The European Commission summarizes the effect this way: NIS2 "introduces accountability of the top management for non-compliance with cybersecurity risk management measures thus bringing cybersecurity to the attention of the boardroom."
What the management body approves: the Article 21 measures
Article 21(1) asks entities to take "appropriate and proportionate technical, operational and organisational measures" to manage risks to their network and information systems. Proportionality takes account of "the degree of the entity's exposure to risks, the entity's size and the likelihood of occurrence of incidents and their severity."
Article 21(2) lists what the measures "shall include at least":
| Point | Measure, as written in Article 21(2) |
|---|---|
| (a) | policies on risk analysis and information system security |
| (b) | incident handling |
| (c) | business continuity, such as backup management and disaster recovery, and crisis management |
| (d) | supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers |
| (e) | security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure |
| (f) | policies and procedures to assess the effectiveness of cybersecurity risk-management measures |
| (g) | basic cyber hygiene practices and cybersecurity training |
| (h) | policies and procedures regarding the use of cryptography and, where appropriate, encryption |
| (i) | human resources security, access control policies and asset management |
| (j) | the use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate |
This list is what the management body approves under Article 20(1). Our companion piece on NIS2 Article 20 and credential risk looks at points (a), (g), (i) and (j) in more detail.
Where enforcement can reach individuals
NIS2 sets fines for entities and two measures that reach people: a temporary ban for essential entities only, and a liability rule that covers both kinds of entity.
Fines on the entity. Article 34(4) sets fines for essential entities that infringe Article 21 or 23 "of a maximum of at least EUR 10 000 000 or of a maximum of at least 2 % of the total worldwide annual turnover in the preceding financial year of the undertaking to which the essential entity belongs, whichever is higher." Article 34(5) sets the figures for important entities at "at least EUR 7 000 000" or "at least 1,4 %."
A temporary ban, as a last step. Article 32(5) applies when earlier enforcement measures "are ineffective" and a deadline to fix the problem has passed. Competent authorities can then ask that courts or other bodies, "in accordance with national law, prohibit temporarily any natural person who is responsible for discharging managerial responsibilities at chief executive officer or legal representative level in the essential entity from exercising managerial functions in that entity." Such prohibitions apply "only until the entity concerned takes the necessary action."
Liability for the duty to ensure compliance. Article 32(6) says Member States "shall ensure that it is possible to hold such natural persons liable for breach of their duties to ensure compliance with this Directive," referring to people who represent, take decisions for or control an essential entity.
These provisions sit in Article 32, which covers essential entities. The temporary ban in Article 32(5) has no counterpart in Article 33, which covers important entities. The liability rule in Article 32(6) does reach them: Article 33(5) says that "Article 32(6), (7) and (8) shall apply mutatis mutandis" to the measures for important entities. The details of any personal liability come from national law.
DORA Article 5: the management body and ICT risk
DORA is a regulation, so it applies directly. Article 64 states: "It shall apply from 17 January 2025."
Article 5(2) says the management body of a financial entity "shall define, approve, oversee and be responsible for the implementation of all arrangements related to the ICT risk management framework referred to in Article 6(1)." It then lists what the management body shall do, including:
- "(a) bear the ultimate responsibility for managing the financial entity's ICT risk;"
- "(d) bear the overall responsibility for setting and approving the digital operational resilience strategy";
- "(g) allocate and periodically review the appropriate budget to fulfil the financial entity's digital operational resilience needs";
- "(h) approve and periodically review the financial entity's policy on arrangements regarding the use of ICT services provided by ICT third-party service providers".
On individuals, Article 50(5) requires Member States, where penalties apply to legal persons, to give competent authorities "the power to apply the administrative penalties and remedial measures, subject to the conditions provided for in national law, to members of the management body, and to other individuals who under national law are responsible for the breach."
What both laws expect leaders to learn
Both texts put training on the management body itself.
| NIS2 | DORA | |
|---|---|---|
| Who | members of the management bodies of essential and important entities | members of the management body of the financial entity |
| Duty | "are required to follow training" (Article 20(2)) | "actively keep up to date with sufficient knowledge and skills to understand and assess ICT risk" (Article 5(4)) |
| Purpose | "to identify risks and assess cybersecurity risk-management practices and their impact on the services provided by the entity" | to understand ICT risk "and its impact on the operations of the financial entity, including by following specific training on a regular basis" |
| Staff | entities are encouraged to offer similar training to employees "on a regular basis" | training applies "to all employees and to senior management staff" (Article 13(6)) |
Where leadership exposure fits
Neither law mentions executives' personal data or leaked passwords. Both ask the management body to understand the organization's risks. NIS2 Article 21(1) ties proportionality to "the degree of the entity's exposure to risks," and Article 21(2)(i) and (j) cover access control and multi-factor authentication.
Credentials of senior people that appear in breach data are one such exposure. CEM, WebThreat's executive exposure product, shows which leaders have records in breach corpora and leak databases and ranks what to fix first with a published method; it gives a risk analysis a concrete input on leadership credentials, while meeting NIS2 and DORA duties remains a matter for the management body and counsel. If your management body wants to see what that looks like, our guides on executive digital exposure and what to do when an executive's password is in a breach explain it. The glossary has short entries on NIS2 and DORA.
Frequently asked questions
What does NIS2 Article 20 require of management bodies?
Article 20(1) says 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. Article 20(2) says their members are required to follow training.
Can managers be banned under NIS2?
For essential entities, Article 32(5)(b) lets competent authorities ask for a temporary prohibition on a person at chief executive officer or legal representative level, in accordance with national law. It applies only after earlier enforcement measures were ineffective and a deadline passed, and only until the entity fixes the problem. Article 33, for important entities, has no equivalent.
What are the maximum NIS2 fines?
Article 34(4) sets a maximum of at least EUR 10 000 000 or at least 2 % of total worldwide annual turnover for essential entities, whichever is higher. Article 34(5) sets at least EUR 7 000 000 or at least 1,4 % for important entities.
What does DORA Article 5 say about the management body?
It says the management body shall define, approve, oversee and be responsible for the ICT risk management framework, bear the ultimate responsibility for managing ICT risk, approve the digital operational resilience strategy and allocate its budget. Article 5(4) requires members to keep their knowledge and skills up to date.
Does this article tell me whether NIS2 or DORA applies to my organization?
No. It is general information, not legal advice. Scope depends on NIS2 Articles 2 and 3, national transposing law and DORA Article 2, applied by counsel to your facts.
Terms used in this article
Sources
- Directive (EU) 2022/2555 (NIS2 Directive), Official Journal of the European Union, accessed
- Regulation (EU) 2022/2554 (Digital Operational Resilience Act), Official Journal of the European Union, accessed
- NIS2 Directive: securing network and information systems, European Commission, accessed
Related
EU regulation and governance
GDPR’s Hidden Pitfalls: How “Fake” Emails, Public Docs, and Geopolitics Converge into Real Privacy Disasters
A three-part investigation into GDPR exposures. “Fake” placeholder emails in public documents turned out to be real addresses. We compared how Microsoft and Vod...
Removal and privacy
Data removal vs breach monitoring: know which one you are buying
Data removal and breach monitoring act on different data. Removal asks people-search sites and data brokers to delete what they publish about a person. Breach m...
Leaked credentials and breach data
Credential leak monitoring: what it can and cannot tell you
Credential leak monitoring tells you which email addresses and passwords tied to your people appear in breach corpora and leak databases, and what was exposed w...
See your leadership's exposure
CEM finds your executives from your company name, checks them against breach corpora and leak databases, and scores each person from 0 to 100.