Patch Management Policy

Patch management policy scope

A patch policy's scope clause lists what is covered, what is excluded and who approved each exclusion. UK Cyber Essentials v3.3, effective 27 April 2026, names ten categories of in-scope items from servers to SaaS, while the proposed HIPAA rule says relevant electronic information systems.

What the section must say

  • The purpose, in one sentence: fixes are installed inside stated windows.
  • What is covered, by class of asset, not by department: operating systems, firmware, applications, libraries, container images, cloud services.
  • Systems run by a third party where you control the patch schedule.
  • Exclusions, each with a reason and an approver; an unlisted exclusion is invalid.
  • What happens to software the vendor no longer supports.

How frameworks define scope

Scope wording as read; the first column names the source, not a requirement to follow all of them.
SourceHow scope is statedRead 19 Nov 2026
UK Cyber Essentials v3.3All in-scope software on servers, desktops, laptops, tablets, mobile phones, firewalls, routers, IaaS, PaaS and SaaSPrimary; NCSC PDF
HIPAA Security Rule proposal, 90 FR 898Relevant electronic information systems of covered entities and business associatesProposal
EU Implementing Regulation 2024/2690DNS service providers, TLD registries, cloud computing and data centre providers, CDN, managed service and managed security service providers, online marketplaces and othersPrimary
NIST SP 800-40 Rev. 4 section 3.2Physical and virtual computing assets, including OT, IoT and container assetsGuidance
CISA BOD 26-04Federal agency assets in any federal information system; excludes national security systems; contractors only if the contract says soPrimary; federal only

Sample wording

1.1 This policy covers every operating system, firmware, application, library, container image and cloud service that [Company name] owns, operates or administers, and every system run by a third party where [Company name] controls the patch schedule.

1.2 Exclusions are listed in Schedule 1 with the reason, the compensating measures and the approver. A system not listed in Schedule 1 is in scope.

1.3 Software that no longer receives security updates from its vendor is removed from service or isolated and recorded in Annex A within [30] days of the vendor's end-of-support date.

Common mistakes, with the specific that exposes each

  • Leaving SaaS out. Cyber Essentials v3.3 lists SaaS next to laptops and routers as in-scope software. A scope line that says 'devices' fails that test.
  • Treating unsupported software as an exclusion. The same document requires software to be licensed and supported and removed when unsupported; a scope exclusion is not removal.
  • Copying a federal scope. BOD 26-04 reaches contractors only if their contract says so. A contractor that quotes BOD 26-04 timelines as binding has misread its own scope; FedRAMP's rules are the contractual route, as the FedRAMP template shows.
  • Forgetting the inventory behind the scope. Scope is only checkable against an asset inventory.

Continue to roles and responsibilities, or see the whole list at policy sections.

Sources

Last reviewed 19 Nov 2026