# What a Patch Management Policy Is and Must State

Canonical: https://patchmanagementpolicy.com/guides/what-is-a-patch-management-policy/
Last reviewed: 19 Nov 2026

## What is a patch management policy

A patch management policy is the document an organization approves to make patching mandatory: it names the assets covered, the owners, the deadlines by severity, how exceptions are handled and when the policy is reviewed. NIST SP 800-40 Rev. 4 (April 2022) calls the working detail a maintenance plan.

### What it contains

The policy states rules; the [procedure](https://patchmanagementpolicy.com/templates/patch-management-procedure/) states steps. A policy says that critical fixes are installed within a set number of days and who may approve a delay. The procedure says how a technician stages, deploys and verifies. Keeping them apart means the policy changes once a year and the procedure changes when tooling does.

1. Purpose and scope: which assets, which software, which owners.
2. Roles: who approves, who deploys, who reports.
3. Inventory duty: no asset is patched that is not known.
4. Severity and windows: the deadline per severity and where the clock starts.
5. Testing and staging, maintenance windows, exceptions, reporting, review.

### Which outside text asks for which part

| Policy part | Outside text | What it says (short quote) |
|---|---|---|
| Deadlines and escalation | DORA RTS 2024/1774, Article 10(4)(d) | "set deadlines for the installation of software and hardware patches and updates and escalation procedures in case those deadlines cannot be met" |
| Deadlines left to you, with a documented exception | NIS2 Implementing Regulation 2024/2690, 6.6.1(a) and 6.6.2 | "security patches are applied within a reasonable time after they become available"; patches may be skipped when disadvantages outweigh benefits |
| A plan per group of assets | NIST SP 800-40 Rev. 4, section 3.5 | "Organizations should define a maintenance plan for each maintenance group" |
| Annual review | CIS Controls v8, 7.1 | Review documentation "annually, or when significant enterprise changes occur" |
| Review and test every 12 months | HIPAA Security Rule NPRM, proposed 164.308(a)(4)(ii)(B) | Proposed only, published 6 Jan 2025, not in force on the day of the last check |

Policy parts and the clauses behind them, read 19 Nov 2026.

Only the NPRM row carries a review period measured in months; DORA and NIS2 do not give a day count, so a policy that quotes them still has to choose its own. The [patch window table](https://patchmanagementpolicy.com/patch-windows/) shows which frameworks do set numbers.

### What the policy leaves out

It does not carry the list of products, the names of tools or the current week's schedule. Those change faster than an approval cycle. Link them, as an appendix, from the [policy sections](https://patchmanagementpolicy.com/policy-sections/). To write one now, follow [how to write a patch management policy](https://patchmanagementpolicy.com/guides/how-to-write-a-patch-management-policy/) or fill the [template](https://patchmanagementpolicy.com/templates/patch-management-policy-template/).

### Questions

**what is a patch management policy**

A patch management policy is the approved document that makes patching mandatory and sets who is covered, who approves, the deadline per severity, how exceptions work and when it is reviewed. The steps that carry it out go in a separate procedure. Clauses behind each part are in the table above.

**what is patch management policy**

It is the same document: the written rule for identifying, prioritizing, installing and verifying patches. NIST SP 800-40 Rev. 4 defines the process it governs, and the [policy sections](https://patchmanagementpolicy.com/policy-sections/) explain each part.

### Sources

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

Last reviewed 19 Nov 2026

### Related pages

- [How to Write a Patch Management Policy in 9 Sections](https://patchmanagementpolicy.com/guides/how-to-write-a-patch-management-policy/)
- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
