What is patch management
Patch management is the process of identifying, prioritizing, acquiring, installing and verifying patches, updates and upgrades across an organization (NIST SP 800-40 Rev. 4, April 2022). On 19 Nov 2026 the CISA KEV catalog held 1,786 entries, which is why it needs to be a routine and not an event.
Definition and what it covers
The NIST definition covers patches, updates and upgrades, on operating systems, applications and firmware. Patching is, in NIST's words, a "normal and necessary part" of keeping systems reliable, not only a security step. In cyber security it is how a known flaw is removed.
Patch management software automates the install and reports on it; see automated patch management.
Scale as of 19 Nov 2026
| Measure | Value | Source and note |
|---|---|---|
| Entries in the CISA KEV catalog | 1,786 (version 2026.11.18) | CISA JSON feed, primary |
| KEV entries added by year | 186 in 2024, 245 in 2025, 302 in 2026 to 18 Nov | Our count from the same feed |
| KEV entries flagged known ransomware use | 361 | Our count from the same feed |
| CVE records published, 2025 | 49,972 | NVD API, sum of four date windows |
| CVE records published, 1 Jan to 18 Nov 2026 | 102,901 | NVD API; counts can change as NVD reprocesses |
Mandiant's analysis of 138 vulnerabilities exploited in the wild reported an average time to exploit of five days for 2023, against 32 days for 2021 and 2022 (third-party; published 15 Oct 2024). It excluded 15 outliers; without them the 2023 average is 47 days.
Why it is a policy matter
The deadline, the owner and the exceptions are decisions, and they are written once in a patch management policy rather than argued per patch. The steps are in the process, and the first thing most auditors ask for is the compliance record. Short answers to 17 common questions are collected in the FAQ.
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
what is patch management
Patch management is the process of identifying, prioritizing, acquiring, installing and verifying patches, updates and upgrades (NIST SP 800-40 Rev. 4). It is run as a routine cycle with a faster path for urgent fixes.
what is patch management in cyber security
It is how known software flaws are removed before they are used against you. The CISA KEV catalog held 1,786 exploited flaws on 19 Nov 2026.
what is patch management and why is it important
It is the routine of installing and verifying fixes, and it matters because attackers use known flaws: Mandiant measured an average of five days from disclosure to exploitation for 2023 (published 15 Oct 2024).
what is patch management in windows
On Windows it is built around the monthly security update, published on the second Tuesday, with optional preview updates in the fourth week and out-of-band releases as needed.
what is patch management in networking
It is the same cycle applied to routers, switches, firewalls and their firmware, usually with tighter maintenance windows. See network devices and firmware.
Sources
- NIST CSRC, SP 800-40 Rev. 4 publication page, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
- CISA, Known Exploited Vulnerabilities catalog JSON feed, read 19 Nov 2026
- NIST NVD API 2.0, CVE records by publication date, read 19 Nov 2026
- Google Cloud / Mandiant, Time-to-Exploit Trends 2023 (15 Oct 2024), read 19 Nov 2026
Last reviewed 19 Nov 2026