# Patch Management Metrics: What the Policy Should Report

Canonical: https://patchmanagementpolicy.com/policy-sections/reporting-and-metrics/
Last reviewed: 19 Nov 2026

## Patch management metrics

A reporting clause should ask for a matrix, not one percentage. NIST SP 800-40 Rev. 4 section 3.6 shows the share patched by deadline, mean days and median days for each pairing of asset importance and vulnerability importance, and calls a single organization-wide percentage not actionable.

### What the section must say

- Who receives the report, how often, and by what date.
- The figures: share patched by deadline, mean days, median days, split by asset importance and vulnerability class.
- Open exceptions with age; assets with no owner.
- Where the evidence behind each figure is stored and for how long.

NIST's argument is concrete: if you were told 10 percent of assets were not being patched, what would that mean for risk? If they are the most important assets it may be a major problem; if the least important it may reflect sensible prioritization. A metric that counts all vulnerabilities and the percentage patched is, in NIST's words, not actionable.

### NIST's notional matrix, with its values

| Vulnerability importance | Low asset importance | Moderate asset importance | High asset importance |
|---|---|---|---|
| Low | 64.7% by deadline; mean 80.4 days; median 75.2 | 72.4%; 34.7; 33.7 | 85.0%; 14.6; 8.1 |
| Medium | 66.5%; 75.1; 70.7 | 68.7%; 33.2; 31.6 | 71.4%; 12.9; 10.5 |
| High | 68.6%; 62.1; 58.0 | 78.8%; 26.8; 22.1 | 85.5%; 8.8; 8.1 |
| Critical | 81.4%; 44.4; 41.3 | 92.3%; 21.2; 23.9 | 95.2%; 5.2; 5.1 |

Table 1, Vulnerability Mitigation Time Summary Matrix, NIST SP 800-40 Rev. 4. The values are NIST's notional example, not measurements of any organization. Each cell: share patched by deadline, mean days, median days.

NIST also says each audience needs its own cut, for instance a Linux administrator's view of Linux patching or a business unit's comparison with others, and that the low-level data should be kept accurate because errors flow into the enterprise-level figures. It adds that collecting data by less accurate methods tends to underreport vulnerabilities and skew the higher-level metrics.

### Sample wording

```text
8.1 By the [5th] working day after each cycle, the patch coordinator sends the executive sponsor a report showing, for each pairing of asset importance (high, moderate, low) and vulnerability class (1 to 5): the share of assets patched by their deadline, the mean days to patch and the median days to patch.
8.2 The report lists open exceptions with their age, assets without an owner, and windows missed with the cause.
8.3 The board receives the high-importance column for classes 1 and 2 each [quarter]. Group owners receive their own group's cells.
8.4 Data for each figure is exportable from [system] and kept for [period].
```

### Common mistakes, and the review cadence in CIS

- **One percentage.** See NIST's 10 percent example above.
- **Mean without median.** A few very old items distort a mean; NIST's matrix shows both.
- **No review of the strategy.** CIS Controls v8 safeguard 7.2 asks for a risk-based remediation strategy with monthly or more frequent reviews; the cadence is for the strategy, not for installing patches.

Compliance rates for auditors are covered in [patch compliance rate](https://patchmanagementpolicy.com/guides/patch-compliance-rate/). The next clause is [review and approval](https://patchmanagementpolicy.com/policy-sections/review-and-approval/); the report as a process step is [report](https://patchmanagementpolicy.com/process/report/).

### Sources

- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026
- [CIS Controls v8 guide (August 2023), Control 7, safeguards 7.1 to 7.7](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [Patch Compliance Rate: Formula, Denominators, Clocks](https://patchmanagementpolicy.com/guides/patch-compliance-rate/)
- [Patch Management Policy Approval and Revision](https://patchmanagementpolicy.com/policy-sections/review-and-approval/)
- [Step 8: Patch Management Report Contents](https://patchmanagementpolicy.com/process/report/)
