Patch Management Policy

Patch management policy template

The general policy has nine numbered sections and one annex. Its windows are 3 days for known exploited internet-facing systems, 14 for critical, 30 for high, 90 for medium and 180 for low, each traced below to a clause read on 19 Nov 2026 or marked as the site's suggested default.

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].

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.

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

Windows as this template sets them, on the same 0 to 180 day scale as the builder.

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]).

Where each window comes from

No single framework sets all five classes, so the table below says, per window, which text it follows and whether that text binds you. A number is a framework requirement only when the right-hand column says so; the rest are this site's suggested defaults chosen to sit inside the stricter of the figures read.

Window sources, all read 19 Nov 2026. See the patch window table for every framework.
ClassWindowClause it followsStatus of the clause
1. Known exploited, internet-facing3 daysCISA BOD 26-04, Table 1, shortest timeline (3 days, with forensic triage for the highest-risk rows)Binds U.S. federal agencies only; the table has 16 rows and was read from an image. Default elsewhere
1. Known exploited, other14 daysBOD 26-04 Table 1, 14 day tierSame. The BOD assigns rows by four factors; this template uses one (internet exposure)
2. Critical14 daysCyber Essentials v3.3: 14 days of release for critical or high updatesRequired for in-scope systems of a Cyber Essentials applicant; also inside the 15 days proposed for HIPAA and the one month PCI SSC FAQ 1597 gives for critical
3. High30 daysHIPAA Security Rule proposal, 90 FR 898: 30 calendar days for high risk; FedRAMP legacy: 30 daysThe HIPAA text is a proposal, not in force on 19 Nov 2026
4. Medium90 daysFedRAMP legacy playbook: Moderate risks within 90 days of discoveryLegacy FedRAMP text only
5. Low180 daysFedRAMP legacy playbook: Low risks within 180 days of discoveryLegacy FedRAMP text only
Routine baselineMonthly or more oftenCIS Controls v8, safeguards 7.3 and 7.4A recommended practice, not a regulation

Not read on 19 Nov 2026: PCI DSS v4.0.1 requirement text (the one-month figure and the number 6.3.3 come from PCI SSC FAQ 1597, not from the standard), ISO/IEC 27001 Annex A 8.8, and SOC 2 CC7.1 and CC8.1. The template makes no claim to satisfy them beyond what the other clauses show.

Why the clock starts at release

Cyber Essentials counts 14 days from release of the update, the HIPAA proposal counts from identifying the need to patch, FedRAMP's legacy text counts from discovery and BOD 19-02, now revoked, counted from initial detection. Section 4.2 of the template picks vendor release, because it is the only start date a third party can check from the vendor's own advisory. If your auditor works from a different start date, change 4.2 and say so in the cover note.

Which clause answers which requirement

  • Section 1.3 (unsupported software) answers Cyber Essentials v3.3, which requires software to be licensed and supported and removed when unsupported.
  • Section 3.1 (inventory fields) follows the characteristics listed in NIST SP 800-40 Rev. 4 section 3.2, including who administers the asset and any contractual restriction on patching.
  • Sections 4.4 and Annex A answer DORA RTS Article 10(4)(d), which asks for set deadlines and escalation procedures when they cannot be met, and NIS2 Implementing Regulation point 6.6.2, which asks for a documented reason when a patch is not applied.
  • Section 5 answers NIS2 point 6.6.1(b), testing before production, and the canary approach in NIST section 3.5.1.
  • Section 9.1 answers the 12 month review and test cadence in the HIPAA proposal (164.308(a)(4)(ii)(B)) and the annual documentation review in CIS safeguard 7.1.

Adapting it

Replace each bracket, then run three checks. First, list the frameworks that bind you and confirm no window in section 4.3 is longer than the shortest figure they set; if you hold Cyber Essentials, change class 3 to 14 days. Second, read the variant for your sector (HIPAA, PCI DSS, FedRAMP) and paste its sections over 4 and 8. Third, write the exceptions annex using the exceptions template and the steps beneath it from the procedure.

Questions

patch management policy example

The template above is a complete example: nine sections and an exceptions annex with a window table of 3, 14, 30, 90 and 180 days. Replace the square brackets with your roles, groups and windows. Sections 4 and 7 are the ones most organizations change.

patch management policy sample

Use the template block on this page as the sample. It is full text, not an outline, and every window in section 4.3 cites the clause it follows in the table above. Variants for seven situations replace specific sections.

Sources

Last reviewed 19 Nov 2026