# Patch Management Policy Builder and Templates

Canonical: https://patchmanagementpolicy.com/
Last reviewed: 19 Nov 2026

## Patch Management Policy: build one from the clauses it has to meet

A patch management policy is the written rule that says which assets are patched, who approves, and how fast, by severity. The builder below assembles one from clauses read on 19 Nov 2026, including CISA BOD 26-04 (3, 14 and 60 days), UK Cyber Essentials v3.3 (14 days) and NIST SP 800-40 Rev. 4.

### What the builder produces

You choose a company size, the frameworks that apply to you and the asset classes you run. The builder, which runs in your browser and sends nothing, returns policy text with a patch window for each severity, and downloads as .docx and PDF. Each framework number in the output comes from the table below or from the [patch window table](https://patchmanagementpolicy.com/patch-windows/), with its source and read date. Where no selected framework sets a number, the builder shows the general policy template's suggested default and labels it "Suggested default (site template)".

Where a framework sets no number, the builder does not present one as the framework's. It shows the template's suggested default, labeled as a default, and a field marked "Not set: fill in" where the template has none. That affects more frameworks than most templates admit: NIST SP 800-40 Rev. 4, NIS2, DORA and NYDFS Part 500 all leave the day count to the organization.

The text sits inside the nine sections described in [the policy sections](https://patchmanagementpolicy.com/policy-sections/). The same text, filled for a company type, is in [the template set](https://patchmanagementpolicy.com/templates/), and the companion [procedure](https://patchmanagementpolicy.com/templates/patch-management-procedure/) says how each step is carried out.

### Patch windows the builder draws on

| Source | Window stated | Who it binds | Status on 19 Nov 2026 |
|---|---|---|---|
| CISA BOD 26-04 (issued 10 Jun 2026) | 3 days (with forensic triage for the highest-risk rows), 14 days, 60 days, or fix on system upgrade | Federal agency assets | In force; revoked BOD 19-02 and BOD 22-01 |
| UK Cyber Essentials v3.3 | 14 days of release for fixes the vendor calls critical or high risk | Certified organizations | Effective 27 Apr 2026 |
| PCI DSS v4.0.1 | One month from release for critical vulnerabilities, per PCI SSC FAQ 1597 | Cardholder data environments | Standard text could not be read on 19 Nov 2026; FAQ 1597 read |
| CIS Controls v8, 7.3 and 7.4 | Monthly, or more frequent | Operating systems and applications | Guidance |
| FedRAMP legacy POA&M page | 30 days critical and high, 90 moderate, 180 low, from discovery | Legacy Rev5 providers | Legacy documentation |
| HIPAA Security Rule NPRM | 15 calendar days critical, 30 high (proposed) | Covered entities and business associates | Proposal of 6 Jan 2025; no final rule found on 19 Nov 2026 |
| NIS2, DORA, NYDFS 500.5 | No number: reasonable time, own deadlines, timely | Entities in scope | In force |

Windows by source, read 19 Nov 2026. Each row has its own page under /patch-windows/. ISO/IEC 27001 Annex A 8.8 and SOC 2 clause text could not be read on 19 Nov 2026 and are not in the table.

Severity means different things in each row: BOD 26-04 uses four inputs (publicly exposed, in the KEV catalog, automatable, technical impact), Cyber Essentials uses the vendor's own words, PCI uses critical only. The [method page](https://patchmanagementpolicy.com/method/) explains how the builder reconciles them.

### Where to go next

- Writing from scratch: [how to write a patch management policy](https://patchmanagementpolicy.com/guides/how-to-write-a-patch-management-policy/).
- Definitions first: [what a patch management policy is](https://patchmanagementpolicy.com/guides/what-is-a-patch-management-policy/).
- The steps behind the policy: [the patch management process](https://patchmanagementpolicy.com/process/).
- Dates that change windows: [dates to know](https://patchmanagementpolicy.com/dates-to-know/).

### Sources

- [CISA, BOD 26-04, Prioritizing Security Updates Based on Risk](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), 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
- [PCI SSC blog, Just Published: PCI DSS v4.0.1 (11 Jun 2024)](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1), read 19 Nov 2026
- [CIS Controls v8 (August 2023 guide), Control 7 safeguards](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026
- [FedRAMP legacy playbook, POA&M, Remediation Requirements](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/), read 19 Nov 2026
- [Federal Register, HIPAA Security Rule NPRM, 90 FR 898 (6 Jan 2025)](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
- [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
- [EUR-Lex, Implementing Regulation (EU) 2024/2690, Annex points 6.6.1 and 6.6.2](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690), read 19 Nov 2026
- [EUR-Lex, Delegated Regulation (EU) 2024/1774, Article 10(4)(d)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32024R1774), read 19 Nov 2026
- [Cornell LII, 23 NYCRR 500.5](https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.5), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Policy Template Set, 10 Documents](https://patchmanagementpolicy.com/templates/)
- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [Patch Management Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/)
- [Patch Management Guides: 13 Guides, Each Sourced](https://patchmanagementpolicy.com/guides/)
- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
