Patch Management Policy

Patch maintenance window policy

A maintenance window clause fixes when installs happen and when they are forced. Microsoft publishes its monthly security update on the second Tuesday: 8 December 2026, 12 January 2027, 9 February 2027. A quarterly window cannot meet a 14 day deadline, a monthly window usually can.

What the section must say

  • The standard window for each maintenance group: day, hours, time zone.
  • How far ahead the schedule is published.
  • That installation is forced after a grace period, and how.
  • Where reboots happen, and what is done for assets that cannot reboot.
  • How the window relates to the vendor's release rhythm.

NIST SP 800-40 Rev. 4 says routine patches should be installable with some flexibility, but installation should be forced after a grace period ends, either directly by triggering patch execution or indirectly by preventing network access for unpatched assets. Its inventory example of a mission restriction is an asset that can only be rebooted during a monthly maintenance outage.

The vendor rhythm to plan around

Microsoft Learn says the monthly security update is published on the second Tuesday of each month, typically at 10:00 AM Pacific Time; an optional non-security preview update comes in the fourth week; and out-of-band updates arrive as needed. Computed from that rule, the next release days are 8 December 2026, 12 January 2027 and 9 February 2027.

Arithmetic of the interval against the Cyber Essentials 14 day rule and the one-month PCI rule and the 30 day HIPAA proposal. Not a source figure.
Window frequencyLongest wait for an update released just after a windowMeets 14 day rule?Meets 30 day rule?
Weekly7 daysYesYes
Fortnightly14 daysOnly if the window falls inside the 14 daysYes
MonthlyUp to about 31 daysNo, for a patch released early in the cycle, unless a critical window is addedMarginal
QuarterlyUp to about 92 daysNoNo

The consequence is a rule written into the clause: the monthly window is the default, and class 1 to 3 items get an extra window so the deadline is met.

Sample wording

6.1 Standard windows: [group A: second Tuesday, 20:00 to 02:00 local]; [group B: Saturday following, 22:00 to 04:00]. The schedule for the next [3] months is published [5] working days before each window.

6.2 Class 1 to 3 patches that would miss their deadline before the next standard window are installed in an additional window agreed with the system owner within [2] working days.

6.3 If a patch is not installed by [14] days after the start of its window, installation is forced.

6.4 Reboots required to complete an install happen inside the same window. Assets that cannot be rebooted are recorded in Annex A with the compensating measures.

Common mistakes, and live patching

  • Quarterly windows. See the table: a 90 day gap cannot satisfy a 14 or 30 day deadline.
  • Treating live patching as a window. Red Hat says live kernel patches cover selected Important and Critical CVEs, are cumulative, are supported without extra cost for 6 months after the kernel errata release date, and exist for x86_64 and ppc64le only; Canonical says Livepatch covers critical and high kernel vulnerabilities between security maintenance windows. Both are vendor statements. Write the live patch as a stopgap, not a replacement for the reboot.
  • No grace period. NIST says patches must at some point be installed; clause 6.3 forces it.

See the dedicated page on systems that cannot reboot, the guide to how often to patch, then the next clause, reporting and metrics.

Sources

Last reviewed 19 Nov 2026