Patch management timelines by framework
The Patch Window Table lists 37 rows from 12 frameworks and directives, read on 19 Nov 2026. The shortest deadline each framework states runs from 12 hours (FedRAMP Class D) and 3 days (CISA BOD 26-04) to 14 days (Cyber Essentials), 15 days (proposed HIPAA) and one month (PCI DSS). NIS2, DORA and NYDFS set no number.
How to read the table
Every row is one clause or one set of clauses, read from the issuer's own text or, where the text was not readable, from the issuer's own statement of it (PCI DSS rows come from the PCI Security Standards Council's FAQ). Timing falls into three kinds. A deadline is a count of days or hours from a stated start. A cadence is a recurring interval, such as the monthly cycle in CIS Control 7. No number set means the text read contains no figure and the organization's own policy must supply one. Calendar days are used unless the row says otherwise; the clock start differs by framework and is the first thing to check before copying any number.
Of the 37 rows, 35 carry clause text and 2 are marked Not read. Two directives are shown only as history because CISA revoked them on 10 Jun 2026. How each row was read is on the method page.
The table
| Framework | Version | Clause | What it requires | Timing | Applies to | Source | Read |
|---|---|---|---|---|---|---|---|
| PCI DSS | 4.0.1 | 6.3.3 | Install security patches and updates; critical vulnerabilities resolved within one month of release | 1 month (30 days) for critical | Entities in PCI DSS scope (scope text not read) | PCI SSC FAQ 1597 | 2026-11-19 |
| PCI DSS | 4.0.1 | 6.3.3, other patches | All other applicable patches installed within time frames set by the entity's risk assessment | No number set; entity's targeted risk analysis | Entities in PCI DSS scope | PCI SSC FAQ 1597 | 2026-11-19 |
| PCI DSS | 4.0.1 | 6.3.1, 11.3.1, 11.3.1.1 | Assign risk levels to vulnerabilities; resolve critical and high-risk; address lower levels per targeted risk analysis | No number set | Entities in PCI DSS scope | PCI SSC FAQ 1597 | 2026-11-19 |
| CISA BOD 26-04 | Issued 10 Jun 2026 | Table 1, rows 1, 3, 9 | Remediate and perform forensic triage: in the KEV, total control, and publicly exposed or automatable | 3 days and forensic triage | Federal agency assets; contractors only if the contract says so | CISA BOD 26-04 | 2026-11-19 |
| CISA BOD 26-04 | Issued 10 Jun 2026 | Table 1, rows 2, 5 | Remediate: row 2 exposed, in the KEV, automatable, partial control; row 5 exposed, not in the KEV, automatable, total control | 3 days | Federal agency assets | CISA BOD 26-04 | 2026-11-19 |
| CISA BOD 26-04 | Issued 10 Jun 2026 | Table 1, rows 4, 6, 7, 10, 11, 12 | Remediate: row 4 exposed, in the KEV, not automatable, partial; row 6 exposed, not in the KEV, automatable, partial; row 7 exposed, not in the KEV, not automatable, total; rows 10 to 12 not exposed, in the KEV, any combination other than automatable with total control | 14 calendar days | Federal agency assets | CISA BOD 26-04 | 2026-11-19 |
| CISA BOD 26-04 | Issued 10 Jun 2026 | Table 1, rows 8, 13, 14 | Remediate: exposed, not in the KEV, not automatable, partial; not exposed, not in the KEV, automatable | 60 calendar days | Federal agency assets | CISA BOD 26-04 | 2026-11-19 |
| CISA BOD 26-04 | Issued 10 Jun 2026 | Table 1, rows 15, 16 | Remediate at next scheduled major upgrade or rebuild: not exposed, not in the KEV, not automatable | Fix on system upgrade | Federal agency assets | CISA BOD 26-04 | 2026-11-19 |
| CISA BOD 22-01 (revoked 10 Jun 2026) | Issued 3 Nov 2021 | Required actions | Remediate KEV entries by the catalog due date | 2 weeks (CVE assigned 2021 or later); 6 months (older). History only | Federal civilian agencies (historical) | CISA BOD 22-01 | 2026-11-19 |
| CISA BOD 19-02 (revoked 10 Jun 2026) | Issued 29 Apr 2019 | Required actions | Remediate critical and high findings on internet-accessible systems | 15 calendar days (critical); 30 (high). History only | Federal agency internet-accessible systems (historical) | CISA BOD 19-02 | 2026-11-19 |
| NIST SP 800-40 | Rev. 4, April 2022 | 3.5 | Maintenance plan per group per scenario, with timeframes for beginning and ending each action | No number set | Organizations; guidance, not a mandate | NIST SP 800-40r4 | 2026-11-19 |
| NIST SP 800-40 | Rev. 4, April 2022 | 3.5.2 | Emergency patching on an accelerated schedule | No number set (hours or days, by urgency) | Emergency patching scenario | NIST SP 800-40r4 | 2026-11-19 |
| NIST SP 800-40 | Rev. 4, April 2022 | 3.5 (KEV note) | Reports BOD 22-01: remediate new KEV entries within two weeks | 2 weeks, as reported for BOD 22-01; not a NIST requirement | U.S. federal agencies (historical) | NIST SP 800-40r4 | 2026-11-19 |
| CIS Controls | v8, Aug 2023 guide | 7.3, 7.4 | Automated operating system and application patch management | Monthly, or more frequent | Enterprise assets; IG1, IG2, IG3 | CIS Controls v8 guide | 2026-11-19 |
| CIS Controls | v8, Aug 2023 guide | 7.7 | Remediate detected software vulnerabilities per the remediation process | Monthly, or more frequent | IG2, IG3 | CIS Controls v8 guide | 2026-11-19 |
| CIS Controls | v8, Aug 2023 guide | 7.2 | Risk-based remediation strategy in a documented process | Monthly, or more frequent review of the strategy | IG1, IG2, IG3 | CIS Controls v8 guide | 2026-11-19 |
| CIS Controls | v8, Aug 2023 guide | 7.1 | Documented vulnerability management process | Annual review of the documentation | IG1, IG2, IG3 | CIS Controls v8 guide | 2026-11-19 |
| CIS Controls | v8, Aug 2023 guide | 7.5, 7.6 | Automated vulnerability scans: internal, then externally exposed assets | Quarterly (internal); monthly (external), or more frequent | IG2, IG3 | CIS Controls v8 guide | 2026-11-19 |
| HIPAA Security Rule (in force) | 45 CFR 164.308, eCFR current | (a)(1)(ii)(A), (B) | Risk analysis; security measures that reduce risks to a reasonable and appropriate level | No number set | Covered entities and business associates | eCFR 45 CFR 164.308 | 2026-11-19 |
| HIPAA Security Rule NPRM (proposed) | 90 FR 898, 6 Jan 2025 | Proposed (a)(4)(ii)(C)(1) | Patch, update or upgrade for a critical risk | 15 calendar days (proposed) | Relevant electronic information systems | 90 FR 898 | 2026-11-19 |
| HIPAA Security Rule NPRM (proposed) | 90 FR 898, 6 Jan 2025 | Proposed (a)(4)(ii)(C)(2) | Patch, update or upgrade for a high risk | 30 calendar days (proposed) | Relevant electronic information systems | 90 FR 898 | 2026-11-19 |
| HIPAA Security Rule NPRM (proposed) | 90 FR 898, 6 Jan 2025 | Proposed (a)(4)(ii)(C)(3), (B), (D) to (F) | Other patches per written policy; annual review and test; documented exceptions with compensating controls | No number for other patches; 12 months for review (proposed) | Covered entities and business associates | 90 FR 898 | 2026-11-19 |
| FedRAMP Rev5 VDR | Launched 24 Jun 2026 | VDR-TFR-PVR, Class A and B | Partially or fully mitigate, or remediate to a lower impact, by Potential Agency Impact level | 4 to 192 days (maximums, SHOULD) | Rev5 certification holders | FedRAMP VDR rules | 2026-11-19 |
| FedRAMP Rev5 VDR | Launched 24 Jun 2026 | VDR-TFR-PVR, Class C | Same, shorter table | 2 to 192 days (maximums, SHOULD) | Class C certification holders | FedRAMP VDR rules | 2026-11-19 |
| FedRAMP Rev5 VDR | Launched 24 Jun 2026 | VDR-TFR-PVR, Class D | Same, shortest table | 12 hours to 192 days (maximums, SHOULD) | Class D certification holders | FedRAMP VDR rules | 2026-11-19 |
| FedRAMP Rev5 VDR | Launched 24 Jun 2026 | VDR-TFR-KEV | Remediate KEVs by the CISA due date, even if fully mitigated | Per KEV entry; no number set by FedRAMP | FedRAMP certification holders | FedRAMP VDR rules | 2026-11-19 |
| FedRAMP Rev5 VDR | Launched 24 Jun 2026 | VDR-TFR-RMN | Mitigate or remediate remaining vulnerabilities in routine operations | No number set | FedRAMP certification holders | FedRAMP VDR rules | 2026-11-19 |
| FedRAMP legacy documentation | Legacy playbook | Remediation Requirements | Remediate by risk level from discovery | 30 days (critical, high); 90 (moderate); 180 (low) | Legacy Rev5 cloud service providers | FedRAMP legacy POA&M page | 2026-11-19 |
| UK Cyber Essentials | v3.3, effective 27 Apr 2026 | Security Update Management | Update, including vulnerability fixes, where critical or high risk (CVSS v3 base 7 or above) or severity unknown | 14 days of release | In-scope servers, desktops, laptops, tablets, phones, firewalls, routers, IaaS, PaaS, SaaS | NCSC Cyber Essentials v3.3 | 2026-11-19 |
| EU NIS2 Implementing Regulation 2024/2690 | Adopted 17 Oct 2024 | Annex 6.6.1(a) | Security patches applied after they become available | Reasonable time; no number set | DNS, TLD, cloud, data centre, CDN, managed service, managed security service, marketplace, search engine, social network and trust service providers | EUR-Lex 2024/2690 | 2026-11-19 |
| EU NIS2 Implementing Regulation 2024/2690 | Adopted 17 Oct 2024 | Annex 6.6.2 | Derogation if disadvantages outweigh benefits, documented and substantiated | No number set | Same entity types | EUR-Lex 2024/2690 | 2026-11-19 |
| EU NIS2 Implementing Regulation 2024/2690 | Adopted 17 Oct 2024 | Annex 6.10.2(c) | Address vulnerabilities critical to operations | Without undue delay | Same entity types | EUR-Lex 2024/2690 | 2026-11-19 |
| EU DORA RTS 2024/1774 | Adopted 13 Mar 2024 | Article 10(4)(d) | Set deadlines for patch installation and escalation if missed | No number set; entity sets deadlines | Financial entities under Regulation 2022/2554 | EUR-Lex 2024/1774 | 2026-11-19 |
| EU DORA RTS 2024/1774 | Adopted 13 Mar 2024 | Article 10(2)(b) | Automated vulnerability scanning of assets supporting critical or important functions | At least weekly | Financial entities under Regulation 2022/2554 | EUR-Lex 2024/1774 | 2026-11-19 |
| NYDFS 23 NYCRR Part 500 | 500.5 as amended, eff. 1 Nov 2023 | 500.5(c) | Timely remediation, prioritized by risk to the covered entity | Timely; no number set | Covered entities under Part 500 | Cornell LII 23 NYCRR 500.5 | 2026-11-19 |
| ISO/IEC 27001 | 2022 | Annex A 8.8 | Text not read on 19 Nov 2026 (HTTP 403) | Not read | Not read | ISO/IEC 27001 page | 2026-11-19 |
| SOC 2 Trust Services Criteria | 2017, revised points of focus 2022 | CC7.1, CC8.1 | Text not read on 19 Nov 2026 (download needs an account) | Not read | Not read | AICPA criteria download | 2026-11-19 |
Deadlines in one list, shortest to longest
The list below orders the stated deadlines by length only, for the highest-priority row of each framework that has one. It does not compare the frameworks.
- 12 hours: FedRAMP Class D, PAIN-5, column LEV + IRV (a maximum, SHOULD). FedRAMP page.
- 3 days: CISA BOD 26-04, Table 1, rows 2 and 5, and with forensic triage in rows 1, 3 and 9. BOD 26-04 page.
- 14 days: UK Cyber Essentials v3.3, from release, for critical or high-risk updates. Cyber Essentials page.
- 15 days: HIPAA Security Rule proposal, critical risk, from identifying the need to patch (not in force). HIPAA page.
- One month (30 days): PCI DSS Requirement 6.3.3 for critical vulnerabilities, from release. PCI DSS page.
- Monthly cadence: CIS Controls v8, safeguards 7.3, 7.4 and 7.7.
Frameworks that leave the number to the policy
NIST SP 800-40, NIS2, DORA, the in-force HIPAA Security Rule and NYDFS Part 500 all require a patch process and leave the number to the organization. Each adds something checkable instead: NIST asks for timeframes inside each maintenance plan, NIS2 asks for a test step and a documented derogation, DORA asks for escalation when a deadline is missed, and NYDFS asks that priority follow the risk each vulnerability poses. A policy built on these needs its own severity table; the policy section on severity and patch windows shows one.
Not in the table
- ISO/IEC 27001:2022 Annex A 8.8: iso.org returned HTTP 403 on 19 Nov 2026 and the standard text is sold. Nothing is recorded about the content of the control.
- SOC 2 criteria CC7.1 and CC8.1: the AICPA download is a script-rendered page that needs a free account. Nothing is recorded.
- Australian Essential Eight: cyber.gov.au did not load (connection failed) on 19 Nov 2026. No row is written and no figure is recorded.
- CIS Controls v8.1: the safeguard text sits behind a form, so the rows are v8 as published in the August 2023 guide.
Files
The same rows are published as CSV and JSON, with the fields listed on the method page. The dates behind these rows are on dates to know. Reuse of the files follows the terms of use.
Sources
- CISA, BOD 26-04, read 19 Nov 2026
- PCI SSC, FAQ 1597, read 19 Nov 2026
- NIST, SP 800-40 Rev. 4, read 19 Nov 2026
- CIS, Controls v8 guide, Control 07, read 19 Nov 2026
- Federal Register, 90 FR 898, read 19 Nov 2026
- FedRAMP, VDR rules (Rev5), read 19 Nov 2026
- NCSC, Cyber Essentials Requirements v3.3, read 19 Nov 2026
- EUR-Lex, Regulation 2024/2690, read 19 Nov 2026
- EUR-Lex, Delegated Regulation 2024/1774, read 19 Nov 2026
- Cornell LII, 23 NYCRR 500.5, read 19 Nov 2026
Last reviewed 19 Nov 2026