Guide, read 12 Nov 2026

# Give the board one measure, its trend and three decisions each quarter

**The short answer:** A quarterly CTEM board report needs one page: one measure, such as validated exposures on the top three business services, its trend over four quarters, and three decisions the board must make. NYDFS Part 500.4(b) already requires an annual written CISO report; the SEC cybersecurity reporting rule (26 Jul 2023) asks about board oversight.

[Stage Coverage Map](https://ctemvendors.com/stage-coverage-map/) | [All guides](https://ctemvendors.com/guides/)

## Boards already receive a legal minimum

Several rules now set what a board must hear about cyber risk. Under New York's Part 500.4(b), the CISO of each covered entity must report in writing at least annually to the senior governing body, covering among other things material cybersecurity risks, the overall effectiveness of the cybersecurity program and plans for remediating material inadequacies. NYDFS confirms in its FAQs that an authorized board committee can receive it.

The SEC cybersecurity reporting rule, adopted 26 Jul 2023, requires registrants to describe in the annual Form 10-K their processes for assessing, identifying and managing material cybersecurity risks, the board's oversight of those risks, and management's role, starting with fiscal years ending on or after 15 Dec 2023. In the EU, NIS2 introduces accountability of top management for non-compliance with cybersecurity risk-management measures, which the European Commission says brings cybersecurity to the attention of the boardroom.

A quarterly CTEM report does not replace those documents. It feeds them: four quarters of a consistent measure is the evidence behind any annual statement about program effectiveness.

## Pick one measure and keep it

Boards follow one number well and five numbers poorly. The best candidate from a CTEM program is the count of validated exposures on the company's top three business services: paths that testing proved usable this quarter, reported with the number of items tested. It is concrete, it falls when fixes work, and it cannot be gamed by turning off a scanner. Directors can also check it against what they know about the business: if the payments service shows the most proven paths, they know where money and attention should go.

An alternative for a mature program is the median days to mitigate proven exposures. Either works. Do not switch between them from quarter to quarter, and do not replace the measure with a composite risk score; the [measurement guide](https://ctemvendors.com/guides/measuring-a-ctem-program/) explains why.

## Show the trend across four quarters

A single quarter's number invites the wrong question: is that good? A trend across four quarters answers it. Plot the measure for each service, mark when scope or testing changed, and mark major external events such as a KEV listing for a product the company runs. CISA's catalog held 1,779 entries in version 2026.11.10, so expect some quarters to rise for reasons outside the program.

Add one line of context per quarter, in business terms: which service, which kind of exposure, what was done. 'Two proven paths to the payments database from the internet, both closed within 9 days' is a board sentence. 'Critical vulnerabilities down 14 percent' is not.

Keep the scope of the measure fixed while the trend runs. If the program adds a fourth service, show it as a new line rather than folding it into the old total, or the trend will jump for reasons that have nothing to do with exposure.

## Ask for three decisions

A board report without a decision is a briefing. End each quarter with three decisions, each with an owner, a cost and a date. Typical decisions in a CTEM program are below.

- Accept, fund or reject a fix that needs money or downtime: a platform upgrade, a legacy system retirement, a network redesign.
- Approve an accepted risk on a proven exposure past its first expiry, with a named executive owner.
- Choose the next scope: which business service the program covers next quarter.
- Approve or defer a change in third-party terms where a supplier's exposure sits on a proven path.
- Set the tolerance: how many days a proven internet-facing path may stay open before it escalates to the board.

## A one-page template

The page below fits one slide. The measure and trend take the top half; the decisions take the bottom.

| Block | Content | Source in the program |
|---|---|---|
| Measure | Validated exposures on top three services this quarter, with items tested | Validation results |
| Trend | Same measure, last four quarters, with scope changes marked | Cycle records |
| Context | One sentence per service in business terms | Exposure team summary |
| Decision 1 | Fund, accept or reject a costed fix | Mobilization record |
| Decision 2 | Approve or end an accepted risk | Exception register |
| Decision 3 | Next scope or tolerance change | Scoping plan |

## Leave the scanner output out

Leave out total vulnerability counts, average severity, ATT&CK heatmaps and vendor dashboards. Each needs a security specialist to read and none of them leads to a decision. Keep them in an appendix for the audit committee if asked.

Leave out technique names and tool names in the main page as well. Directors need to know which business service is exposed, how that changed and what they are being asked to decide. The validation evidence behind each number stays with the program, ready for audit.

Leave out Gartner's forecast that continuous exposure management programs make a breach three times less likely by 2026. It is an analyst prediction from August 2023, not a measure of this company, and quoting it invites the question of why the company was breached anyway.

## Tie the quarterly page to the annual report

Once a year, collect the four quarterly pages into the written report the CISO already owes the board or its committee. The four trends answer the question Part 500.4(b) asks about overall program effectiveness, and the decision log shows the board's oversight, which is what the SEC rule asks registrants to describe. Regulated companies should read the [regulated companies guide](https://ctemvendors.com/guides/ctem-for-regulated-companies/) for the evidence each rule expects, and the [roles guide](https://ctemvendors.com/guides/ctem-roles-and-ownership/) for who prepares each block.

Keep the decision log from every quarter: what was asked, what the board decided, and what happened next. After a year, that log is the most direct record of oversight a company can produce.

## Sources

- [https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf](https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf), read 12 Nov 2026
- [https://www.dfs.ny.gov/cybersecurity/faqs](https://www.dfs.ny.gov/cybersecurity/faqs), read 12 Nov 2026
- [https://www.sec.gov/newsroom/press-releases/2023-139](https://www.sec.gov/newsroom/press-releases/2023-139), read 12 Nov 2026
- [https://digital-strategy.ec.europa.eu/en/policies/nis2-directive](https://digital-strategy.ec.europa.eu/en/policies/nis2-directive), read 12 Nov 2026
- [https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read 12 Nov 2026
- [https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes](https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/guides/reporting-exposure-to-a-board/
