Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

How do we…

How do we plan cybersecurity training for our management body?

4 decision pointsThe pack behind this answer: NIS2 Implementation & Readiness

Add to board memo

The short answer

Recommendation
Train every member of the management body at least once a year, and each new member soon after appointment, on a programme with one topic for each duty the body has. Use your own readiness result, gaps and cyber report in every session, and keep the attendance, topics and materials as the record.
Reasoning
NIS2 requires members of the management body to follow training, so that each can judge the entity's cyber risks and challenge how they are managed. The Directive sets no interval, so the cadence is the pack's (NR-05). Training built around the body's own position, rather than general awareness, is what lets members challenge the cyber report. The plan is also the record: what each member attended, when and what it covered, which a supervisor may ask for. A member past their due date and not trained since means the duty is not met for them.
Considerations
  • The 12-month cadence, the 3 months for a new member, the 60-day book-ahead window and the programme of about 120 minutes are the pack's defaults. National law may set a shorter cadence or required content, so check with counsel. This is not legal advice.
  • Where the body is one or two people, one session a year covering all six topics is enough. Keep the attendance record all the same.
  • An outside trainer or provider may deliver sessions, but the content and the attendance record stay yours.
  • A financial entity under DORA keeps its management body's ICT risk training to DORA's own requirement as well.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 18 steps.
  1. Start

    The management body needs a cybersecurity training plan

    NIS2 requires members of the management body to follow training, so that each can judge the entity's cyber risks and challenge how they are managed. The plan is also the record: what each member attended, when, and what it covered. A supervisor may ask for it.

  2. Step

    List every member of the body, with the date appointed

    The body is the board of directors, or the management board in a two-tier structure; where there is no board, the people national law makes responsible for running the entity. NIS2 does not define the term, so confirm with counsel. Record each member's role and appointment date, and keep members who leave on the list with the date they left.

  3. Step

    Set the cadence: yearly, and soon after appointment

    The pack's defaults: every member at least every 12 months, and a new member within 3 months of appointment. Shorten them if national law sets a shorter time. Each member's next due date is the last training plus 12 months, or, for someone not yet trained, the appointment date plus 3 months.

    In the pack

  4. Step

    Build one topic for each duty the body has

    The pack's default is six topics, about 120 minutes: your NIS2 status and what it asks of the body; the ten measures and where you stand; top risks and appetite; incidents and the decisions only the board or its equivalent takes; supervision, enforcement and personal accountability; reading and challenging the cyber report. Change the content, but keep a topic for each duty.

  5. Step

    Use your own readiness result, gaps and cyber report

    Each session should speak of the entity's own position, so the plan depends on the latest readiness result, the open gaps and the quarterly cyber report. The annual session refreshes all six topics with the year's readiness result, incidents and gaps.

    In the pack

  6. Decision

    Is the management body one or two people?

    The pack scales the plan to the size of the body. The attendance record is kept in every case.

    In the pack

  7. Step

    Hold one session a year covering all six topics

    For a body of one or two people, one session a year that covers every topic is enough. It can be a briefing by the NIS2 lead or an outside trainer. Keep the attendance record all the same.

    In the pack

  8. Step

    Plan an annual session, inductions and refreshers

    The annual session covers all six topics for every member. An induction covers the whole programme for a new member. A refresher covers the topics a material change touches, for example a change in the law, the classification or the risks. An outside trainer or provider may deliver sessions, but the content and attendance record stay yours.

  9. Step

    Have the chair and the board secretary approve the plan

    The plan names its objectives and measures of success, who is trained, the trainer, the budget and the review points. The pack has the chair of the management body and the board secretary approve it.

    In the pack

  10. Decision

    Has a member joined who is not yet trained?

    A new member falls due soon after appointment, so the induction cannot wait for the next annual session. The board secretary checks when a member joins.

    In the pack

  11. Step

    Book their induction in their first month

    The pack's review point is an induction booked within the first month, inside the 3 months. In the pack's example, a member appointed in mid-July was booked on an induction in early October, before the due date in mid-October. A booking after the due date shows as a problem to move forward.

  12. Step

    Book every member before they fall due

    In the pack's default, a member due within 60 days and not booked shows Book now. Move any booking that falls after the member's due date. Check every member's status and bookings each quarter.

  13. Step

    Record attendance, topics and materials for each session

    One row per member per session: booked, then attended yes or no. For each session keep the date, the trainer, the topics covered, the agenda, the slides and the sign-in, and say where they are kept. That, with the plan, is the record a supervisor may ask for.

  14. Decision

    Is any member past their due date and untrained?

    A member past the due date and not trained since is overdue, and the training duty is not met for them. If a member's status is not known, check it before answering no.

  15. Outcome

    Train them at once, and report it as not met

    Train anyone overdue at once. Report the gap with the quarterly cyber report and in your management body record, with the date it will close. A member of the body who is not trained is itself a gap your readiness work should track.

    In the pack

  16. Decision

    Did a session leave out a topic for anyone?

    The plan counts sessions that left out a topic. A member who missed a topic should cover it at the next session.

    In the pack

  17. Step

    Cover the missed topic at their next session

    The plan marks which topics each session covered. Make sure the member's next session includes the topic they missed, and check afterwards that it did.

  18. Outcome

    Report the board's figure with the quarterly cyber report

    Report how many members are trained, as the board half of the board and staff training measure, and give the figures to whoever keeps the management body record. Once a year, at the annual approval, the chair and the NIS2 lead review the programme's content.

    In the pack

Practical checklist

  1. List every member of the management body with their role and appointment date, keeping leavers on the list.
  2. Set the cadence: yearly for every member, and within the pack's 3 months for a new member.
  3. Build the programme with one topic for each duty, using your own readiness result, gaps and cyber report.
  4. Plan an annual session, inductions and refreshers after a material change, and have the plan approved.
  5. Book a new member's induction in their first month, and book every member before they fall due.
  6. Record attendance, topics, trainer and materials for every session.
  7. Train anyone overdue at once and report it as not met; cover any missed topic at the next session.
  8. Report the board's training figure with the quarterly cyber report.

Evidence to have ready

  • The approved training plan, with its objectives, cadence and programme.
  • The list of members with appointment dates, last training and next due date.
  • For each session: the date, trainer, topics covered, agenda, slides and sign-in.
  • Attendance records, one row per member per session.
  • The board's training figure as reported, and the training part of the management body record.

Assumptions

  • Your entity is in scope of NIS2, and you know who counts as its management body.
  • This follows the CISO Times NIS2 pack. It is not legal advice. National law may add to the Directive, for example how often members must be trained, so confirm with counsel.
  • The 12-month cadence, the 3 months for a new member, the 60-day book-ahead window and the programme of about 120 minutes are the pack's defaults. National law may set a shorter cadence; the window and the programme are yours to set.

Not covered here