Give the board nine metrics, each computed from one source and read the same way every quarter | Compliance Automation Tools

[Skip to content](#main)
[Compliance Automation Tools](https://complianceautomationtools.com/)
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Menu
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Guide, read 13 Nov 2026

# Give the board nine metrics, each computed from one source and read the same way every quarter

**The short answer:** A board can read about nine compliance metrics if each has one data source and one definition. NIST SP 800-55 Vol. 1 (December 2024) says that with quantitative metrics, initially at least, less is often more, and the SEC's 2023 rule requires annual reporting on board oversight of cyber risk.

[Framework Coverage Matrix](https://complianceautomationtools.com/matrix/) | [All guides](https://complianceautomationtools.com/guides/)

## Why nine and not ninety

A board reads a few pages per meeting. The metrics page has to fit on one. NIST SP 800-55 Vol. 1, Measurement Guide for Information Security (December 2024, replacing Rev. 1 of 16 July 2008), is direct about this: it warns that poorly selected quantitative metrics can undermine the quality of reporting and erode confidence, and that with quantitative metrics, initially at least, less is often more. Its test for a metric is whether the data point directly illustrates the performance of a valid control or tracks the presence of a material risk to the organization's objective. If not, leave it out.

The same document splits measures into four types: implementation (are controls in place), effectiveness (are they working), efficiency (how fast do they give feedback and how quickly are issues addressed) and impact. Pick across the types. Nine metrics that all count implementation tell the board nothing about results.

Keep definitions fixed. NIST notes that keeping metrics consistent over time lets an organization see trends and expected ranges. Changing a definition mid-year resets the trend, so change it only at the start of a fiscal year and say so on the page.

## The nine metrics and what each is computed from

Each metric below has one numerator, one denominator and one system of record. If you cannot name the system of record, do not report the metric yet. The table is the page to give a board.

Every metric is a count or a percentage with a date. Show the current quarter, the previous quarter and the target. Do not show a color without the number behind it.

| Metric | Computed from | Type (SP 800-55) | Watch for |
|---|---|---|---|
| 1. Control pass rate | Controls with a passing latest test divided by controls in scope | Effectiveness | Untested controls counted as passed |
| 2. Controls tested on schedule | Tests completed by due date divided by tests due | Implementation | Tests re-dated after the fact |
| 3. Median days to remediate a failed control | Fail date to pass date, from the ticket system | Efficiency | Closing tickets without a re-test |
| 4. Overdue exceptions | Open exceptions past expiry, count and share of all open | Effectiveness | Renewal without a new approval |
| 5. Vendors past review date | Tier 1 and 2 vendors past due divided by vendors in tier | Implementation | Vendors missing from the register |
| 6. Evidence age | Median days since last evidence collection, by control family | Efficiency | Auto-refreshed timestamps with no new content |
| 7. Open audit findings | Count by severity, with age in days | Effectiveness | Findings closed by changing the finding |
| 8. Open risks above appetite | Register rows with exposure over the threshold, count | Impact | Scores revised without reasons |
| 9. Access reviews completed | Reviews finished on time divided by reviews due | Implementation | Rubber-stamp approvals |

## Reading each metric

Control pass rate is the headline, but it is only honest when the denominator includes every control in scope, including those not yet tested. Report the untested count beside it. A pass rate of 96 percent with 30 untested controls is not 96 percent.

Time to remediate is the efficiency metric NIST describes: the speed at which issues are addressed. Use the median, not the average, since one long-running item will distort the average. Report the oldest open item too.

Overdue exceptions and vendors past review date are the two metrics that show whether the program runs between audits. Both should be at zero or near it. Their definitions come from [policy exceptions](https://complianceautomationtools.com/guides/policy-exceptions/) and [vendor risk at scale](https://complianceautomationtools.com/guides/vendor-risk-at-scale/).

Evidence age tells you how stale your proof is. For a SOC 2 or ISO audit, an auditor will ask for evidence from within the period. For example, a median of 12 days for access evidence is fine; a median of 200 is a finding waiting to be written. See [evidence that survives an audit](https://complianceautomationtools.com/guides/evidence-that-survives-an-audit/).

Open audit findings give the outside view. Show severity and age, and name the owner role. Open risks above appetite connect the page to the [risk register](https://complianceautomationtools.com/guides/risk-register-basics/). If a metric has no owner, it does not go on the page.

## What the SEC rule asks of boards

For companies that file with the SEC, board oversight is a reporting item. The SEC press release of 26 July 2023 on its cybersecurity rules says registrants must describe the board of directors' oversight of risks from cybersecurity threats, and describe management's role and expertise in assessing and managing them, in the annual report on Form 10-K. It also says an Item 1.05 Form 8-K is generally due four business days after a registrant determines a cybersecurity incident is material.

The rule does not prescribe metrics. It does mean the sentences in your 10-K should match what the board actually sees. If the filing says the board receives quarterly reports, the metrics page should exist and be dated.

NIST CSF 2.0 supports this with its Oversight category, GV.OV. GV.OV-03 says organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed. A dated metrics page, with the board's questions recorded in the minutes, is the evidence for that outcome.

## What to avoid

Avoid vanity counts. Number of alerts, number of policies, number of controls and number of integrations are activity, not results. NIST gives the better pattern: for training, report completion rates and quiz results instead of marking participation as low, medium or high.

Avoid single composite scores. A blended score of 87 hides which part fell. Avoid metrics that reward the wrong behavior: a short time to close findings can be reached by closing them without fixing them. Pair it with a re-test rate.

Avoid red, amber and green without thresholds written beside them. Avoid metrics with no target. A board reads a number against a target, and a number with no target invites a story.

Last, do not hide the bad quarter. A board that learns about an overdue Tier 1 vendor from an auditor will stop trusting the page. Show the miss, the cause and the date it will be fixed.

## Where this shows up in the index

For DORA, Secureframe leads at 7.55 in the framework view, and Scytale is 4th at 7.08. The [DORA page](https://complianceautomationtools.com/frameworks/dora/) sets out what the regulation asks a board to oversee.

## Sources

- [csrc.nist.gov/pubs/sp/800/55/v1/final](https://csrc.nist.gov/pubs/sp/800/55/v1/final), read 12 Nov 2026
- [nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-55v1.pdf](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-55v1.pdf), read 12 Nov 2026
- [nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf), read 12 Nov 2026
- [sec.gov/newsroom/press-releases/2023-139](https://www.sec.gov/newsroom/press-releases/2023-139), read 12 Nov 2026
Last reviewed 13 Nov 2026.

- [Matrix](https://complianceautomationtools.com/matrix/)
- [Integrations](https://complianceautomationtools.com/integrations/)
- [Datasets](https://complianceautomationtools.com/datasets/)
- [News](https://complianceautomationtools.com/news/)
- [FAQ](https://complianceautomationtools.com/faq/)
- [About](https://complianceautomationtools.com/about/)
- [Editorial policy](https://complianceautomationtools.com/editorial-policy/)
- [Corrections](https://complianceautomationtools.com/corrections/)
- [Contact](https://complianceautomationtools.com/contact/)
- [Privacy](https://complianceautomationtools.com/privacy/)
- [Terms](https://complianceautomationtools.com/terms/)
- [llms.txt](https://complianceautomationtools.com/llms.txt)
- [llms-full.txt](https://complianceautomationtools.com/llms-full.txt)
- [Sitemap](https://complianceautomationtools.com/sitemap.xml)
- [RSS](https://complianceautomationtools.com/feed.xml)

Compliance Automation Tools. Every platform fact carries its source and read date. Read 13 Nov 2026.

Canonical: https://complianceautomationtools.com/guides/continuous-compliance-metrics-for-the-board/
