# Severity and Patch Windows: What Each Framework Sets

Canonical: https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/
Last reviewed: 19 Nov 2026

## 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.

### Every number read, side by side

| Source | Timing | Clock starts | Binds whom |
|---|---|---|---|
| CISA BOD 26-04 (10 Jun 2026), Table 1 | 3 days (with forensic triage for the highest-risk rows), 14 days, 60 days, or fix on system upgrade | Per directive | U.S. federal agencies; 16 rows; read from an image |
| UK Cyber Essentials v3.3 | 14 days for critical or high | Release of the update | Applicants, in-scope systems |
| HIPAA Security Rule proposal, 90 FR 898 | 15 days critical, 30 days high | Identifying the need to patch | Proposed; not in force |
| PCI DSS v4.0.1 (PCI SSC FAQ 1597) | One month for critical | Release | Entities in scope; standard text not read |
| FedRAMP legacy playbook | 30 days critical and high, 90 moderate, 180 low | Discovery | Legacy authorizations |
| FedRAMP 2026 VDR rules | 12 hours to 192 days by class and impact level | Evaluation | Mandatory from 7 Dec 2026 |
| CIS Controls v8, 7.3, 7.4, 7.7 | Monthly 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-prioritized | Availability of the patch (2024/2690) | No day count |
| NIST SP 800-40 Rev. 4 | None; timeframes defined per maintenance plan | - | Guidance |

Read 19 Nov 2026; each row has its own page in the [patch window table](https://patchmanagementpolicy.com/patch-windows/).

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

```text
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](https://patchmanagementpolicy.com/templates/patch-management-policy-template/); for the next clause see [testing and staging](https://patchmanagementpolicy.com/policy-sections/testing-and-staging/).

### Sources

- [CISA, BOD 26-04, Prioritizing Security Updates Based on Risk (10 June 2026), Required Action 6 and Table 1](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026
- [CISA, BOD 22-01 (revoked), directive page](https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities), read 19 Nov 2026
- [CISA, BOD 19-02 (revoked, archived), directive page](https://www.cisa.gov/news-events/directives/bod-19-02-vulnerability-remediation-requirements-internet-accessible-systems), read 19 Nov 2026
- [NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management](https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf), read 19 Nov 2026
- [Federal Register, HIPAA Security Rule to Strengthen the Cybersecurity of ePHI, 90 FR 898 (6 January 2025), proposed 164.308(a)(4)](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information), read 19 Nov 2026
- [PCI Security Standards Council blog, Just Published: PCI DSS v4.0.1 (11 June 2024)](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1), read 19 Nov 2026
- [FedRAMP, legacy Rev5 playbook, POA&M, Remediation Requirements](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/), read 19 Nov 2026
- [FedRAMP, Consolidated Rules for 2026, Rev5, Vulnerability Detection and Response](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/), read 19 Nov 2026
- [CIS Controls v8 guide (August 2023), Control 7, safeguards 7.1 to 7.7](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026
- [EU Implementing Regulation 2024/2690, Annex, point 6.6](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690), read 19 Nov 2026
- [EU Delegated Regulation 2024/1774 (DORA RTS), Article 10(4)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32024R1774), read 19 Nov 2026
- [Cornell LII, 23 NYCRR 500.5 (as amended, effective 1 November 2023)](https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.5), read 19 Nov 2026
- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [Patch Testing and Staging Policy Clause](https://patchmanagementpolicy.com/policy-sections/testing-and-staging/)
- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
