Patch Management Policy

Automated patch management

Automated patch tools ship defaults that decide what is installed and when. On 19 Nov 2026 the AWS Windows Server baseline auto-approved Critical and Important updates 7 days after release, and Azure automatic guest patching installed within 30 days. CIS Controls v8 7.3 asks for monthly or faster.

Defaults stated in the vendors' documentation

Vendor documentation read 19 Nov 2026; statements are the vendor's. Other tools are in the directory.
Platform (alphabetical)Default behavior statedFigureSource
AWS Systems Manager, Debian Server baseline"Immediately approves all operating system security-related patches" of priority Required, Important, Standard, Optional or ExtraNo waitAWS predefined baselines
AWS Systems Manager, CentOS Stream baselineApproves "all updates 7 days after they become available, including nonsecurity updates"7 daysAWS predefined baselines
AWS Systems Manager, Windows Server baseline (AWS-DefaultPatchBaseline)Approves CriticalUpdates and SecurityUpdates with an MSRC severity of Critical or Important, "auto-approved 7 days after they are released or updated"7 daysAWS predefined baselines
Azure automatic VM guest patchingDownloads and applies patches classified Critical or Security; "installed within 30 days of the monthly patch releases", in off-peak hours of the VM's time zone, and only while the VM is running30 daysMicrosoft Learn
Azure VM patch mode when none is setWindows VMs default to Automatic Updates (AutomaticByOS); Linux VMs default to the image's own configuration (ImageDefault); neither supports availability-first patchingNot applicableMicrosoft Learn, automatic VM guest patching
Windows Autopatch, quality updatesMonthly security updates are approved automatically by default and other updates manually; the deferral for automatic approval allows 0 to 30 days, and Microsoft says to "keep quality update deferrals under three days"0 to 30 daysMicrosoft Learn

What the defaults do to a policy's windows

Three consequences follow from the table, and the arithmetic is this site's. First, a window of 14 days from release (Cyber Essentials v3.3) cannot be met by a tool whose stated behavior is installation within 30 days of release, so the schedule must be set shorter than the default. Second, the AWS Windows Server baseline names only Critical and Important MSRC severities; a policy that gives Moderate or Low items a window needs a second rule, because the default filter does not select them. Third, the Debian baseline approves with no wait while the Windows and CentOS baselines wait 7 days, so one policy window applied across mixed fleets starts its install clock from different points unless the approval delay is recorded for each baseline.

CIS Controls v8 safeguard 7.3 asks to "Perform operating system updates on enterprise assets through automated patch management on a monthly, or more frequent, basis" (CIS Controls v8). Monthly is a cadence, so the tool's own setting is the evidence for it. How the approval delay in an AWS baseline is bounded is in patch management practices.

What stays in the policy

  • Approval: who may change an approval delay, since the AWS value can be set anywhere from 0 to 360 days and a change moves every window downstream.
  • Rings: which groups are first. NIST SP 800-40 Rev. 4 section 3.5.1 calls the first subset "canaries", and Autopatch rings carry their own deferral.
  • Reboots: when a restart may be forced (see maintenance windows); Azure installs only while the VM is running, so a powered-off VM waits for its next assessment.
  • Failures: a failed install is a missed deadline until it is retried or recorded as an exception.
  • Scope: assets the tool does not manage, listed, because a compliance rate computed from the tool's list hides them.

A tool patches what it has a catalog for. Third-party titles, firmware and appliances usually need another route; see third-party and open source patching and network devices and firmware. Wording for automated approval belongs in the process step for approval.

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

automated patch management

It is software that detects missing patches and installs them on a schedule, in rings. CIS Controls v8 7.3 asks for it for operating systems monthly or more often.

automated patch management aws

In AWS Systems Manager Patch Manager, a patch baseline sets which patches are approved and after how many days. The predefined Windows Server baseline approves Critical and Important updates 7 days after release.

Sources

Last reviewed 19 Nov 2026