Patch Management Policy

What is a patch management policy

A patch management policy is the document an organization approves to make patching mandatory: it names the assets covered, the owners, the deadlines by severity, how exceptions are handled and when the policy is reviewed. NIST SP 800-40 Rev. 4 (April 2022) calls the working detail a maintenance plan.

What it contains

The policy states rules; the procedure states steps. A policy says that critical fixes are installed within a set number of days and who may approve a delay. The procedure says how a technician stages, deploys and verifies. Keeping them apart means the policy changes once a year and the procedure changes when tooling does.

  1. Purpose and scope: which assets, which software, which owners.
  2. Roles: who approves, who deploys, who reports.
  3. Inventory duty: no asset is patched that is not known.
  4. Severity and windows: the deadline per severity and where the clock starts.
  5. Testing and staging, maintenance windows, exceptions, reporting, review.

Which outside text asks for which part

Policy parts and the clauses behind them, read 19 Nov 2026.
Policy partOutside textWhat it says (short quote)
Deadlines and escalationDORA RTS 2024/1774, Article 10(4)(d)"set deadlines for the installation of software and hardware patches and updates and escalation procedures in case those deadlines cannot be met"
Deadlines left to you, with a documented exceptionNIS2 Implementing Regulation 2024/2690, 6.6.1(a) and 6.6.2"security patches are applied within a reasonable time after they become available"; patches may be skipped when disadvantages outweigh benefits
A plan per group of assetsNIST SP 800-40 Rev. 4, section 3.5"Organizations should define a maintenance plan for each maintenance group"
Annual reviewCIS Controls v8, 7.1Review documentation "annually, or when significant enterprise changes occur"
Review and test every 12 monthsHIPAA Security Rule NPRM, proposed 164.308(a)(4)(ii)(B)Proposed only, published 6 Jan 2025, not in force on the day of the last check

Only the NPRM row carries a review period measured in months; DORA and NIS2 do not give a day count, so a policy that quotes them still has to choose its own. The patch window table shows which frameworks do set numbers.

What the policy leaves out

It does not carry the list of products, the names of tools or the current week's schedule. Those change faster than an approval cycle. Link them, as an appendix, from the policy sections. To write one now, follow how to write a patch management policy or fill the template.

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

what is a patch management policy

A patch management policy is the approved document that makes patching mandatory and sets who is covered, who approves, the deadline per severity, how exceptions work and when it is reviewed. The steps that carry it out go in a separate procedure. Clauses behind each part are in the table above.

what is patch management policy

It is the same document: the written rule for identifying, prioritizing, installing and verifying patches. NIST SP 800-40 Rev. 4 defines the process it governs, and the policy sections explain each part.

Sources

Last reviewed 19 Nov 2026