Year-end review & approvals
- Review and approve the ICT risk management frameworkDORA Art. 5(2), 6(5)
- Approve the digital operational resilience testing programmeDORA Art. 24
- Follow up last year's audit and test findingsDORA Art. 6(6)
Board Reporting
Under DORA Art. 5(2) the management body bears final responsibility for ICT risk. Tasks can be delegated, accountability cannot. This guide shows what should reach the board agenda, and when.
01 · Foundation
Regular reports that keep the board informed: risk status, test results, third-party exposure.
Event-driven briefings when something serious happens, such as a major ICT incident.
Decisions the board itself must take and record in the minutes.
02 · Annual agenda
A suggested rhythm. DORA requires these items at least yearly but does not fix the quarter, so adapt it to your board calendar.
03 · Escalation
These events should reach the board between scheduled meetings.
Inform the board promptly once an incident is classified as major and reported to the supervisor. Brief on impact, measures and follow-up.
DORA Art. 17(3)(e), 19
The board must be informed of planned arrangements that support critical or important functions, and of material changes.
DORA Art. 28(2)
A serious threat that could affect critical services should reach the board, even if no incident has happened yet.
DORA Art. 19(2)
Remarks, orders or inspections from Finansinspektionen or an ESA on ICT risk.
DORA Art. 50
04 · Approvals log
Supervisors expect to find these approvals in the board minutes. Tick off what is approved and up to date. Progress is saved only in this browser.
0 of 6 approved
05 · Export
Below is the full checklist as plain text. Copy it for the board secretary or the risk and compliance function.
DORA Board Agenda & Oversight Checklist Q1 — Year-end review & approvals [ ] Review and approve the ICT risk management framework (DORA Art. 5(2), 6(5)) [ ] Approve the digital operational resilience testing programme (DORA Art. 24) [ ] Follow up last year's audit and test findings (DORA Art. 6(6)) Q2 — Third parties & register [ ] Annual report on ICT third-party providers and concentration risk (DORA Art. 28(2–3)) [ ] Status of contract clauses and exit strategies for critical functions (DORA Art. 28(8), 30) Q3 — Continuity & crisis readiness [ ] Business continuity and disaster recovery plans (DORA Art. 11) [ ] Results of continuity, backup and restore tests (DORA Art. 11(6), 12) Q4 — Security status & board competence [ ] Annual ICT and cybersecurity status report (DORA Art. 6(5); RTS 2024/1774) [ ] Review the board's own ICT risk training plan (DORA Art. 5(4)) [ ] Approve the ICT budget for the coming year (DORA Art. 5(2)(g)) Ad-hoc escalations - Major ICT-related incident (DORA Art. 17(3)(e), 19) - New or changed contract for a critical or important function (DORA Art. 28(2)) - Significant cyber threat (DORA Art. 19(2)) - Supervisory findings or orders (DORA Art. 50) Mandatory board approvals (record in minutes) [ ] ICT risk management framework (DORA Art. 5(2)(b), 6) [ ] Digital operational resilience strategy (DORA Art. 6(8)) [ ] ICT business continuity policy (DORA Art. 5(2)(e), 11) [ ] ICT response and recovery plans (DORA Art. 5(2)(e), 11(3)) [ ] Policy on use of ICT third-party services (DORA Art. 5(2)(h), 28(2)) [ ] ICT internal audit plans (DORA Art. 5(2)(f)) Source: https://dora.gunnarslott.se/board-reporting
Board members also need regular ICT risk training (Art. 5(4)) — see the Board Track.
Educational overview, not legal advice. Check article references against the official text on the Legal Acts page.