Patch Management Policy

Patch management vs vulnerability management

Patch management installs fixes; vulnerability management finds weaknesses and chooses the response, of which a patch is one. NIST SP 800-218 RV.2.2 asks for a decision whether each vulnerability "will be remediated or if the risk will be addressed through other means". Patching carries out the first branch.

The two side by side

Comparison from the clauses linked below, read 19 Nov 2026.
QuestionPatch managementVulnerability management
Starting pointA vendor releases a fixA weakness is found or reported
Main outputFix installed and verified on named assetsA decision per finding: remediate, or another response
Typical cadence in the clauses readMonthly or more frequent (CIS 7.3, 7.4); 14 days of release (Cyber Essentials v3.3)Internal scans quarterly or more frequent (CIS 7.5); externally exposed monthly or more frequent (7.6)
Defined by NIST as"identifying, prioritizing, acquiring, installing, and verifying the installation of patches" (SP 800-40 Rev. 4)Gather information on vulnerabilities, then "make a risk-based decision" (SP 800-218 RV.1.1, RV.2.2)
Fails whenA patch exists and is not installed in timeA finding is never triaged, or has no patch

CIS Controls v8 shows how they join: safeguards 7.3 and 7.4 (automated patching of operating systems and applications) sit in the same control as 7.1 (a documented vulnerability management process) and 7.5 to 7.7 (scans and remediation).

Where one hands to the other

Vulnerability management prioritizes. BOD 26-04 (10 Jun 2026) shows an example of the hand-off: four inputs (publicly exposed, in the KEV catalog, automatable, technical impact) select one of 3, 14 or 60 days or a fix at upgrade. The patch process then needs to meet that date. NIST SP 800-40 Rev. 4 calls patching one way of the risk response "mitigate", beside accept, transfer and avoid, which is the point at which the two meet.

A patch policy that reads "critical within 14 days" has already assumed the severity call. Naming who makes it (the scanner, the vendor's word, or a human) is a clause in its own right; see the severity and patch window section.

What this site does not cover

Building a vulnerability management program is not covered here. For the patch side only, read what is patch management and the patch management program guide.

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

patch management vs vulnerability management

Patch management installs and verifies fixes; vulnerability management finds weaknesses and picks a response, and a patch is only one response. CIS Controls v8 puts both under Control 7, with different cadences.

what is vulnerability and patch management

It is the pair of functions: finding and triaging weaknesses, then installing the fixes. The comparison guide sets out where each starts and stops.

Sources

Last reviewed 19 Nov 2026