Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

How do we…

How do we choose which metrics the board sees?

6 decision pointsThe pack behind this answer: Board Cybersecurity Reporting

Add to board memo

The short answer

Recommendation
Let a measure reach the board only if it answers a question the board asks and carries a target, ideally with a tolerance, that the board has agreed. Start from a short list with the count of risks outside appetite first, name an owner for each, and ask the board to agree the set before the first report.
Reasoning
Every extra number competes for the same few minutes of attention, and a measure with no target cannot be judged good or bad. Some figures only look like assurance: attacks blocked, percentage of systems patched or alerts handled reward the wrong thing or cannot carry a meaningful target, so each is replaced by the board measure that answers the real question. Useful but detailed figures stay with the executive or the team that runs the control. The count of risks outside appetite comes first because every report opens by saying whether the organisation is within appetite.
Considerations
  • The eight board measures and the suggested limit of eight are the defaults in the CISO Times board reporting pack. Your board may agree a different set and limit. A small organisation usually needs five or six.
  • Set a tolerance as well as a target. Without one, any miss of the target reads as "Outside tolerance".
  • Who agrees the measures depends on how you are governed: the board or a risk committee it delegates to, the management board in a two-tier structure, or executive management where there is no board. NIS2 or DORA entities keep the risk count with tolerances approved in writing.
  • Most board measures can be improved by changing what is counted. Write each definition down, keep it stable, and restate the previous figure when a definition changes.

The decision, step by step

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

  • Start
  • Step
  • Decision
  • Outcome
  • Loop back

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. 19 steps.
  1. Start

    You have far more figures than the board can use

    Every extra number competes for the same few minutes of attention. A dashboard of twenty coloured tiles with no targets moves the discussion to the numbers and away from the risk. The aim is a handful of measures a director can judge at a glance.

    In the pack

  2. Step

    Write down the questions this board asks about cyber risk

    Start from the board's questions, not from what your tools can report. The pack's board measures answer eight: are we within appetite, are we closing the weaknesses attackers use, where have we knowingly accepted risk, have we been hurt, are key suppliers held to our standard, could we recover, is the funded plan on track, and are we trained.

    In the pack

  3. Step

    Start from the board measures, with risks outside appetite first

    The pack's eight board measures each answer one of those questions: risks outside appetite, critical exposure fixed on time, expired or high-risk exceptions, significant incidents and time to contain, critical suppliers assessed, critical services restored in tests, programme delivery, and board and staff training. A small organisation usually needs five or six.

    In the pack

  4. Decision

    Does the measure answer a question this board asks?

    Test each candidate, including those already in the report. 'The previous report always showed it' is not a reason. A measure that answers no board question takes attention from the ones that do.

    In the pack

  5. Decision

    Is it a figure that only looks like assurance?

    Some measures mislead at any level above the team: attacks blocked, phishing emails received, percentage of systems patched, security spend as a share of IT budget, percentage of controls compliant, external security ratings, alerts handled, tickets closed. They reward the wrong thing, cannot carry a meaningful target, or look like assurance when they are not.

    In the pack

  6. Outcome

    Drop it, and use the board measure it points to

    Replace each with the measure that answers the real question. Percentage patched becomes critical exposure fixed on time. Alerts handled becomes significant incidents and time to contain. Attacks blocked becomes threat context, in words, in the Exposure part. Security spend becomes a costed ask tied to the risk it reduces. If customers or insurers quote your external rating, know it and explain it in words when asked.

    In the pack

  7. Decision

    Would it explain a board measure when that measure moves?

    Some figures are useful to the executive or a risk committee but too detailed for every board report: phishing report rate, multi-factor authentication coverage, privileged access reviewed, overdue audit findings. The pack's catalogue marks them 'Executive only'. They earn a place when they explain why a board measure moved.

    In the pack

  8. Outcome

    Keep it below board level, for the appendix if asked

    Report it to the executive or risk committee. Bring it to the board only when it explains a board measure, and then in the appendix. If a gap it shows becomes a top risk, it reaches the board through the risk count and the Exposure part instead.

    In the pack

  9. Outcome

    Keep it on the operational dashboard

    Raw vulnerability counts, backup job success, endpoint coverage and leavers removed on time help the team that runs the control. They say little about risk to the organisation, so they stay with that team.

    In the pack

  10. Decision

    Can you set a target the board will agree?

    The target is the level you aim for. Without one a measure cannot be judged good or bad. Set a tolerance too: the worst level the board accepts before it must act, not just be told. Without a tolerance, any miss of the target reads as 'Outside tolerance'. If you cannot yet say, answer no.

    In the pack

  11. Outcome

    Hold it back until a target is set

    A measure with no target should not reach the board. If it matters, propose a target and tolerance for the board to agree, then add it. Until then it would appear as 'No target set' and invite 'so what?'.

    In the pack

  12. Step

    Name an owner by role, and the data source

    Someone must answer for each figure when the board asks. Name the role and the source in your organisation. Where a service provider supplies the figure, make it a reporting obligation in the contract and name an owner inside your organisation who checks it.

    In the pack

  13. Step

    Note how each measure can mislead, and fix its definition

    Most board measures can be improved by changing what is counted: rating fewer weaknesses Priority 1 or 2, re-scoring a risk, reclassifying an incident. Write the definition down, keep it stable, and report any change with the previous figure restated. Keep scan coverage in the appendix beside the fix rate.

    In the pack

  14. Decision

    Is the selection within the limit you set?

    More measures than the board can discuss is the commonest way reports stop being read. The pack suggests no more than eight; set your own limit. Five to eight measures with targets beat twenty tiles.

    In the pack

  15. Step

    Cut back to the measures that answer the board's questions

    Remove the measure whose question is already answered by another, or which the board has not asked about. It can still sit below board level.

    In the pack

  16. Decision

    Is the count of risks outside appetite in the selection?

    Every report opens by saying whether the organisation is within appetite, and this is the measure that answers it. It counts top risks above appetite and top risks past their own tolerance limit, from the whole risk register.

    In the pack

  17. Step

    Add it: the report cannot open without it

    If the board has not set an appetite, the measure cannot be calculated yet. Say so in the report and make agreeing an appetite the first ask.

    In the pack

  18. Step

    Ask the board to agree the measures, targets and tolerances

    Who agrees depends on how you are governed: the board, or a risk committee it has delegated to; the management board in a two-tier structure; executive management where there is no board. For NIS2 or DORA entities, the pack keeps the risk count with tolerances the board has approved in writing.

    In the pack

  19. Outcome

    Report the agreed set every cycle, and keep it for a year

    Copy the agreed measures into your data collection workbook. Do not drop measures that look bad or add new ones each quarter. Change the set only at the yearly review, and say what changed.

    In the pack

Practical checklist

  1. Write down the questions this board asks about cyber risk, and start from the board measures, with risks outside appetite first.
  2. Test each candidate against those questions, and replace figures that only look like assurance with the board measure each points to.
  3. Keep detailed figures below board level, for the appendix when they explain why a board measure moved.
  4. Set a target and a tolerance for each measure kept, or hold it back until you can.
  5. Name an owner by role and the data source for each measure. Where a provider supplies the figure, make it a contract obligation and name an owner inside your organisation who checks it.
  6. Trim the selection to your limit, and confirm the count of risks outside appetite is in it.
  7. Ask the board to agree the measures, targets and tolerances, then copy them into your data collection workbook.
  8. Keep the set for a year, and change it only at the yearly review, saying what changed.

Evidence to have ready

  • The agreed selection: each measure with the question it answers, its target, its tolerance, its owner and its data source.
  • The board's agreement of the measures, targets and tolerances.
  • The written definition of each measure, and any restated figures after a definition changed.
  • The yearly review of the selection, with what changed and why.

Assumptions

  • You have a risk register with top risks, and at least some of the sources the measures come from: a vulnerability tracker, an exception register, an incident log.
  • The eight board measures and the suggested limit of eight are the defaults in the CISO Times board reporting pack. Your board may agree a different set and limit. The test each measure must pass matters more than the list.

Not covered here