Patch Management Policy

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

Patch Window Table, 37 rows, read 19 Nov 2026. Timing is stated as the source states it; maximums and proposals are labeled. Rows marked history are revoked and not current rules.
FrameworkVersionClauseWhat it requiresTimingApplies toSourceRead
PCI DSS4.0.16.3.3Install security patches and updates; critical vulnerabilities resolved within one month of release1 month (30 days) for criticalEntities in PCI DSS scope (scope text not read)PCI SSC FAQ 15972026-11-19
PCI DSS4.0.16.3.3, other patchesAll other applicable patches installed within time frames set by the entity's risk assessmentNo number set; entity's targeted risk analysisEntities in PCI DSS scopePCI SSC FAQ 15972026-11-19
PCI DSS4.0.16.3.1, 11.3.1, 11.3.1.1Assign risk levels to vulnerabilities; resolve critical and high-risk; address lower levels per targeted risk analysisNo number setEntities in PCI DSS scopePCI SSC FAQ 15972026-11-19
CISA BOD 26-04Issued 10 Jun 2026Table 1, rows 1, 3, 9Remediate and perform forensic triage: in the KEV, total control, and publicly exposed or automatable3 days and forensic triageFederal agency assets; contractors only if the contract says soCISA BOD 26-042026-11-19
CISA BOD 26-04Issued 10 Jun 2026Table 1, rows 2, 5Remediate: row 2 exposed, in the KEV, automatable, partial control; row 5 exposed, not in the KEV, automatable, total control3 daysFederal agency assetsCISA BOD 26-042026-11-19
CISA BOD 26-04Issued 10 Jun 2026Table 1, rows 4, 6, 7, 10, 11, 12Remediate: 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 control14 calendar daysFederal agency assetsCISA BOD 26-042026-11-19
CISA BOD 26-04Issued 10 Jun 2026Table 1, rows 8, 13, 14Remediate: exposed, not in the KEV, not automatable, partial; not exposed, not in the KEV, automatable60 calendar daysFederal agency assetsCISA BOD 26-042026-11-19
CISA BOD 26-04Issued 10 Jun 2026Table 1, rows 15, 16Remediate at next scheduled major upgrade or rebuild: not exposed, not in the KEV, not automatableFix on system upgradeFederal agency assetsCISA BOD 26-042026-11-19
CISA BOD 22-01 (revoked 10 Jun 2026)Issued 3 Nov 2021Required actionsRemediate KEV entries by the catalog due date2 weeks (CVE assigned 2021 or later); 6 months (older). History onlyFederal civilian agencies (historical)CISA BOD 22-012026-11-19
CISA BOD 19-02 (revoked 10 Jun 2026)Issued 29 Apr 2019Required actionsRemediate critical and high findings on internet-accessible systems15 calendar days (critical); 30 (high). History onlyFederal agency internet-accessible systems (historical)CISA BOD 19-022026-11-19
NIST SP 800-40Rev. 4, April 20223.5Maintenance plan per group per scenario, with timeframes for beginning and ending each actionNo number setOrganizations; guidance, not a mandateNIST SP 800-40r42026-11-19
NIST SP 800-40Rev. 4, April 20223.5.2Emergency patching on an accelerated scheduleNo number set (hours or days, by urgency)Emergency patching scenarioNIST SP 800-40r42026-11-19
NIST SP 800-40Rev. 4, April 20223.5 (KEV note)Reports BOD 22-01: remediate new KEV entries within two weeks2 weeks, as reported for BOD 22-01; not a NIST requirementU.S. federal agencies (historical)NIST SP 800-40r42026-11-19
CIS Controlsv8, Aug 2023 guide7.3, 7.4Automated operating system and application patch managementMonthly, or more frequentEnterprise assets; IG1, IG2, IG3CIS Controls v8 guide2026-11-19
CIS Controlsv8, Aug 2023 guide7.7Remediate detected software vulnerabilities per the remediation processMonthly, or more frequentIG2, IG3CIS Controls v8 guide2026-11-19
CIS Controlsv8, Aug 2023 guide7.2Risk-based remediation strategy in a documented processMonthly, or more frequent review of the strategyIG1, IG2, IG3CIS Controls v8 guide2026-11-19
CIS Controlsv8, Aug 2023 guide7.1Documented vulnerability management processAnnual review of the documentationIG1, IG2, IG3CIS Controls v8 guide2026-11-19
CIS Controlsv8, Aug 2023 guide7.5, 7.6Automated vulnerability scans: internal, then externally exposed assetsQuarterly (internal); monthly (external), or more frequentIG2, IG3CIS Controls v8 guide2026-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 levelNo number setCovered entities and business associateseCFR 45 CFR 164.3082026-11-19
HIPAA Security Rule NPRM (proposed)90 FR 898, 6 Jan 2025Proposed (a)(4)(ii)(C)(1)Patch, update or upgrade for a critical risk15 calendar days (proposed)Relevant electronic information systems90 FR 8982026-11-19
HIPAA Security Rule NPRM (proposed)90 FR 898, 6 Jan 2025Proposed (a)(4)(ii)(C)(2)Patch, update or upgrade for a high risk30 calendar days (proposed)Relevant electronic information systems90 FR 8982026-11-19
HIPAA Security Rule NPRM (proposed)90 FR 898, 6 Jan 2025Proposed (a)(4)(ii)(C)(3), (B), (D) to (F)Other patches per written policy; annual review and test; documented exceptions with compensating controlsNo number for other patches; 12 months for review (proposed)Covered entities and business associates90 FR 8982026-11-19
FedRAMP Rev5 VDRLaunched 24 Jun 2026VDR-TFR-PVR, Class A and BPartially or fully mitigate, or remediate to a lower impact, by Potential Agency Impact level4 to 192 days (maximums, SHOULD)Rev5 certification holdersFedRAMP VDR rules2026-11-19
FedRAMP Rev5 VDRLaunched 24 Jun 2026VDR-TFR-PVR, Class CSame, shorter table2 to 192 days (maximums, SHOULD)Class C certification holdersFedRAMP VDR rules2026-11-19
FedRAMP Rev5 VDRLaunched 24 Jun 2026VDR-TFR-PVR, Class DSame, shortest table12 hours to 192 days (maximums, SHOULD)Class D certification holdersFedRAMP VDR rules2026-11-19
FedRAMP Rev5 VDRLaunched 24 Jun 2026VDR-TFR-KEVRemediate KEVs by the CISA due date, even if fully mitigatedPer KEV entry; no number set by FedRAMPFedRAMP certification holdersFedRAMP VDR rules2026-11-19
FedRAMP Rev5 VDRLaunched 24 Jun 2026VDR-TFR-RMNMitigate or remediate remaining vulnerabilities in routine operationsNo number setFedRAMP certification holdersFedRAMP VDR rules2026-11-19
FedRAMP legacy documentationLegacy playbookRemediation RequirementsRemediate by risk level from discovery30 days (critical, high); 90 (moderate); 180 (low)Legacy Rev5 cloud service providersFedRAMP legacy POA&M page2026-11-19
UK Cyber Essentialsv3.3, effective 27 Apr 2026Security Update ManagementUpdate, including vulnerability fixes, where critical or high risk (CVSS v3 base 7 or above) or severity unknown14 days of releaseIn-scope servers, desktops, laptops, tablets, phones, firewalls, routers, IaaS, PaaS, SaaSNCSC Cyber Essentials v3.32026-11-19
EU NIS2 Implementing Regulation 2024/2690Adopted 17 Oct 2024Annex 6.6.1(a)Security patches applied after they become availableReasonable time; no number setDNS, TLD, cloud, data centre, CDN, managed service, managed security service, marketplace, search engine, social network and trust service providersEUR-Lex 2024/26902026-11-19
EU NIS2 Implementing Regulation 2024/2690Adopted 17 Oct 2024Annex 6.6.2Derogation if disadvantages outweigh benefits, documented and substantiatedNo number setSame entity typesEUR-Lex 2024/26902026-11-19
EU NIS2 Implementing Regulation 2024/2690Adopted 17 Oct 2024Annex 6.10.2(c)Address vulnerabilities critical to operationsWithout undue delaySame entity typesEUR-Lex 2024/26902026-11-19
EU DORA RTS 2024/1774Adopted 13 Mar 2024Article 10(4)(d)Set deadlines for patch installation and escalation if missedNo number set; entity sets deadlinesFinancial entities under Regulation 2022/2554EUR-Lex 2024/17742026-11-19
EU DORA RTS 2024/1774Adopted 13 Mar 2024Article 10(2)(b)Automated vulnerability scanning of assets supporting critical or important functionsAt least weeklyFinancial entities under Regulation 2022/2554EUR-Lex 2024/17742026-11-19
NYDFS 23 NYCRR Part 500500.5 as amended, eff. 1 Nov 2023500.5(c)Timely remediation, prioritized by risk to the covered entityTimely; no number setCovered entities under Part 500Cornell LII 23 NYCRR 500.52026-11-19
ISO/IEC 270012022Annex A 8.8Text not read on 19 Nov 2026 (HTTP 403)Not readNot readISO/IEC 27001 page2026-11-19
SOC 2 Trust Services Criteria2017, revised points of focus 2022CC7.1, CC8.1Text not read on 19 Nov 2026 (download needs an account)Not readNot readAICPA criteria download2026-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

Last reviewed 19 Nov 2026