Cyber Essentials 14 day patching
UK Cyber Essentials Requirements for IT Infrastructure v3.3 (April 2026, effective 27 Apr 2026) requires updates that fix vulnerabilities described as critical or high risk, or with a "CVSS v3 base score of 7 or above", to be installed within 14 days of release. Applying every update in 14 days is advised, not required.
4.3 Patch windows
UK Cyber Essentials v3.3
| Severity | Window3143090180 days | Clock starts | Set by |
|---|---|---|---|
| Critical | 14 days of release | Release | UK Cyber Essentials v3.3, Security Update Management |
| High | 14 days of release | Release | UK Cyber Essentials v3.3, Security Update Management |
Framework clauses, read 19 Nov 2026:
- UK Cyber Essentials v3.3: Security Update Management, Requirements: 14 days of release
The clause
Under Security Update Management, the requirements apply to servers, desktop computers, laptops, tablets, mobile phones, firewalls, routers, IaaS, PaaS and SaaS. All software on in-scope devices must "be licensed and supported," be removed when it becomes unsupported (or removed from scope by a defined subset that blocks all traffic to and from the internet), have automatic updates enabled where possible, and "be updated, including vulnerability fixes, within 14 days of release" where any of three conditions holds.
- The update fixes vulnerabilities described by the vendor as critical or high risk.
- The update addresses vulnerabilities with a "CVSS v3 base score of 7 or above".
- There are no details from the vendor on the level of vulnerabilities the update fixes.
What the guidance adds
- Not mandatory, but advised: "For optimum security we strongly recommend (but it's not mandatory) that all released updates are applied within 14 days of release."
- Why 14: "14 days is considered a reasonable period to be able to implement this requirement. Any longer would constitute a serious security risk while a shorter period may not be practical."
- Bundled updates: if a vendor ships multiple issues of differing severity as one update, and it covers any critical or high-risk issue, "then it must be installed within 14 days."
- Different vendor wording: where a vendor uses other severity terms, "critical" or "high risk" means a "CVSS v3 base score of 7 or above", or identified as such by the vendor.
What changed around it
Version 3.3 became the current version on 27 Apr 2026, per the NCSC resources page, and the document's own list of changes does not touch the 14 day rule. The changes include a definition of cloud services, a statement that cloud services cannot be excluded from scope, and the introduction of the Software Security Code of Practice. Reports of question-set changes tied to the same date could not be confirmed from the documents readable on 19 Nov 2026 and are left out.
The clock differs from other frameworks in the table. Cyber Essentials counts from vendor release; the HIPAA proposal counts from the entity's identification of the need to patch; the BOD 26-04 clock starts at KEV listing or first identification on an asset.
What a policy must write
- A 14 day window from vendor release for critical or high-risk updates, stated in days and measured from release.
- The severity test copied from the scheme: vendor wording of critical or high risk, CVSS v3 base 7 or above, or no vendor detail at all (which must be treated as in scope).
- A rule for bundled updates that says one critical item in the bundle triggers the 14 days for the whole update.
- A supported-software rule: licensed, with a vendor-published end date for fixes, and removed or isolated from the internet once unsupported.
- Automatic updates enabled where possible, with the exceptions listed.
Evidence
The document tells applicants that they "might also be required to supply evidence before your Certification Body can award certification." It defines licensed and supported software as software with a vendor commitment to "regular vulnerability fixes" and a published future date when they stop. The checkable records are therefore install dates against release dates for critical and high items, the list of in-scope devices, and each product's vendor support end date. The questions a certification body asks beyond that are not in the document. A small-organization policy built on the 14 day rule is in the small business template; the other numbers sit in the Patch Window Table, and the severity and patch window section shows how to write them.
Sources
- NCSC, Cyber Essentials: Requirements for IT Infrastructure v3.3, Security Update Management (April 2026), read 19 Nov 2026
- NCSC, Cyber Essentials resources (version and effective date), read 19 Nov 2026
Last reviewed 19 Nov 2026