How often should you perform patch management
Patch on a fixed monthly cycle and meet a separate deadline for urgent fixes. CIS Controls v8 asks for operating system and application updates monthly or more often; Cyber Essentials v3.3 asks for critical or high fixes within 14 days of release; BOD 26-04 sets 3, 14 or 60 days. Read 19 Nov 2026.
Cadence by source
| Source | Cadence or deadline | Clock starts |
|---|---|---|
| CIS Controls v8, 7.3 and 7.4 | Monthly, or more frequent | Not stated |
| UK Cyber Essentials v3.3 | 14 days, for critical or high risk fixes | Release |
| PCI DSS v4.0.1 (PCI SSC FAQ 1597) | One month, critical vulnerabilities | Release |
| CISA BOD 26-04 | 3, 14 or 60 days, or fix on system upgrade | KEV listing or agency identification, whichever is first |
| FedRAMP legacy POA&M page | 30 days critical and high, 90 moderate, 180 low | Discovery |
| NIST SP 800-40 Rev. 4 | No number; emergency patching "in the following hours or days" | Per plan |
The monthly rhythm
Microsoft says the monthly security update is published on the second Tuesday, "typically at 10:00 AM Pacific Time". From that rule the next dates are 8 Dec 2026, 12 Jan 2027 and 9 Feb 2027; 10 Nov 2026 matched the release date in Microsoft's security update data. A 14-day window that starts at release therefore ends on 22 Dec 2026 for the December cycle.
Size varies and counting it takes care. Microsoft's November 2026 security update document lists 1,791 CVE entries, of which 762 list a Windows product (counted from the CVRF document on 19 Nov 2026). It spans more than Windows, so 1,791 is not the Windows cycle's size.
Turning it into a rule
- Fix one monthly maintenance window per group; see maintenance windows.
- Set a separate, shorter deadline for critical and high fixes and name the clock start.
- Write that a KEV listing or a vendor's out-of-band release is handled under the emergency clause, not the monthly cycle.
- Report misses by group, as in patch compliance rate.
The dates above are also kept on the dates page. Every deadline in the table has its own page in the patch window table. Short answers to related questions are 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
how often should you perform patch management
Monthly at a minimum, with a shorter deadline for urgent fixes. CIS Controls v8 asks monthly or more frequent; Cyber Essentials v3.3 asks 14 days of release for critical or high fixes.
Sources
- CIS Controls v8 (August 2023 guide), Control 7 safeguards, read 19 Nov 2026
- NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management, read 19 Nov 2026
- PCI SSC blog, Just Published: PCI DSS v4.0.1 (11 Jun 2024), read 19 Nov 2026
- CISA, BOD 26-04, Prioritizing Security Updates Based on Risk, read 19 Nov 2026
- FedRAMP legacy playbook, POA&M, Remediation Requirements, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
- Microsoft Learn, Update release cycle for Windows clients, read 19 Nov 2026
- Microsoft MSRC CVRF API, November 2026 Security Updates, read 19 Nov 2026
Last reviewed 19 Nov 2026