Patch management process
The patch management process has nine steps: inventory, monitor for releases, assess and prioritize, acquire and test, approve and schedule, deploy, verify, report, and review the cycle. They follow NIST SP 800-40 Rev. 4 (April 2022), which defines the work as identifying, prioritizing, acquiring, installing and verifying patches. Read 19 Nov 2026.
The nine steps
NIST defines enterprise patch management as “the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization” (NIST SP 800-40 Rev. 4). This site splits that definition into nine steps so that each one can be owned, timed and audited on its own. Each step has its own page with inputs, actions, outputs and the record to keep.
- Inventory: list every asset with its software, its owner and its outage limits. Output: one record per asset that a later step can filter by maintenance group.
- Monitor for releases: subscribe to each vendor's advisory channel and to the CISA Known Exploited Vulnerabilities feed. Output: a dated list of releases that touch assets you own.
- Assess and prioritize: decide for each release which risk response applies and how fast. Output: a response and a deadline per asset group.
- Acquire and test: validate the patch, then try it on canary assets. Output: a pass or fail with the evidence.
- Approve and schedule: get change approval and fix the window, including the grace period after which installation is forced. Output: an approved change with a window.
- Deploy: distribute, install and restart in stages, with a rollback path. Output: install logs per asset.
- Verify: confirm the patch is installed and in effect, then keep checking that it stays installed. Output: a status per asset that separates installed from effective.
- Report: turn asset-level status into measures per maintenance group and deadline. Output: a dated report with the denominator stated.
- Review the cycle: review exceptions, deadlines and tooling, and feed changes back to the policy. Output: a dated review with decisions.
How the steps map to NIST SP 800-40 Rev. 4
| Step | Where NIST SP 800-40 Rev. 4 covers it | What the source says in short |
|---|---|---|
| 1 Inventory | Section 3.2 | Keep inventories current by automation; scan-based monthly or quarterly updates “should no longer be used” |
| 2 Monitor | Section 2.2, item 1 | Know when new vulnerabilities affect assets, for example through vendor feeds and the NVD |
| 3 Assess and prioritize | Sections 2.3.1 and 3.3 | Four risk responses: accept, mitigate, transfer, avoid; four scenarios |
| 4 Acquire and test | Sections 2.3.1 and 3.5.1 | Validate authenticity and integrity; canary assets act as the test |
| 5 Approve and schedule | Sections 2.3.1 and 3.5.1 | Schedule through change management; force installation after a grace period |
| 6 Deploy | Section 2.3.2 | Distribute, validate, install, change state (restart), resolve issues |
| 7 Verify | Sections 2.3.3 and 2.3.4 | Confirm the patch took effect; monitor that it stays installed |
| 8 Report | Section 3.6 | Metrics must weigh asset and vulnerability importance |
| 9 Review | Sections 3.5.4 and 3.5.5 | Re-evaluate alternatives to patching; review every exception regularly |
What the policy fixes for the whole process
NIST says routine patching “is often postponed and neglected,” which “provides many additional windows of opportunity for attackers” (NIST SP 800-40 Rev. 4, section 3.3). A policy answers that by naming an owner and a clock for every step above, not only for deployment. The clock values per framework are on the patch window table; the policy text for them is in severity and patch windows.
The process also differs by asset. A laptop fleet and a medical device share the nine steps but not the windows, so the eleven asset class pages give the vendor rhythm and the usual constraints for each class. Short answers to common questions about these steps are in the FAQ.
Questions
patch management process steps
Nine steps on this site: inventory, monitor for releases, assess and prioritize, acquire and test, approve and schedule, deploy, verify, report, and review the cycle. NIST SP 800-40 Rev. 4 groups the same work into identifying, prioritizing, acquiring, installing and verifying patches.
what is the second phase of the patch management process lifecycle
In NIST SP 800-40 Rev. 4, section 2.2, the second item of the life cycle is to plan the risk response: assess the risk, choose accept, mitigate, transfer or avoid, and decide how to carry it out. In this site's nine steps that work is step 3, assess and prioritize.
patch management process flow
The flow is linear with one loop: steps 1 to 8 run in order for each release, and step 9 feeds exceptions and deadline changes back into step 1 and the policy. NIST adds that verification should continue after install, to detect a patch being uninstalled.
Sources
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
- NIST CSRC, SP 800-40 Rev. 4 publication page, read 19 Nov 2026
Last reviewed 19 Nov 2026