A board cyber risk report is a document that tells the board and senior executives what the organization is exposed to, how far it has progressed, and what decisions are needed. The board does not need technical detail, but it does need information it can use to decide on budget and risk. This article summarizes NACD and NIST guidance on what metrics to include, how to write them, and what to avoid.
What the board should receive
The NACD (the US association of corporate directors) states in its 2026 Director's Handbook on Cyber-Risk Oversight that boards should receive five things: a summary of posture and trends, top risk scenarios with estimated financial impact, incident and resilience information, regulatory compliance status, and investment and staffing indicators. The handbook recommends reporting at least quarterly, with extra reports after material incidents under escalation thresholds set in advance.
NIST CSF (the US cybersecurity risk framework) version 2.0 has a Govern function stating that senior leadership is responsible for cybersecurity risk under its leadership-responsibility requirement, and that results of risk management are reviewed to adjust strategy. A board report is how leaders carry out this duty in practice. For an overview of the framework see NIST CSF 2.0 implementation
Metrics to include
NACD gives six example metrics that boards often track, which each organization can adapt to its own business.
- Risk estimated in money: split by business unit. If money estimates are not yet possible, start with simple scoring from simple cyber risk assessment
- Number and severity of incidents: shown over time
- Mean time to detect and contain incidents: for the meaning of MTTD and MTTR see MTTD, MTTR and AI in the SOC
- Patch rate for critical systems: measure only the systems the business depends on most
- Third-party risk: how many critical suppliers the organization depends on
- Share of staff who finished security training: a view of awareness inside the organization
Our view: choose only 5-7 metrics per cycle. Each should have a current value, a trend against the last period, a target, an owner, and the decision being asked of the board. NACD also advises showing whether a metric is improving, stable or deteriorating rather than a single-date number, and using the same language and cycle as other company risks.
Metrics that tend to confuse a board
- Counting activity instead of outcomes: such as the number of alerts or blocked attacks, where a big number does not show that risk fell (our view)
- Jargon without explanation: the board should be able to read it and see the effect on money, operations or reputation, which matches NACD's advice to use financial and operational terms
- A single number with no comparison: nobody can tell whether it is better or worse, so no decision follows
Confusing
- Activity countssuch as alert counts
- Bare jargoneffect not clear
- One-off numberno comparison
Decision-ready
- Business outcomesmoney, operations, reputation
- Trend over periodsimproving, stable, worse
- Tied to risk appetitesame language as other risks
The US SEC cyber disclosure rules
The SEC (the US Securities and Exchange Commission) adopted rules on 26 July 2023 that require US-listed companies to report cyber incidents determined to be material on Form 8-K Item 1.05, within 4 business days of that determination, and to disclose each year on Form 10-K, under Regulation S-K Item 106, how the board oversees cyber risk and what role management plays. The rules apply only to companies under US SEC jurisdiction. We did not check Thai regulator requirements. This article is not legal advice, so ask legal counsel to confirm.
Where to start
- This week: ask the board or executives which decisions they need to make and what format they prefer
- This month: choose 5-7 metrics, set a data owner and measurement method for each, and make the first one-page report
- Every quarter: report metric trends, and define which events must reach the board immediately
- No risk data yet: start with our assessment