Patch Management Policy

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.

Patch Management Policy

Owner: [Role, e.g. Head of IT]. Approved by: [Name, role]. Version: [1.0]. Effective: [date]. Next review: [date, no later than 12 months after approval].

Built for a company of 50 to 999 people. Frameworks: none selected.

1 Purpose and scope

1.1 This policy sets how [Company name] finds, tests, installs and verifies security patches and updates, so that known vulnerabilities in its systems are fixed inside the windows in section 4.

1.2 It covers every operating system, firmware, application, library, container image and cloud service that [Company name] owns, operates or administers, including systems run by a third party where [Company name] controls the patch schedule. Exclusions: [list each, with reason and approver]. An exclusion not listed here is not valid.

1.3 Software that no longer receives vendor security updates is removed from service or isolated and recorded under Annex A. It is not kept in service by default.

1.4 Asset classes in scope: Endpoints, Servers, Network devices, Cloud and containers, Third-party apps, OT.

2 Roles and responsibilities

2.1 Policy owner ([role]): owns this policy, approves the windows, reports to [executive sponsor].

2.2 Patch coordinator ([role]): runs the monthly cycle, keeps the schedule and the evidence.

2.3 System owners ([role per system]): approve outage time and accept test results for their maintenance group.

2.4 Platform administrators ([role]): deploy, verify and roll back.

2.5 Executive sponsor ([role]): receives the monthly report and decides any window missed for more than [5] working days.

2.6 Third parties that administer a system must patch to these windows and report completion in writing.

3 Asset inventory

3.1 The inventory records, for every asset: owner; platform type (IT, OT, IoT, mobile, cloud, virtual machine, container); who administers it (internal, third party, shared); the tool that manages it; whether it is reachable from the internet; its maintenance group; any legal, contractual or outage limit on patching; and the date it was last patched.

3.2 An asset is added before it goes into production. Automated discovery runs at least [weekly].

3.3 An asset found by discovery that has no owner is given one within [5] working days or isolated.

4 Severity and patch windows

4.1 Each vulnerability takes the severity the vendor publishes. If the vendor publishes none, the policy owner assigns one from the organization's risk analysis. A vulnerability listed in the CISA Known Exploited Vulnerabilities catalog is class 1 whatever its vendor label. If two classes apply, the shorter window applies.

4.2 The window starts when the vendor releases the patch. If no patch exists, the window starts when one becomes available and the mitigation in Annex A applies meanwhile.

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.

4.4 A window that cannot be met is escalated to the executive sponsor before it expires and recorded under Annex A.

5 Testing and staging

5.1 Every maintenance group has a canary set of [number or percent] assets that receives each patch first.

5.2 A patch moves from canary to the full group after [2] working days with no incident, or sooner if the patch is class 1.

5.3 A rollback method is written down before deployment. If none exists, say so in the change record and name the fallback.

5.4 Test evidence (what was tested, by whom, result, date) is kept with the change record.

6 Maintenance windows

6.1 Standard windows by group: [group, day, hours, time zone]. The schedule is published [5] working days ahead.

6.2 Installation is forced after [number] days from the start of the window, by direct execution or by restricting network access of the unpatched asset.

6.3 Reboots needed to finish an install happen inside the same window. An asset that cannot reboot is handled under Annex A.

7 Emergency patching

7.1 The policy owner (or deputy [role]) may declare an emergency for named assets when a vulnerability is class 1, when a vendor issues an emergency update, or when the policy owner judges that waiting for the standard window is unacceptable.

7.2 While an emergency is declared, the standard windows and change lead times are suspended for the named assets only. The declaration records who declared it, the time, the assets and the reason.

7.3 Canary installation may run for minutes to hours; full installation follows in the hours or days the emergency allows.

7.4 When the patch is installed and verified, the declaration is closed and the standard windows resume.

8 Reporting and metrics

8.1 Each month the patch coordinator reports to the executive sponsor: the share of assets patched inside their window, by class and by asset importance; the mean and median days to patch; open exceptions with age; assets with no owner.

8.2 Evidence for every reported figure is exportable from [system] for [retention period].

9 Review and approval

9.1 The policy is reviewed at least every 12 months, and when a framework named in section 4 changes its timing.

9.2 Changes are approved by [role]. The approved version, date and approver are recorded on the cover.

Annex A Exceptions

Exceptions follow the exceptions clause ([insert clause text]).

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, 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. The same text, filled for a company type, is in the template set, and the companion procedure says how each step is carried out.

Patch windows the builder draws on

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.
SourceWindow statedWho it bindsStatus 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 upgradeFederal agency assetsIn force; revoked BOD 19-02 and BOD 22-01
UK Cyber Essentials v3.314 days of release for fixes the vendor calls critical or high riskCertified organizationsEffective 27 Apr 2026
PCI DSS v4.0.1One month from release for critical vulnerabilities, per PCI SSC FAQ 1597Cardholder data environmentsStandard text could not be read on 19 Nov 2026; FAQ 1597 read
CIS Controls v8, 7.3 and 7.4Monthly, or more frequentOperating systems and applicationsGuidance
FedRAMP legacy POA&M page30 days critical and high, 90 moderate, 180 low, from discoveryLegacy Rev5 providersLegacy documentation
HIPAA Security Rule NPRM15 calendar days critical, 30 high (proposed)Covered entities and business associatesProposal of 6 Jan 2025; no final rule found on 19 Nov 2026
NIS2, DORA, NYDFS 500.5No number: reasonable time, own deadlines, timelyEntities in scopeIn force

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 explains how the builder reconciles them.

Where to go next

Sources

Last reviewed 19 Nov 2026