# Small Business Patch Management Policy Template

Canonical: https://patchmanagementpolicy.com/templates/small-business/
Last reviewed: 19 Nov 2026

## Patch management policy for small business

A company under 50 people can run a patch policy on one number: 14 days from release for any update the vendor calls critical or high, the rule in UK Cyber Essentials v3.3, effective 27 April 2026. This variant keeps that window, a monthly check, and a written record, in full text below.

### What changes from the general policy and why

The general policy has five severity classes, rings and a coordinator role. A team without security staff cannot staff those, so this variant keeps three rows and one named person. Everything dropped is dropped for a reason that can be checked.

- Medium and low windows (90 and 180 days) are gone. Without a vulnerability scanner nobody can sort medium from low, and CIS Controls v8 safeguards 7.3 and 7.4 ask for operating system and application updates monthly or more often anyway.
- Classes 2 and 3 merge into one 14 day row, because [Cyber Essentials v3.3](https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf) puts critical and high updates in the same 14 day rule. The general policy's 30 days for high would fail a Cyber Essentials check.
- The scope line names SaaS, IaaS and PaaS next to laptops and routers because the Cyber Essentials requirement lists exactly these categories, along with servers, desktops, tablets, mobile phones and firewalls.

### What Cyber Essentials requires, read exactly

Updates must be installed within 14 days of release where the update fixes vulnerabilities the vendor describes as critical or high risk. The document says applying all updates within 14 days is recommended but not mandatory, and that a single update covering any critical or high issue must still go on in 14 days. It also requires software to be licensed and supported and removed when unsupported. Read 19 Nov 2026 from the NCSC PDF; the NCSC resources page confirms v3.3 as the current version, effective 27 April 2026.

A date check shows how little time that leaves. Microsoft publishes its monthly security update on the second Tuesday of the month; the next one is 8 December 2026 ([Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/update/release-cycle)). Fourteen days from then is 22 December 2026, so a monthly check done on 9 December has a two week margin and a check done on 23 December has already failed it for anything released on the 8th.

### The template

```text
## Small business variant: paste over the same-numbered sections of the general policy

## 1. Purpose and scope

1.1 [Company name] keeps its computers, phones, network devices and cloud services up to date so that known security flaws are closed quickly.
1.2 Scope: laptops, desktops, servers, tablets, mobile phones, firewalls, routers, and every cloud service (IaaS, PaaS and SaaS) that staff use for company work, whether the company or a person owns the device. Personal devices that open company data are in scope.
1.3 Software that the maker no longer supports is removed. Where it cannot be removed, the IT lead records why and when it will go.

## 2. Roles and responsibilities

2.1 IT lead ([name], backup [name]): owns this policy and the monthly check. If an outside IT provider ([provider]) does the work, the IT lead is still accountable and keeps the provider's monthly written report.
2.2 Every employee: installs prompted updates within [3] days and restarts when asked.
2.3 Director ([name]): hears about any update that is more than 14 days late.

## 3. Asset inventory

3.1 One spreadsheet or tool lists every device and cloud service, its owner, whether it updates itself, and the date of the last check.
3.2 A new device is added on the day it is issued.

## 4. Severity and patch windows

| Update type | Window |
|---|---|
| Fixes a flaw the maker calls critical or high | 14 days from release |
| Listed as exploited in the CISA Known Exploited Vulnerabilities catalog | 3 days if the system is reachable from the internet, otherwise 14 days |
| Everything else | Next monthly cycle |

4.1 Automatic updates are switched on wherever the product allows it. The IT lead checks every month, on the Wednesday after the second Tuesday, that nothing is waiting.

## 5. Testing and staging

5.1 The IT lead's own device and one volunteer's device get updates first, then everyone else after [2] working days. Servers are updated outside working hours with a backup taken first.

## 6. Maintenance windows

6.1 Servers and network devices: [day, time]. Laptops: restarts allowed any weekday before [time].

## 8. Reporting and metrics

8.1 Monthly note to the director: devices checked, devices late, reason, date fixed.

```

### Records an assessor will ask for

The variant produces three records without extra tooling: the device list (section 3.1), the monthly note (section 8.1) and, if an outside provider patches, that provider's monthly report. For a larger practice, move to the [general policy](https://patchmanagementpolicy.com/templates/patch-management-policy-template/) once you add a dedicated security role, and read how the monthly rhythm works in [how often to patch](https://patchmanagementpolicy.com/guides/how-often-to-patch/). Where a laptop will not restart for weeks, the [systems that cannot reboot](https://patchmanagementpolicy.com/patching/systems-that-cannot-reboot/) page covers what to write instead.

### 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
- [NCSC, Cyber Essentials resources page (v3.3 effective 27 April 2026)](https://www.ncsc.gov.uk/cyberessentials/resources), read 19 Nov 2026
- [Microsoft Learn, Update release cycle for Windows clients](https://learn.microsoft.com/en-us/windows/deployment/update/release-cycle), read 19 Nov 2026
- [CIS Controls v8 guide (August 2023), Control 7, safeguards 7.1 to 7.7](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026
- [CISA, Known Exploited Vulnerabilities Catalog page](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/)
- [Patch Management Policy Template Set, 10 Documents](https://patchmanagementpolicy.com/templates/)
- [How Often to Patch: Cadences From the Clauses Read](https://patchmanagementpolicy.com/guides/how-often-to-patch/)
- [Severity and Patch Windows: What Each Framework Sets](https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/)
