Patch Management Policy

Cloud patch management

Cloud virtual machines are patched by the customer unless a managed service does it. AWS Patch Manager runs by patch policy, maintenance window or on-demand Patch now, and Azure Update Manager uses maintenance configurations, up to 250 schedules per subscription per region. Read 19 Nov 2026.

Who patches what

NIST lists “the party who administrates the asset (for example IT department, third party, end user, vendor/manufacturer, shared responsibility model)” among the fields to inventory, and names moving to SaaS, where the provider patches, as a way to transfer risk (NIST SP 800-40 Rev. 4). For virtual machines the guest operating system is the customer's. The cloud provider's host maintenance is a separate matter and outside this page.

Guest operating system windows come from the Windows and Linux pages, and the process steps are in the overview.

Two orchestration models compared

Sources: AWS Systems Manager User Guide and Microsoft Learn, read 19 Nov 2026. Vendor descriptions of their own services.
FeatureAWS Systems Manager Patch ManagerAzure Update Manager
How patching is scheduledPatch policy in Quick Setup (single policy across accounts and Regions with AWS Organizations), maintenance window, or on-demand Patch nowMaintenance configurations: recurring schedules, daily, weekly or hourly
What decides the patchesPatch baselines, predefined or custom; default Windows Server and many Linux baselines wait 7 daysUpdate classifications chosen in the schedule
Status vocabularyINSTALLED, INSTALLED_PENDING_REBOOT, MISSING, FAILED and othersPer-machine results in the service
Documented limit worth planning aroundWindows Server default baselines include a 7-day auto-approval delay; a custom baseline is needed to install sooner250 schedules per subscription per region; 3,000 resource associations per schedule
HooksMaintenance window tasksPre-events and post-events; a failed pre-event must be cancelled by you or the run proceeds

Azure also states that VMs created from a supported Windows Server image have Automatic VM Guest Patching enabled by default, which means a policy must say whether that behavior is acceptable or turned off in favor of a customer-managed schedule. Machines in the same Azure availability set that patch in overlapping schedules may be skipped or fail if the window overruns; split them or lengthen the window.

Testing, rollback and evidence

Use tags or groups to run a canary group first, and take a snapshot or image before the install. The sources read here document the baselines and schedules, not rollback; the deploy step covers what to record. Evidence for an auditor: the baseline or configuration identifier and its date, the compliance report showing installed and missing patches, and the list of nodes with patches installed but not restarted (AWS counts that as compliant, so report it separately; see verify).

Questions

automated patch management aws

In AWS, automated patching is done by Systems Manager Patch Manager. A patch baseline decides which patches are approved, and a patch policy in Quick Setup, a maintenance window or a Patch now operation applies them. Default Windows Server baselines wait 7 days after release before approving.

aws patch management policy

An AWS patch management policy can be written as a Patch Manager patch policy: one Quick Setup configuration that defines schedules and baselines for an AWS Organizations scope. The written policy should also state which baseline is used and who owns exceptions.

Sources

Last reviewed 19 Nov 2026