Patch Management Policy

Patch deployment process

Patch deployment has five parts in NIST SP 800-40 Rev. 4: distribute, validate, install, change software state (such as a restart), and resolve issues. A rollback path is part of it; Intune can uninstall the latest quality update, while Windows Server hotpatches cannot roll back automatically. Read 19 Nov 2026.

The five parts

NIST section 2.3.2 says deployment varies with the type of software (firmware, operating system, application), the platform (IT, OT, IoT, mobile, cloud, VM, container), whether the asset is managed and where it sits, and limits such as bandwidth. Its steps are to distribute, validate again, install, change state, and resolve issues. “Resolve issues” includes side effects such as altering security settings, and can mean “uninstalling the patch, reverting to the previous version of the software, or restoring the software or asset from backups” (NIST SP 800-40 Rev. 4).

This step follows approve and schedule and is checked by verify; systems that cannot restart are in patching systems that cannot be rebooted.

Mechanisms and their rollback

Sources: Ubuntu Server documentation, Microsoft Learn, AWS documentation, read 19 Nov 2026.
MechanismHow it deploysRollback the documentation describes
Ubuntu unattended-upgradesInstalled by default; applies security updates without interaction; runs once per day by default; can reboot if an update requires itNone described on the page; logs are in /var/log/unattended-upgrades
Intune Windows update ringsClient-side deferral, restart and deadline settingsAdministrator can uninstall the latest quality update; Intune then pauses that update type on the ring, and when the pause ends the update reinstalls if still applicable. Feature update uninstall is limited to a 2 to 60 day period
Windows Server hotpatchIn-memory patches without restart, on a baseline that refreshes every three monthsNo automatic rollback; uninstall the update and install the last working baseline, which needs a restart
AWS Patch ManagerBaseline approves; install task or patch policy appliesNot described on the baseline pages; the compliance state reports failures (see verify)

Reinstall after rollback

The Intune detail is easy to miss: uninstalling a quality update also pauses that update type, and the pause lasts no more than 35 days. After it ends, devices reinstall the update if it still applies. A procedure that rolls back must therefore set a date by which a fixed patch or a mitigation replaces it, or the devices will take the faulty update again. Ubuntu's page also notes that adding a package repository does not make unattended-upgrades consider it for updates, so third-party repositories need their own entry.

The record to keep

  • Install logs per asset with the patch version before and after.
  • Restart status: installed but not restarted is a separate state (see verify).
  • Each rollback: who decided, what replaced the patch, and by when.
  • Assets that missed the window and the mechanism used to force them, per approve and schedule.

Questions

patch management rollback process

A rollback process names who may reverse a patch, how, and what replaces it. In Intune an administrator can uninstall the latest quality update, but updates of that type are then paused for up to 35 days and reinstall afterward if still applicable. Windows Server hotpatches have no automatic rollback and need a restart to undo.

Sources

Last reviewed 19 Nov 2026