# Patch management practices, each with its source

Canonical: https://patchmanagementpolicy.com/guides/patch-management-practices/
Last reviewed: 19 Nov 2026

## Patch management practices, each with its source

Ten patch management practices follow, each with its clause and the record that shows it is done, read on 19 Nov 2026. They include maintenance groups and canaries (NIST SP 800-40 Rev. 4), a 14 day window (Cyber Essentials v3.3) and an AWS approval delay that can run from 0 to 360 days.

### Practices, sources and the record that proves each

| Practice | Source | What it says | Record that proves it |
|---|---|---|---|
| Group assets by maintenance needs | NIST SP 800-40 Rev. 4, 3.4 | A maintenance group has "the same software maintenance needs" | Inventory field naming the group for every asset |
| Write a plan per group and scenario | NIST SP 800-40 Rev. 4, 3.5 | "define a maintenance plan for each maintenance group" | Plan with start and end times for each action |
| Patch a small set first | NIST SP 800-40 Rev. 4, 3.5.1 | "These assets act as canaries" | Canary membership list and the date the rollout widened |
| Automate OS and application updates | CIS Controls v8, 7.3 and 7.4 | Monthly, or more frequent | Tool schedule export showing the cadence |
| Set a window for critical and high | Cyber Essentials v3.3 | Within 14 days of release | Install date beside vendor release date, per asset |
| Name the clock start | CISA BOD 26-04 | KEV listing or identification, whichever is first | Ticket field holding the start date and which event set it |
| Document skipped patches | NIS2 Implementing Regulation 2024/2690, 6.6.2 | Derogation when disadvantages outweigh benefits | Written derogation with its stated reason |
| Escalate missed deadlines | DORA RTS 2024/1774, Article 10(4)(d) | "escalation procedures" | Escalation log entry with date and recipient |
| Include third-party components | NIST SP 800-218 v1.1, PW.4.4 | Verify "throughout their life cycles" | Component list with the version each build uses |
| Keep exceptions under watch | NIST SP 800-40 Rev. 4, 3.5.5 | "reviewed regularly" | Exceptions register with the last recheck date |

Read 19 Nov 2026. Quotes shortened. The last column is this site's drafting of the record each clause implies; none of the sources prescribes a format.

### One setting with a range: the approval delay

A tool's approval delay is where a practice meets a number. In AWS Systems Manager Patch Manager, a baseline's `ApproveAfterDays` is "the number of days after the release date of each patch matched by the rule that the patch is marked as approved," with a minimum of 0 and a maximum of 360 ([AWS PatchRule reference](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_PatchRule.html)). AWS evaluates release dates in UTC: its own example is a patch released at 2025-11-09T18:00:00Z with a value of 7, approved after 2025-11-16T18:00:00Z. AWS also cautions that for Windows Server baselines a value that is too broad can leave crucial patches uninstalled, because superseded updates are removed.

The arithmetic belongs in the policy. Under a 14 day window from release (Cyber Essentials v3.3), a 7 day approval delay leaves 7 days for scheduling and installing; a 14 day delay leaves none. That subtraction is this site's, not AWS's. The same window logic for each asset class is in [patching by asset class](https://patchmanagementpolicy.com/patching/), and the defaults other platforms ship with are in [automated patch management](https://patchmanagementpolicy.com/guides/automated-patch-management/).

### Where each practice sits

Groups and plans are worked through in the [program guide](https://patchmanagementpolicy.com/guides/patch-management-program/), windows in the [patch window table](https://patchmanagementpolicy.com/patch-windows/), and the written record for a skipped patch in the [exceptions clause](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/). Vendor pages in the [directory](https://patchmanagementpolicy.com/tools/) are read as that vendor's claims, and practices without a primary text behind them are not listed.

### Questions

**why system patch management policy needed**

A policy fixes deadlines, owners and exceptions in advance so patching is not renegotiated per patch. NIST SP 800-40 Rev. 4 treats patching as preventive maintenance and asks for a plan per maintenance group.

**what is a security patch management process**

It is the identify, prioritize, acquire, install and verify cycle applied to security fixes. The deadline per severity is set in the policy.

### 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
- [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
- [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
- [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
- [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
- [NIST SP 800-218 v1.1, Secure Software Development Framework, PW.4.4, RV.1.1, RV.2.2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf), read 19 Nov 2026
- [AWS Systems Manager API Reference, PatchRule (ApproveAfterDays, ApproveUntilDate)](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_PatchRule.html), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Program: Six Groups and What Proves Each](https://patchmanagementpolicy.com/guides/patch-management-program/)
- [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 Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/)
- [Automated Patch Management: Defaults a Policy Must Set](https://patchmanagementpolicy.com/guides/automated-patch-management/)
