# Patch Management Policy Sections: The Nine to Include

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

## Patch management policy sections

A patch management policy needs nine sections: purpose and scope, roles, asset inventory, severity and patch windows, testing, maintenance windows, emergency patching, reporting and metrics, and review and approval. Each answers named clauses read on 19 Nov 2026, and exceptions sit in an annex.

### The nine sections and what each answers

| # | Section | One line | Clauses it answers (read 19 Nov 2026) |
|---|---|---|---|
| 1 | Purpose and scope | What is covered, what is excluded, who approved the exclusion | Cyber Essentials v3.3 scope categories; NIS2 point 6.6.1; NIST SP 800-40r4 3.2 |
| 2 | Roles and responsibilities | Who owns, runs, approves, installs and escalates | DORA RTS Art. 10(4)(d) escalation; NIST audiences for metrics |
| 3 | Asset inventory requirement | What the inventory records and how fresh it stays | NIST 3.2; CIS Controls v8 safeguard 7.1 |
| 4 | Severity and patch windows | Classes, deadlines and the clock start | Cyber Essentials 14 days; PCI one month (FAQ 1597); HIPAA proposal 15 and 30; FedRAMP 2026 and legacy; BOD 26-04 |
| 5 | Testing and staging | Canary first, rollback ready, evidence kept | NIS2 6.6.1(b); NIST 3.5.1; DORA Art. 10(4) |
| 6 | Maintenance windows | When installs happen and when they are forced | NIST 3.5.1; CIS 7.3 and 7.4 (monthly) |
| 7 | Emergency patching clause | When windows are suspended and who decides | NIST 3.5.2; DORA Art. 10(4) |
| 8 | Reporting and metrics | What is measured, for whom, how often | NIST 3.6; CIS 7.2 monthly review |
| 9 | Review and approval | Annual review and the events that force one | HIPAA proposal 12 months; CIS 7.1 annual; BOD 26-04 Table 1 reassessment |

Numbering matches the [general policy template](https://patchmanagementpolicy.com/templates/patch-management-policy-template/). Exceptions are Annex A, written in the [exceptions clause](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/).

### Why this order

Scope and roles come first because every later clause needs a subject and an owner. The inventory precedes the windows because a window can only be met for an asset the policy knows about; NIST SP 800-40 Rev. 4 puts inventory second in its planning steps, before it defines risk response scenarios and maintenance plans. Testing and maintenance windows follow the deadlines because they are the means of meeting them. Emergency patching comes after the routine rules since it is defined as the departure from them. Reporting and review close the loop: a policy with no measurement and no review date cannot show it was followed, and the proposed HIPAA rule would require the review and test at least once every 12 months.

### Which sections frameworks leave to you

Several frameworks set no number and ask only for a documented process. EU Regulation 2024/2690 point 6.6.1(a) asks for patches within a reasonable time; DORA's RTS asks financial entities to set their own deadlines; NYDFS 500.5(c) asks for timely remediation prioritized by risk. For these, section 4 of your policy is the requirement, and an auditor will test you against what you wrote. The [patch window table](https://patchmanagementpolicy.com/patch-windows/) lists the numbers that exist and says which frameworks set none.

Do not put the decision on whether to accept a risk into the policy body. The policy carries an exceptions annex that records the departure; the grounds and fields are in the [exceptions template](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/).

### Sources

- [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
- [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
- [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
- [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
- [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
- [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
- [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
- [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

Last reviewed 19 Nov 2026

### Related pages

- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [Patch Management Policy Exceptions Clause Template](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/)
- [Patch Management Policy Template Set, 10 Documents](https://patchmanagementpolicy.com/templates/)
