Patch Management Policy

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

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.
PracticeSourceWhat it saysRecord that proves it
Group assets by maintenance needsNIST SP 800-40 Rev. 4, 3.4A maintenance group has "the same software maintenance needs"Inventory field naming the group for every asset
Write a plan per group and scenarioNIST 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 firstNIST 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 updatesCIS Controls v8, 7.3 and 7.4Monthly, or more frequentTool schedule export showing the cadence
Set a window for critical and highCyber Essentials v3.3Within 14 days of releaseInstall date beside vendor release date, per asset
Name the clock startCISA BOD 26-04KEV listing or identification, whichever is firstTicket field holding the start date and which event set it
Document skipped patchesNIS2 Implementing Regulation 2024/2690, 6.6.2Derogation when disadvantages outweigh benefitsWritten derogation with its stated reason
Escalate missed deadlinesDORA RTS 2024/1774, Article 10(4)(d)"escalation procedures"Escalation log entry with date and recipient
Include third-party componentsNIST SP 800-218 v1.1, PW.4.4Verify "throughout their life cycles"Component list with the version each build uses
Keep exceptions under watchNIST SP 800-40 Rev. 4, 3.5.5"reviewed regularly"Exceptions register with the last recheck date

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). 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, and the defaults other platforms ship with are in automated patch management.

Where each practice sits

Groups and plans are worked through in the program guide, windows in the patch window table, and the written record for a skipped patch in the exceptions clause. Vendor pages in the directory are read as that vendor's claims, and practices without a primary text behind them are not listed.

4.3 Patch windows

SeverityWindow3143090180 days
1. Known exploited, internet-facing3 calendar daysApplies to: Systems reachable from the internet
1. Known exploited, other14 calendar daysApplies to: All other systems
2. Critical14 calendar days
3. High30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials]
4. Medium90 calendar days
5. Low180 calendar days
Routine baselineEvery month, or more oftenApplies to: Operating system and application updates

No framework selected: every window above is the site template's suggested default, and the clock starts as this section states.

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

Last reviewed 19 Nov 2026