Patch Management Policy

Patch management policy sections

A patch management policy needs nine sections: purpose and scope, roles, asset inventory, severity and patch windows, testing, maintenance windows, emergency patching, reporting and metrics, and review and approval. Each answers named clauses read on 19 Nov 2026, and exceptions sit in an annex.

The nine sections and what each answers

Numbering matches the general policy template. Exceptions are Annex A, written in the exceptions clause.
#SectionOne lineClauses it answers (read 19 Nov 2026)
1Purpose and scopeWhat is covered, what is excluded, who approved the exclusionCyber Essentials v3.3 scope categories; NIS2 point 6.6.1; NIST SP 800-40r4 3.2
2Roles and responsibilitiesWho owns, runs, approves, installs and escalatesDORA RTS Art. 10(4)(d) escalation; NIST audiences for metrics
3Asset inventory requirementWhat the inventory records and how fresh it staysNIST 3.2; CIS Controls v8 safeguard 7.1
4Severity and patch windowsClasses, deadlines and the clock startCyber Essentials 14 days; PCI one month (FAQ 1597); HIPAA proposal 15 and 30; FedRAMP 2026 and legacy; BOD 26-04
5Testing and stagingCanary first, rollback ready, evidence keptNIS2 6.6.1(b); NIST 3.5.1; DORA Art. 10(4)
6Maintenance windowsWhen installs happen and when they are forcedNIST 3.5.1; CIS 7.3 and 7.4 (monthly)
7Emergency patching clauseWhen windows are suspended and who decidesNIST 3.5.2; DORA Art. 10(4)
8Reporting and metricsWhat is measured, for whom, how oftenNIST 3.6; CIS 7.2 monthly review
9Review and approvalAnnual review and the events that force oneHIPAA proposal 12 months; CIS 7.1 annual; BOD 26-04 Table 1 reassessment

Why this order

Scope and roles come first because every later clause needs a subject and an owner. The inventory precedes the windows because a window can only be met for an asset the policy knows about; NIST SP 800-40 Rev. 4 puts inventory second in its planning steps, before it defines risk response scenarios and maintenance plans. Testing and maintenance windows follow the deadlines because they are the means of meeting them. Emergency patching comes after the routine rules since it is defined as the departure from them. Reporting and review close the loop: a policy with no measurement and no review date cannot show it was followed, and the proposed HIPAA rule would require the review and test at least once every 12 months.

Which sections frameworks leave to you

Several frameworks set no number and ask only for a documented process. EU Regulation 2024/2690 point 6.6.1(a) asks for patches within a reasonable time; DORA's RTS asks financial entities to set their own deadlines; NYDFS 500.5(c) asks for timely remediation prioritized by risk. For these, section 4 of your policy is the requirement, and an auditor will test you against what you wrote. The patch window table lists the numbers that exist and says which frameworks set none.

Do not put the decision on whether to accept a risk into the policy body. The policy carries an exceptions annex that records the departure; the grounds and fields are in the exceptions template.

Sources

Last reviewed 19 Nov 2026