# Purpose and Scope of a Patch Management Policy

Canonical: https://patchmanagementpolicy.com/policy-sections/purpose-and-scope/
Last reviewed: 19 Nov 2026

## 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

| Source | How scope is stated | Read 19 Nov 2026 |
|---|---|---|
| UK Cyber Essentials v3.3 | All in-scope software on servers, desktops, laptops, tablets, mobile phones, firewalls, routers, IaaS, PaaS and SaaS | Primary; NCSC PDF |
| HIPAA Security Rule proposal, 90 FR 898 | Relevant electronic information systems of covered entities and business associates | Proposal |
| EU Implementing Regulation 2024/2690 | DNS service providers, TLD registries, cloud computing and data centre providers, CDN, managed service and managed security service providers, online marketplaces and others | Primary |
| NIST SP 800-40 Rev. 4 section 3.2 | Physical and virtual computing assets, including OT, IoT and container assets | Guidance |
| CISA BOD 26-04 | Federal agency assets in any federal information system; excludes national security systems; contractors only if the contract says so | Primary; federal only |

Scope wording as read; the first column names the source, not a requirement to follow all of them.

### Sample wording

```text
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](https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/) shows.
- **Forgetting the inventory behind the scope.** Scope is only checkable against an [asset inventory](https://patchmanagementpolicy.com/policy-sections/asset-inventory-requirement/).

Continue to [roles and responsibilities](https://patchmanagementpolicy.com/policy-sections/roles-and-responsibilities/), or see the whole list at [policy sections](https://patchmanagementpolicy.com/policy-sections/).

### Sources

- [NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management](https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf), read 19 Nov 2026
- [Federal Register, HIPAA Security Rule to Strengthen the Cybersecurity of ePHI, 90 FR 898 (6 January 2025), proposed 164.308(a)(4)](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information), read 19 Nov 2026
- [EU Implementing Regulation 2024/2690, Annex, point 6.6](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690), read 19 Nov 2026
- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026
- [CISA, BOD 26-04, Prioritizing Security Updates Based on Risk (10 June 2026), Required Action 6 and Table 1](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [Patch Management Roles and Responsibilities](https://patchmanagementpolicy.com/policy-sections/roles-and-responsibilities/)
- [Asset Inventory Requirement in a Patch Policy](https://patchmanagementpolicy.com/policy-sections/asset-inventory-requirement/)
- [FedRAMP Patch Management Policy Template](https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/)
