An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesEvidence for management oversight
Governance / 2026-09-26

Evidence for management oversight

Article 20 of Directive (EU) 2022/2555 makes the management bodies of essential and important entities responsible for approving cybersecurity risk-management measures and overseeing their implementation. Oversight that cannot be evidenced did not, for supervisory purposes, happen - so this guide sets out the records that show approval, oversight, training and follow-through as part of normal governance.

What Article 20 actually asks of management

Management bodies must approve the cybersecurity risk-management measures the entity takes under Article 21, oversee their implementation, and can be held liable for infringements under national law. Members of management bodies are also expected to follow training so they can identify risks and assess risk-management practices. The article does not ask directors to become engineers; it asks them to govern - to decide, to resource, to question and to record.

Approval evidence: the decision layer

The core record is the approval itself: dated minutes or a written decision that identifies the measures approved, the risk assessment they rest on, the resources committed and any measures considered and deferred, with reasons. Approving a budget line is weaker than approving a defined set of measures against a stated risk picture. Where management accepts a residual risk or an exception, the acceptance, its owner and its review date belong in the same record.

Oversight evidence: the reporting rhythm

Oversight is a rhythm, not an annual event. Establish a regular reporting pack to the management body covering the state of the Article 21 measures, significant incidents and near misses, testing and audit results, supplier and concentration risks, and overdue remediation, each with named owners. The pack matters less than the trail it creates: questions asked, actions set, deadlines given and completion checked at the next meeting. That trail is the evidence that oversight was exercised rather than received.

  • Standing agenda item with a defined reporting pack
  • Actions logged with owners and dates, and reviewed for completion
  • Escalation route for risks management decides not to accept

Training records for management bodies

Article 20 expects members of management bodies to be able to gain sufficient knowledge and skills to identify risks and assess cybersecurity risk-management practices and their impact on the services the entity provides. Keep training records at the same standard as other governance records: who attended, what was covered, when, and what follow-up was agreed. Generic awareness completion certificates say little; scenario-based sessions tied to the entity own risk picture evidence the capability the article is aiming at.

The record also protects management itself

Article 20 is not only an organisational duty: it contemplates personal consequences. Member States must be able to hold management bodies liable for infringements of the Article 21 duty under their national rules, and for essential entities the Directive provides for the possibility of a temporary prohibition on exercising managerial functions in serious cases. A contemporaneous record of informed decisions - what was presented, what was asked, what was decided and what was resourced - is therefore the same evidence that shows the organisation was governed and that the individuals governing it acted on the information they had. Oversight done on paper after the fact protects nobody; oversight recorded as it happens is both the compliance artefact and the defence.

Connect oversight to incidents and change

Oversight evidence is tested hardest after an incident. Records should show how significant incidents reach the management body, what decisions management took during and after the event, and how lessons changed the measures. The same applies to major change: entering a new market, adopting a critical supplier or replacing a core platform should surface in management reporting before the risk lands, not after.

Keep the record proportionate and findable

Article 20 does not require a separate bureaucracy. Most entities can evidence oversight inside existing governance: board or executive committee minutes, the risk register, the audit plan and the remediation tracker. What matters is that the cybersecurity content is identifiable inside those records - a decision a supervisor cannot find is a decision that cannot be evidenced. Assign one owner for the governance evidence set and review its completeness whenever the measures are re-approved.

Points of clarification

Can management delegate Article 20 responsibility to a CISO?

Operational work can and should be delegated; accountability cannot. Article 20 keeps approval and oversight with the management body, so the CISO prepares, recommends and reports, while the management body decides and records its decisions.

What is the single most useful oversight record?

The dated approval decision for the Article 21 measures, tied to the risk assessment and revisited when the risk picture changes. It anchors the reporting rhythm, the training duty and the follow-up actions to one identifiable act of governance.

Does Article 20 require management to be cybersecurity experts?

No. It requires enough knowledge and skill to identify risks and assess risk-management practices, gained through training. Oversight quality shows in the questions asked and the decisions recorded, not in technical depth.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.