Report operational resilience to the board through a recurring pack that maps critical or important functions to their impact tolerances (or recovery objectives), shows from test results whether they can be met, and lists major incidents, third-party exposure and the remediation that needs approval. Under DORA (Regulation (EU) 2022/2554, Article 5), the management body bears the ultimate responsibility for ICT risk and must approve, oversee and periodically review the ICT business continuity policy and the ICT response and recovery plans. The report should therefore ask the board for explicit decisions, not just inform it.
The 30-second version
- Who decides: the management body (DORA Art. 5), the management bodies of essential and important entities (NIS2 Art. 20), the board (PRA SS1/21 and FCA PS21/3 in the UK).
- What it shows: critical or important functions against their tolerances, test results, major incidents, critical ICT providers, remediation and budget.
- Where it starts: an up-to-date business impact analysis (BIA). Without one, no impact tolerance is defensible.
- How often: the rules set annual minimums and event triggers; a short quarterly pack plus an annual in-depth review is a good practice, not a legal requirement.
- What proves it: minutes that record approvals, challenges and decisions, dated versions of what was approved, and training records.
What does the board actually have to approve?
DORA (financial entities in the EU). Article 5(2) of Regulation (EU) 2022/2554 requires the management body to define, approve, oversee and be responsible for all arrangements of the ICT risk management framework. In particular it must:
- bear the ultimate responsibility for managing the entity's ICT risk (point (a));
- set and approve the digital operational resilience strategy referred to in Article 6(8), including the ICT risk tolerance level (point (d));
- approve, oversee and periodically review the ICT business continuity policy and the ICT response and recovery plans of Article 11 (point (e));
- approve and periodically review the ICT internal audit plans (point (f));
- allocate and periodically review the budget for digital operational resilience (point (g));
- approve and periodically review the policy on the use of ICT services provided by ICT third-party service providers (point (h));
- put in place reporting channels so that it is informed of arrangements with ICT third-party service providers, planned material changes to them, and at least major ICT-related incidents with their impact and the response, recovery and corrective measures (point (i)).
Article 5(4) adds that members of the management body must keep sufficient knowledge and skills to understand and assess ICT risk, including by following specific training on a regular basis. Note that Article 16 sets a simplified ICT risk management framework for certain smaller entities, to which Articles 5 to 15 do not apply.
NIS2 (essential and important entities). Article 20(1) of Directive (EU) 2022/2555 requires management bodies to approve the cybersecurity risk-management measures taken under Article 21, oversee their implementation, and makes them liable for infringements. Article 20(2) requires their members to follow training. NIS2 is a directive: the precise obligations and sanctions come from each Member State's transposition law. For financial entities, DORA applies as the sector-specific act.
UK (PRA and FCA). Under the Bank of England / PRA Supervisory Statement SS1/21 and the FCA Policy Statement PS21/3, the board of a firm in scope approves the important business services, the impact tolerances set for them and the self-assessment.
The Basel Committee's Principles for Operational Resilience (March 2021) take the same line for banks: governance by the board comes first.
| Board report item | Regulatory basis | Minimum frequency / trigger | Decision expected from the board |
|---|---|---|---|
| Digital operational resilience strategy | DORA Art. 5(2)(d), Art. 6(8) | Adoption and periodic review | Approve |
| ICT business continuity policy, response and recovery plans | DORA Art. 5(2)(e), Art. 11 | Periodic review | Approve and oversee |
| Review of the ICT risk management framework | DORA Art. 6(5) | At least yearly and after major ICT-related incidents | Take note, arbitrate gaps |
| Lessons from ICT incidents and resilience tests | DORA Art. 13(5) | At least yearly | Validate the recommendations |
| Major ICT-related incidents and their impact | DORA Art. 5(2)(i) | Each major incident | Be informed, decide on measures |
| Arrangements with ICT third-party service providers | DORA Art. 5(2)(h) and (i), Art. 28 | Periodic review, material changes | Approve the policy, follow the risks |
| Cybersecurity risk-management measures | NIS2 Art. 20 and 21 | Ongoing oversight | Approve and oversee |
| Important business services, impact tolerances, self-assessment (UK) | PRA SS1/21, FCA PS21/3 | Regular review | Approve |
Which metrics belong in a board-level resilience report?
Separate decision metrics, which the board needs, from operational metrics, which stay with management (server availability, patch rates, ticket volumes). A short list is enough:
- Critical or important functions and their status against impact tolerances, or against the MTPD and RTO set in the BIA: within tolerance, at risk, in breach, not yet tested.
- Results of the latest tests. DORA Articles 24 and 25 set the digital operational resilience testing programme; Article 24(6) requires appropriate tests at least yearly on all ICT systems and applications supporting critical or important functions.
- Major ICT-related incidents since the last report, their impact and the lessons drawn.
- Concentration and criticality of ICT third-party providers, drawn from the register of information of DORA Article 28(3) (see our DORA register of information guide).
- Remediation plan: open actions with owner, deadline and the budget requested.
These metrics all come out of the BIA. It is the BIA that identifies the critical functions, their dependencies and the time after which a disruption becomes intolerable. Without a current BIA, the tolerance shown to the board is a guess. Our BIA guide explains how to run one.
How do you build the report step by step?
- Start from the BIA: list the critical or important functions, their dependencies and their thresholds (MTPD, RTO, or impact tolerance).
- Map the resources each one needs: people, technology, sites, information and third parties.
- Test the thresholds against test results and severe but plausible scenarios: can the function really come back in time?
- Qualify the gaps: each vulnerability with its cause and the function it threatens.
- Write the decisions expected from the board: for each gap, two or three options with their cost and residual risk, a recommendation and a deadline.
- Record the decision and follow it up: the minutes state the decision and the reason; the next report shows whether the gap closed.
A decision request should stay short and comparable. An illustrative example: "In the last test, customer payments came back in 9 hours against a 4-hour objective. Options: second processing site, new recovery clause with the provider, or accept the risk for six months. Recommendation and cost attached. Decision needed by the next meeting."
In ResiPlan, the BIA works out the MTPD and suggests an RTO and a criticality for each process, checks whether the applications, infrastructure and suppliers it depends on come back in time, and freezes each approved version. The register of information and the dependencies simulator feed the third-party and cascade views. The tool gathers the evidence; the board's approval and the assessment of compliance remain yours and your supervisor's.
How often should the board receive it?
The verifiable minimums under DORA are:
- the ICT risk management framework is documented and reviewed at least once a year (periodically for microenterprises) and after major ICT-related incidents, among other triggers (Article 6(5));
- senior ICT staff report at least yearly to the management body on the lessons drawn from resilience testing and real ICT incidents, with recommendations (Article 13(5));
- the management body is informed of major ICT-related incidents through the reporting channels of Article 5(2)(i).
On that base, we recommend a short quarterly summary and an annual in-depth review of the strategy, policy and plans. That rhythm is a good practice, not a regulatory requirement.
How do you make the board's oversight demonstrable to supervisors?
- Minutes that record the approvals, the questions and challenges raised, and the decisions taken with their reasons.
- Dated versions of the strategy, policy and plans, each linked to the meeting that approved it.
- Training records for board members (DORA Art. 5(4), NIS2 Art. 20(2)).
- In the UK, the approved self-assessment (PRA SS1/21, FCA PS21/3).
- For organisations certified or preparing for certification, the management review of ISO 22301:2019 (clause 9.3), which can share the same inputs. See our ISO 22301 checklist.
Common mistakes in board resilience reporting
- Infrastructure KPIs with no link to services. The board approves policies and plans for functions (DORA Art. 5(2)(e)), not server metrics.
- No decision requested. The management body must allocate the budget and approve plans (Art. 5(2)(e) and (g)); a report that asks nothing leaves those duties without a trace.
- Untested tolerances. A green status without a test behind it says nothing (DORA Art. 24 and 25).
- Critical third parties missing. The board must be informed of arrangements with ICT providers and material changes to them (Art. 5(2)(i), Art. 28).
- An out-of-date BIA. Thresholds drawn from last year's processes do not support this year's tolerances.
Board report template
A six-part agenda, one page per part, details in annexes:
- Summary and decisions requested: what changed, what the board must decide today.
- Critical or important functions against tolerances: status per function.
- Tests: what was tested, results, gaps.
- Incidents: major ICT-related incidents, impact, lessons.
- Third parties: critical providers, concentration, material changes, exit plans.
- Remediation and budget: open actions by age and severity, funding requested.
To check where you stand before the first pack, use the DORA readiness checklist or the NIS2 compliance checklist. The Resiplan business continuity platform keeps the BIA, dependencies, plans and approvals linked, so the figures in the pack come from the same source each quarter.
Frequently asked questions
Is the board legally responsible for operational resilience under DORA?
Yes. Article 5(2)(a) of DORA states that the management body bears the ultimate responsibility for managing the financial entity's ICT risk, and Article 5(2) makes it responsible for the implementation of the whole ICT risk management framework.
What is the difference between an impact tolerance and an RTO in board reporting?
An impact tolerance, in the UK rules, is the maximum tolerable level of disruption to an important business service, set from the point of view of harm to customers, the market or the firm. An RTO is a recovery time objective for a process or system, usually set in the BIA below the maximum tolerable period of disruption (MTPD). Both can be shown to the board; the tolerance answers "how much disruption can we accept", the RTO "how fast do we plan to recover".
How often should operational resilience be reported to the board?
DORA requires at least a yearly review of the ICT risk management framework and after major ICT-related incidents (Art. 6(5)), and at least a yearly report from senior ICT staff on lessons learned (Art. 13(5)). A quarterly summary with an annual in-depth review is a good practice on top of those minimums.
Which metrics should a board operational resilience dashboard include?
Status of critical or important functions against tolerances, latest test results, major incidents, critical ICT providers and concentration, and the remediation plan with the budget requested. Keep operational KPIs in the annexes.
Do board members need specific training on ICT and cyber risk?
Yes. DORA Article 5(4) requires members of the management body to keep sufficient knowledge and skills, including through regular specific training, and NIS2 Article 20(2) requires members of management bodies to follow training.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 5, 6, 11, 13, 16, 24, 25 and 28, EUR-Lex.
- Directive (EU) 2022/2555 (NIS2), Articles 20 and 21, EUR-Lex.
- Bank of England / PRA, Supervisory Statement SS1/21, Operational resilience: Impact tolerances for important business services.
- FCA, Policy Statement PS21/3, Building operational resilience.
- Basel Committee on Banking Supervision, Principles for Operational Resilience, March 2021.
- ISO 22301:2019, Security and resilience: Business continuity management systems, clause 9.3 Management review.