Patch Management Policy

Patch management SLA by severity

Frameworks set patch deadlines from 12 hours to 192 days, and several set none: Cyber Essentials v3.3 says 14 days, the HIPAA proposal 15 and 30, PCI DSS one month for critical, CISA BOD 26-04 3, 14 or 60 days. A policy must pick one number per class and one clock start.

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.

Every number read, side by side

Read 19 Nov 2026; each row has its own page in the patch window table.
SourceTimingClock startsBinds whom
CISA BOD 26-04 (10 Jun 2026), Table 13 days (with forensic triage for the highest-risk rows), 14 days, 60 days, or fix on system upgradePer directiveU.S. federal agencies; 16 rows; read from an image
UK Cyber Essentials v3.314 days for critical or highRelease of the updateApplicants, in-scope systems
HIPAA Security Rule proposal, 90 FR 89815 days critical, 30 days highIdentifying the need to patchProposed; not in force
PCI DSS v4.0.1 (PCI SSC FAQ 1597)One month for criticalReleaseEntities in scope; standard text not read
FedRAMP legacy playbook30 days critical and high, 90 moderate, 180 lowDiscoveryLegacy authorizations
FedRAMP 2026 VDR rules12 hours to 192 days by class and impact levelEvaluationMandatory from 7 Dec 2026
CIS Controls v8, 7.3, 7.4, 7.7Monthly or more often-Recommended practice
EU 2024/2690 point 6.6.1(a); DORA Art. 10(4)(d); NYDFS 500.5(c)Reasonable time; self-set deadlines; timely and risk-prioritizedAvailability of the patch (2024/2690)No day count
NIST SP 800-40 Rev. 4None; timeframes defined per maintenance plan-Guidance

Two former federal rules are history. BOD 19-02 (29 April 2019) set 15 days for critical and 30 for high on internet-accessible systems; BOD 22-01 (3 November 2021) set 2 weeks for catalog entries with a 2021 or later CVE ID and 6 months for older ones. Both pages now read that the directive has been revoked and superseded by BOD 26-04. Any policy that still quotes two weeks for known exploited items is quoting a revoked directive.

Sample wording

4.1 Severity is the vendor's published severity. A vulnerability in the CISA Known Exploited Vulnerabilities catalog is class 1 whatever the vendor label. Where two classes apply, the shorter window applies.

4.2 The window runs from the date the vendor releases the patch. Where no patch exists it runs from the date one becomes available.

4.3 Class 1: 3 days (internet-facing) or 14 days. Class 2 (critical): 14 days. Class 3 (high): 30 days. Class 4 (medium): 90 days. Class 5 (low): 180 days.

4.4 A window that will be missed is escalated before it expires.

Common mistakes

  • Mixing clock starts. A 14 day window from release and a 15 day window from identification can differ by weeks when an asset is found late.
  • One number for everything. Frameworks that set numbers set them per class; a flat 30 days fails Cyber Essentials and is too loose for known exploited items.
  • Quoting a revoked directive. See above: BOD 22-01 and BOD 19-02 were revoked on the issue of BOD 26-04 on 10 June 2026.
  • Citing PCI DSS wording from memory. The standard text could not be read on 19 Nov 2026; only the Council's FAQ 1597 and its v4.0.1 blog were.

Windows for each framework are explained in the general template's source table; for the next clause see testing and staging.

Sources

Last reviewed 19 Nov 2026