1. Why the board needs to know, and what it needs
The board of directors, the body that governs the company, is accountable for the risks the company runs, even when it does not know the technical details. A system outage, a data breach or the interruption of a service has economic, legal and reputational consequences that fall on senior management. For this reason the board must receive regular information on cybersecurity, presented in a way that enables it to decide.
The board does not need to know which software versions are installed or how many alerts a system has generated. It needs to know whether the main risks are increasing or decreasing, whether significant events have occurred, whether the company could resume operations within acceptable timescales and which choices fall to it. The report must answer these questions, and no others.
2. Prerequisites: what must exist before the report
A dashboard cannot emerge from nothing. If an inventory of systems and a risk register do not exist, any indicator will be arbitrary, and the board will notice straight away. Before building the report, check that some basic elements are available and that someone is responsible for keeping them up to date. The minimum elements are these. Without them the report becomes a collection of opinions, and the first question from a board member will be about their absence.
- An up-to-date inventory of critical systems and of the suppliers who manage them
- A risk register with owners and the status of treatments
- An internal contact, who may be external to the company, who collects the data each period
- A shared calendar for recovery tests and key reviews
3. Steps to build the report
Build the report starting from the decision the board must take, not from the data available. This order avoids the most common problem: a file full of charts that leads to no choice. Start from the message, then choose the indicators, then design the page. Follow these steps in order. Each step produces an element that stays in the file for the following period, so that comparison over time becomes simple.
- Write in one sentence the main message for the period, for example whether overall risk has changed and why.
- Choose indicators linked to the risk register, not the technical statistics produced by the tools.
- Set a reference threshold for each indicator and the meaning of the colours used on the dashboard.
- Set up the dashboard on a single page, showing the trend compared with the previous period.
- Add at the end the decisions required from the board, with the possible options and the consequences of each.
- Agree with the chair a fixed cadence and the expected reading time.
4. How to build the dashboard
The dashboard is the part the board reads first. It must answer a few recurring questions, always the same over time, so that changes are easy to understand. Indicators change little: if you modify them every time, the board can no longer compare one period with another. The table proposes an organisation by area. Adapt it to your company: not every area is relevant to everyone, and an area without data should be declared as such rather than omitted.
| Area | Question for the board | Example indicator |
|---|---|---|
| Main risks | Which risks have increased or decreased? | High open risks and how long they have been open |
| Incidents | Have there been significant events? | Incidents recorded in the period, with closure status |
| Continuity | Would the company resume operations within acceptable timescales? | Result of the last recovery test and measured actual time |
| Suppliers | Do we depend on suppliers we do not control? | Critical suppliers without a recent security review |
| Access | Do the right people have the right access? | Privileged access reviewed in the period |
5. Common mistakes in reporting
The first mistake is showing too much technical data. A board member cannot assess risk by reading logs, and a page full of acronyms discourages reading. If a technical detail is needed to justify a decision, put it in an annex and refer to it in the main text. The dashboard must remain a governance document, not an operational bulletin. The second mistake is presenting only good news. A report that declares everything under control leaves no room for decisions and loses credibility at the first incident. The third is changing indicators without explaining why. If a measure is no longer useful, replace it and state the change and the reason, so that the comparison remains readable.
6. How to tell whether the report works
A report is effective when it produces useful decisions and questions, not when it receives compliments. After each meeting, check what happened next. If the board has asked nothing, the message was probably unclear or did not concern real choices. Also check whether the report has changed the way senior management discusses security in ordinary meetings. These are the simplest checks to make after the first presentation:
- Has the board taken at least one decision based on the report?
- Were board members able to explain, in their own words, the main risk of the period?
- Are the indicators the same as in the previous period, with the same threshold?
- Were the owners of the actions informed and have they confirmed timescales?
7. What to do after the first report
After the first report the most important work is follow-up. Decisions taken must be tracked in the risk register, with an owner and a deadline. At the next meeting the first item is the status of those decisions, before any new indicator. This creates a cycle in which the board sees that its choices produce effects. Over time the report can connect with other topics covered in this series, such as the security indicators worth measuring, supplier assessment and preparation for an external audit. You do not need to do this straight away. Start with a simple report that works and expand it only once the board uses it.
8. How to start
The first concrete action this week is to write, in a single sentence, the decision the board should take on cybersecurity over the coming months. If you cannot formulate it, a basic piece of information is probably missing, such as the risk register or a clear owner. Then ask the chair for a few minutes at the next meeting to present a single page, with a few indicators and a request for a decision. The first report will not be complete, but it establishes the habit and allows the next one to be better.
Frequently Asked Questions
Is reporting to the board mandatory?
It depends on the legal form, the sector and the specific obligations to which the company is subject. In general, a governing body that is accountable for risks has an interest in receiving regular information, and some sector regulations make governance responsibility explicit. Check with a consultant which obligations apply to your company.
Who should prepare the report?
Usually the security manager, if there is one, or the IT manager working with the administrative management. Where management is outsourced to a supplier, the supplier gathers the data, but the presentation must remain the responsibility of an internal contact who answers the board's questions.
How many pages should the report have?
One page for the dashboard and, if needed, a few pages of annexes with the details. The board must be able to read the main document before the meeting, in a reasonable time. If the content does not fit on the first page, choose what to keep and move the rest to the annexes.
How do I handle an indicator that is getting worse?
Present it first, with the cause, the actions under way, the owner and the expected date of improvement. A deterioration that has been explained is accepted far more readily than a problem the board discovers from other sources. Never hide a negative figure: it is the first thing a reviewer will look for.
Can I use a dashboard generated by an automated tool?
Yes, but the indicators must be chosen by management and linked to the risk register. An automated tool produces a lot of data, often of little use to the board. Use it to collect information and leave the selection to those who have to make the decisions.