Patch Management Policy

What is patch compliance rate

Patch compliance rate is the share of in-scope assets that received a required patch within its deadline: assets on time divided by assets due. In the clauses read on 19 Nov 2026, none sets a target percentage, so the number is yours to define. Clock starts differ: release, discovery or KEV listing.

Formula and a worked example

Rate = assets patched within the deadline / assets whose deadline has passed. Example, invented for illustration and not data: 1,000 assets are due for a critical fix; 940 installed within 14 days; the rate is 94.0 percent. The 60 that are late are listed by group, not averaged away.

Variants defined by this site; no framework read on 19 Nov 2026 defines them.
VariantNumeratorDenominatorUse
Within-window rateInstalled by the deadlineAssets whose deadline passedProves the policy deadline was met
Current-state rateInstalled today, any dateAll in-scope assetsShows exposure now
Exception-adjusted rateWithin window plus documented exceptionsAssets dueShows how much of the gap is owned; report it beside the first, never instead

Why two organizations cannot compare rates

The deadline differs by source and so does the clock. Cyber Essentials v3.3 counts "within 14 days of release". FedRAMP's legacy page counts 30 days for critical and high "of discovery". BOD 26-04 starts at the KEV listing or the agency's identification, whichever comes first. The HIPAA proposal counts from "identifying the need to patch". A rate is only meaningful with the deadline and the clock stated next to it.

Scope moves it as well: the denominator must say whether it includes assets outside the inventory, which by definition cannot be counted; see asset inventory requirement.

Where to publish it

Put the formula, the clock and the severity in the policy's reporting clause (reporting and metrics). Keep the supporting records described in proving patch compliance to an auditor. Microsoft's Autopatch overview describes a view of managed devices that are "Not up to date", which is a current-state view in this table's terms.

Dashboards are the tool's own; their wording is recorded per tool in the directory.

4.3 Patch windows

SeverityWindow3143090180 days
1. Known exploited, internet-facing3 calendar daysApplies to: Systems reachable from the internet
1. Known exploited, other14 calendar daysApplies to: All other systems
2. Critical14 calendar days
3. High30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials]
4. Medium90 calendar days
5. Low180 calendar days
Routine baselineEvery month, or more oftenApplies to: Operating system and application updates

No framework selected: every window above is the site template's suggested default, and the clock starts as this section states.

Questions

what is patch compliance rate

It is the share of in-scope assets patched within the deadline, assets on time divided by assets due. No clause read on 19 Nov 2026 sets a target percentage.

what is patch compliance

Patch compliance is whether assets have the required patches within the deadline the policy or a framework sets. The measure is the patch compliance rate.

Sources

Last reviewed 19 Nov 2026