NIS2 Article 20: what management can document about credential risk

The NIS2 Article 20 management body duties are to approve and oversee the Article 21 risk-management measures and to follow training. Credential risk sits inside those measures: risk analysis, incident handling, cyber hygiene, access control and multi-factor authentication. As practical guidance, not a requirement of the text, a management body can keep six records: approval, risk analysis, oversight, handling procedure, training and corrective actions. NIS2 does not require executive exposure monitoring.

WebThreat Research · Published · 5 min read

Current as of · Editorial policy

What Article 20 asks of the management body

Article 20(1) of Directive (EU) 2022/2555 (NIS2) says 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." Article 20(2) adds that members of management bodies "are required to follow training."

So the management body has two working verbs, approve and oversee, plus a training duty. The European Commission describes the effect as "accountability of the top management for non-compliance with cybersecurity risk management measures." Our pillar article on what NIS2 and DORA ask of management bodies covers liability and enforcement. This one stays with a practical question: what can a management body write down about one specific risk, stolen and leaked credentials?

This is general information, not legal advice. It does not say whether NIS2 applies to your organization. Scope depends on NIS2 Articles 2 and 3 and on national transposing law.

Credentials in the text of NIS2

NIS2 does not mention executives' passwords, breach data or leak databases. It does not require any organization to monitor where its leaders' credentials appear. Anything in this article about credential risk is one way to apply general duties, not a requirement of the text.

Where credential risk sits in Article 21

Article 21(2) lists measures that "shall include at least" ten points. Five of them bear directly on credentials:

Point Article 21(2) wording How credential risk fits
(a) "policies on risk analysis and information system security" Leaked or reused credentials are a risk the analysis can name.
(b) "incident handling" A credential found in breach data needs a defined response.
(g) "basic cyber hygiene practices and cybersecurity training" Password reuse is a hygiene topic.
(i) "human resources security, access control policies and asset management" Who can sign in to what, and how access ends.
(j) "the use of multi-factor authentication or continuous authentication solutions ... where appropriate" A stolen password alone does not open an account protected by a second factor.

Article 21(1) also ties proportionality to "the degree of the entity's exposure to risks." Article 21(4) requires Member States to ensure that an entity that "finds that it does not comply with the measures provided for in paragraph 2 takes, without undue delay, all necessary, appropriate and proportionate corrective measures."

What supervisors can ask to see

For essential entities, Article 32(2) gives competent authorities the power to make "requests for information necessary to assess the cybersecurity risk-management measures adopted by the entity concerned, including documented cybersecurity policies" (point (e)) and "requests for evidence of implementation of cybersecurity policies" (point (g)). For important entities, Article 33(2) gives similar powers on an ex post basis, in points (d) and (f).

The text does not prescribe the form of these documents, and it does not list records a management body must keep.

Six records worth keeping: practical guidance, not law

The list below is WebThreat Research's practical suggestion. It is not taken from NIS2, it is not a legal checklist, and keeping these records does not by itself show compliance. Counsel can adapt it to national law and to what your supervisor asks for.

1. The approval. Minutes that show the management body approved the measures, including the access control policy, the scope of multi-factor authentication and the password policy. If executives' accounts are in scope for multi-factor authentication, the minutes can say so.

2. The risk analysis entry. A line in the risk register that names credential exposure of senior people as a risk, with an owner, the data used to assess it and the date of the last check.

3. The oversight record. What the management body was shown about credential risk, when, and what it decided. Article 20(1) says "oversee," and a record of what was reviewed is how oversight becomes visible.

4. The handling procedure. What happens when a leader's credential turns up in breach data: who is told, which password is changed, whether reuse on other accounts is checked, and whether multi-factor authentication is confirmed. Our guide on what to do when an executive's password is in a breach walks through the steps.

5. The training record. Who on the management body followed training under Article 20(2), when, and whether credential hygiene was covered. Article 20(2) states the purpose: "sufficient knowledge and skills to enable them to identify risks and assess cybersecurity risk-management practices."

6. The corrective actions. Gaps found, and what was done about them, with dates. This is the record Article 21(4) points toward.

Record Related NIS2 text
Approval of measures Article 20(1), Article 21(2)
Risk analysis entry Article 21(1), Article 21(2)(a)
Oversight record Article 20(1)
Handling procedure Article 21(2)(b)
Training record Article 20(2), Article 21(2)(g)
Corrective actions Article 21(4)

When a leaked password is an incident

Article 23(3) calls an incident significant if "it has caused or is capable of causing severe operational disruption of the services or financial loss for the entity concerned" or "it has affected or is capable of affecting other natural or legal persons by causing considerable material or non-material damage." Significant incidents trigger the reporting steps in Article 23(4), starting with an early warning "within 24 hours of becoming aware of the significant incident."

NIS2 does not say how a leaked password should be classified. A password found in an old breach and a password used to sign in to a company system are very different facts, and whether either one is an incident, or a significant one, is a question for counsel and the security team. The handling procedure in record 4 can say who makes that call.

Where an outside-in check fits

Records 2 and 3 need data. One source is a check of breach corpora and leak databases for the leadership team's records. CEM, WebThreat's executive exposure product, finds a company's leadership team from the company name, checks each person against breach corpora and leak databases, and ranks the findings by what to fix first, using factors set out in our methodology. Nothing is installed.

Each scan gives records 2 and 3 a dated, per-person result to put in the risk register and show the management body, with first findings within minutes. It describes the records found at the time of the scan. It does not by itself make an organization compliant with NIS2, and the management body still decides what to approve and how to oversee it. For the terms used here, see the glossary entry on NIS2.

Frequently asked questions

Does NIS2 require monitoring of executives' credentials?

No. NIS2 does not mention executives' credentials or breach data. Credential risk falls under the general Article 21(2) measures, such as risk analysis, cyber hygiene, access control and multi-factor authentication.

What does NIS2 Article 20 require of the management body?

Article 20(1) says the management body approves the Article 21 risk-management measures, oversees their implementation and can be held liable for infringements. Article 20(2) says its members are required to follow training.

What can a management body document about credential risk?

As practical guidance rather than a legal requirement: its approval of the measures, a risk analysis entry, a record of oversight, a handling procedure for leaked credentials, training records and corrective actions. NIS2 does not prescribe these records or their form.

Is a leaked executive password a significant incident under NIS2?

NIS2 does not say. Article 23(3) defines significant incidents by operational disruption, financial loss or considerable damage to others, and whether a specific case qualifies is a question for counsel.

Does using CEM make an organization NIS2 compliant?

No. CEM shows which leaders have records in breach corpora and leak databases and ranks what to fix first. That is one input to a risk analysis; the management body still approves and oversees the measures.

Terms used in this article

Sources

  1. Directive (EU) 2022/2555 (NIS2 Directive), Official Journal of the European Union, accessed
  2. NIS2 Directive: securing network and information systems, European Commission, accessed

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.