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
| Question | Patch management | Vulnerability management |
|---|---|---|
| Starting point | A vendor releases a fix | A weakness is found or reported |
| Main output | Fix installed and verified on named assets | A decision per finding: remediate, or another response |
| Typical cadence in the clauses read | Monthly 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 when | A patch exists and is not installed in time | A 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
| Severity | Window3143090180 days |
|---|---|
| 1. Known exploited, internet-facing | 3 calendar daysApplies to: Systems reachable from the internet |
| 1. Known exploited, other | 14 calendar daysApplies to: All other systems |
| 2. Critical | 14 calendar days |
| 3. High | 30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials] |
| 4. Medium | 90 calendar days |
| 5. Low | 180 calendar days |
| Routine baseline | Every 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
- NIST SP 800-218 v1.1, Secure Software Development Framework, PW.4.4, RV.1.1, RV.2.2, read 19 Nov 2026
- CIS Controls v8 (August 2023 guide), Control 7 safeguards, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
- CISA, BOD 26-04, Prioritizing Security Updates Based on Risk, read 19 Nov 2026
- NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management, read 19 Nov 2026
Last reviewed 19 Nov 2026