Patch Management Policy

How to verify patches are installed

Verify in two ways: the patch is installed and it has taken effect, then monitor that it stays installed. In AWS Patch Manager a node with a patch installed but not yet restarted is INSTALLED_PENDING_REBOOT, which AWS classes as Compliant. A policy should count it separately. Read 19 Nov 2026.

Installed is not the same as effective

NIST defines verification as confirming “that the patch is installed and has taken effect” and says that automated means “are generally needed to achieve verification at scale” (NIST SP 800-40 Rev. 4, sections 2.2 and 2.3.3). The gap between the two is the restart. Patching a service or kernel often changes nothing in the running process until it restarts, which is why deployment records the restart status.

Status values from a real tool

AWS Systems Manager Patch Manager reports a state for each patch on each node. The mapping below is from the vendor's documentation and shows how a tool's word “compliant” can hide an open exposure.

Source: AWS Systems Manager User Guide, patch compliance states (non-Debian, non-Ubuntu table), read 19 Nov 2026.
Patch stateMeaning in AWS documentationCompliance value AWS assigns
INSTALLEDIn the baseline and installedCompliant
INSTALLED_OTHERInstalled but not in or not approved by the baselineCompliant
INSTALLED_PENDING_REBOOTInstalled, but the node has not been rebooted since; AWS says it does not mean a reboot is requiredCompliant
INSTALLED_REJECTEDInstalled but on the rejected listNon-Compliant
MISSINGApproved in the baseline but not installedNon-Compliant
FAILEDApproved but could not be installedNon-Compliant

AWS's own caution is that the pending-reboot state does not by itself mean a reboot is required, only that the node has not rebooted since the install. A policy can still demand a restart check where the vendor says the fix needs one; the Windows and Linux pages note where.

Do not use history as proof

Microsoft's Intune documentation says that after a quality update is rolled back, “device users continue to see the update listed in Windows settings > Updates > Update History.” A listing in an update history screen is therefore weak evidence; query the installed build or package version instead, and compare it with the version the patch should produce.

Keep checking

NIST's last lifecycle phase monitors that the patch is “still installed”: not uninstalled by a user or an attacker, not replaced by an unpatched version restored from backup, and not reset to a vulnerable factory-default state. A monthly re-check of a sample, plus a check after every restore from backup, covers all three.

The record to keep

  • The verification query and its result per asset, with the date.
  • Counts by state, with pending-restart assets listed separately.
  • Restores from backup and factory resets, each followed by a re-check.

Sources

Last reviewed 19 Nov 2026