Patch Management Policy

Patch management lifecycle

NIST SP 800-40 Rev. 4 (April 2022) defines enterprise patch management as identifying, prioritizing, acquiring, installing and verifying patches, updates and upgrades. That is five phases in a loop, and prioritizing is the second. The sequence repeats with every release, not once per year.

The five phases

The verbs are quoted from NIST SP 800-40 Rev. 4 (csrc.nist.gov publication page, read 19 Nov 2026); the process pages are this site's finer split of them.
PhaseWhat happensProcess page
1 IdentifyKnow the assets and learn of fixes for themInventory and monitor for releases
2 PrioritizeDecide how urgent each fix is for each groupAssess and prioritize
3 AcquireObtain the patch and test itAcquire and test
4 InstallApprove, schedule, deployApprove and schedule and deploy
5 VerifyConfirm the install, reportVerify and report

Why it is a loop

NIST treats patching as preventive maintenance: "patching should be viewed as a normal and necessary part of reliably achieving the organization's missions." A loop that has no step for the next cycle drifts; the last page of the process is the cycle check.

The install phase ends with a forced step. For routine patching NIST asks organizations to "offer flexibility with how soon routine patches are to be installed, while also forcing installation after a grace period has ended" (section 3.5.1). Forcing can be direct, like triggering patch execution, or indirect, like preventing network access for unpatched assets until they are patched. The grace period is therefore a dated field in the plan, and the force step is what turns a deadline into an outcome.

Four scenarios feed the same loop in NIST's model: routine patching, emergency patching, emergency mitigation and unpatchable assets. They share the five verbs but differ in timing, so a policy needs a plan for each.

Where the loop meets other functions

How patch management differs from the vulnerability side is in its own guide, and the glossary defines the terms used here.

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

what is the second phase of the patch management process lifecycle

Prioritizing. NIST SP 800-40 Rev. 4 lists the phases as identifying, prioritizing, acquiring, installing and verifying. Other sources split the phases differently, so name the model you are quoting.

patch management lifecycle

The lifecycle is the loop of identify, prioritize, acquire, install, verify, repeated with every release. Each phase has a page under the process.

Sources

Last reviewed 19 Nov 2026