Measure what helps you decide
Security teams produce large volumes of operational data: emails blocked, alerts investigated, updates applied. These numbers help run operations but rarely help a board. The book offers a three-part test for any board metric. Does it describe risk rather than effort? Would a sharp change make us act differently? Can it be compared with a target, tolerance or earlier period in a meaningful way?
"Millions of malicious emails blocked" passes none of these tests. A phishing simulation click rate measured against last year and a stated tolerance passes all three. Good board metrics fall into a few families: exposure, control coverage, response capability, people and culture, and third-party risk. Be wary of raw counts without context, percentages that hide what sits outside the denominator, vanity measures such as policies written, and any line that only ever moves in a good direction. Real risk fluctuates.
Leading and lagging indicators
Lagging indicators, such as the number and cost of incidents, show what has already happened. Leading indicators, such as time to fix critical weaknesses, monitoring coverage, protection of privileged accounts, days since the last successful restore test and suppliers without a current assessment, show whether the conditions for future incidents are improving. A quiet year can be luck rather than skill.
In the book's Meridian Foods story, a director proposed holding the security budget flat after a year without significant incidents. The CISO then showed that the time to fix critical weaknesses had risen from eighteen to thirty-one days and that two of seven critical systems had gone more than nine months without a restore test. The board approved an extra engineer and a firm test schedule, a decision it would never have made from the lagging indicator alone.
KPIs, KRIs and how many to show
A key performance indicator (KPI) shows whether the security programme is performing as planned. A key risk indicator (KRI) shows how much risk the company is carrying relative to its appetite. Performance can be excellent while risk rises, for example when the business adds systems and suppliers faster than the team can protect them, so boards need both. Each KRI should have a threshold tied to the risk appetite and an agreed response, owner and date when it is crossed.
A board dashboard works best with roughly eight to twelve indicators, kept stable so trends are visible and reviewed about once a year. Meridian settled on eleven, covering exposure, control coverage, response, people, suppliers, and two KPIs for roadmap progress and spending. Each mapped to a risk in the register, had an owner and a board-approved threshold, and could be justified in one sentence.
The one-page dashboard and the traffic-light traps
A one-page dashboard has four parts: a two- or three-sentence headline in plain business language saying whether risk is within appetite and whether a decision is needed; the agreed indicators with value, threshold and trend; the three to five top risks with business impact and current action; and decisions or asks, stating plainly when there are none. Technical terms should be translated into consequences, for example naming which customer-facing system carries the unfixed weaknesses.
Red, amber and green ratings mislead in four common ways. The watermelon effect hides a red item inside a green average, as when Meridian's MFA rollout showed green at ninety-four percent while the missing accounts were the most valuable ones. Colours chosen without written criteria drift towards green. Frozen ambers sit unnoticed for quarters, so show how long each colour has held. And a report that never shows red should prompt curiosity rather than relief. Experts should also watch for Goodhart's law, averages that hide long tails, unreliable benchmarks and false precision in financial quantification.
Rhythm, audience and what good looks like
For most mid-size companies, a full report to the audit or risk committee each quarter and to the full board once or twice a year is sensible, with agreed triggers for reporting between meetings. At least once a year the board should hold a deeper review that includes an independent view. Committee, board and executives can see different depths of the same data, but the numbers must agree.
Good reporting is short on top and deep underneath, uses plain language and trends, is honest about uncertainty and comfortable with red. At Meridian, a report that drew no questions was rewritten to open with what is good, what is worrying and what is needed, and it produced the board's most useful cyber discussion in years. The tone in which a board receives bad news shapes every report it gets afterwards.
KEY POINTS
Key points
- Test every board metric: does it describe risk, would a change trigger action, and can it be compared meaningfully?
- Ask what the leading indicators say about next year whenever a report shows a quiet period.
- Agree eight to twelve indicators, each with an owner and a written red, amber and green threshold.
- Require a one-page report that opens with what is good, what is worrying and what is needed.
- Ask what sits outside the denominator of every coverage percentage.
- Thank people for bad news so that future reports stay honest.
QUESTIONS
Common questions
- What cyber security metrics should a board see?
- A board should see a small, stable set of about eight to twelve indicators that describe risk rather than activity. Typical families are exposure, control coverage, response capability, people and culture, and third-party risk, plus a couple of performance measures such as roadmap progress. Each should have an owner, a threshold and a clear link to a risk in the register.
- What is the difference between a KRI and a KPI in cyber security?
- A key performance indicator (KPI) measures how well the security programme is being carried out, such as training completion or roadmap progress. A key risk indicator (KRI) measures how much risk the company is carrying against its risk appetite, such as critical systems without tested backups. Good performance can coexist with rising risk, so boards need both.
- What are leading and lagging indicators in cyber risk?
- Lagging indicators show what has already happened, such as the number and cost of incidents. Leading indicators show conditions that make future incidents more or less likely, such as time to fix critical weaknesses or days since the last successful restore test. A year without incidents can be luck, so leading indicators are more useful for steering.
- What should a one-page board cyber dashboard include?
- It should include a short plain-language headline saying whether risk is within appetite and whether a decision is needed, the agreed indicators with current value, threshold and trend, the three to five top risks with their business impact and response, and any decisions or requests for the board. Supporting detail can sit behind it, but the page must stand alone.
- Why can red, amber, green ratings be misleading?
- Traffic-light ratings mislead when a green average hides a serious red item underneath, when colours are chosen without written criteria and drift towards green, when items stay amber for many quarters until nobody notices, and when the absence of red is treated as success. Colours are useful only when earned by agreed thresholds and backed by visible numbers.
- How often should the board receive cyber security reports?
- For most mid-size companies, a sensible rhythm is a full quarterly report to the audit or risk committee and a report to the full board once or twice a year. Serious incidents or risk indicators crossing their thresholds should be reported between meetings, and the board should hold a deeper annual review that includes an independent view.