Patch Management Policy

Patch management report

A patch management report shows, per maintenance group and severity, the share patched by the deadline plus mean and median time to patch. NIST SP 800-40 Rev. 4 section 3.6 calls a plain percentage of patched vulnerabilities “not actionable.” Read 19 Nov 2026.

Why one percentage is not a report

NIST asks what “10 % of your assets were not being patched” would mean for risk: if those are the most important assets, “then not patching them might be a major problem,” and if they are the least important, it might be reasonable prioritization. Its fix is to weigh both sides: asset importance (low, moderate, high) and vulnerability importance (low, medium, high, critical), each defined by the organization (NIST SP 800-40 Rev. 4, section 3.6). Each cell of NIST's notional matrix holds three numbers: percent patched by the maintenance plan's deadline, average time, and median time. The matrix in the publication is labeled notional, so do not cite its figures as benchmarks.

Match the report to its reader

NIST says audiences differ: it names the chief executive officer as a possible reader of enterprise-level metrics and a Linux system administrator as a reader who needs platform-level ones. It also warns that low-level data decides quality: collecting software data by passive instead of authenticated scans “will generally underreport vulnerabilities and thus skew the higher-level metrics.” For compliance readers, the patch compliance rate page covers the single headline number and the proof for an auditor page covers evidence.

Report template

Patch report: [period]

Prepared on: [date]. Data as of: [date and time of last collection].

  1. Scope
  • Maintenance groups included, and the count of assets in each (the denominator).
  • Assets excluded and why (with exception IDs).
  1. Result by group and severity

For each maintenance group and each severity band:

  • Assets due in the period.
  • Percent patched by the deadline in the group's maintenance plan.
  • Mean and median days from release (or from the deadline start) to verified install.
  • Assets installed but awaiting restart, counted separately.
  1. Open items
  • Assets past deadline, owner, days late, risk response in force (mitigation, isolation, exception).
  • Every exception: ID, expiry date, last review date.
  1. Failures and rollbacks
  • Patches rolled back, cause, replacement date.
  1. Data quality
  • Percent of assets with inventory data older than [x] days.
  • Collection method (authenticated or passive).
  1. Decisions requested
  • Changes to deadlines, windows or tooling for the review.

Pick the deadline each row is measured against from your severity and patch window section, and state the clock start. The fields to keep behind each number are in the record list of verify.

Sources

Last reviewed 19 Nov 2026