<!-- https://cyberessentialssoftware.com/guides/the-14-day-patching-rule/ | read 18 Nov 2026 -->

Guide

# What is the 14-day patching rule in Cyber Essentials?

Cyber Essentials requires you to install updates within 14 days of release where the vendor calls the flaw critical or high risk, the CVSS v3 score is 7 or above, or the vendor gives no severity. Since April 2026 questions A6.4 and A6.5 on this rule fail the assessment automatically, as do unsupported software in scope and missing MFA on cloud services. Read 18 Nov 2026.

## What does the 14-day rule say?

The rule sits in the security update management theme of NCSC's requirements v3.3. All software on in-scope devices must be licensed and supported, removed when it becomes unsupported, set to update automatically where possible, and updated, including vulnerability fixes, within 14 days of release in three cases. The first is where the vendor describes the flaw as critical or high risk. The second is where the update fixes vulnerabilities with a CVSS v3 base score of 7 or above. The third is where the vendor gives no detail of the severity.

NCSC calls 14 days a reasonable period: any longer would be a serious security risk, while a shorter one may not be practical. It strongly recommends, but does not require, that all released updates go on within 14 days. Software here includes operating systems, applications, extensions, libraries, network software and firewall and router firmware.

## Which questions fail the assessment automatically?

IASME's article of 12 Feb 2026 lists the practices that now end an assessment whatever else you score. Question A6.4 asks whether all high-risk or critical updates and vulnerability fixes for operating systems and router and firewall firmware were installed within 14 days of release. Question A6.5 asks the same for applications, including associated files and extensions. A no to either fails the assessment.

Two more fail it automatically. Unsupported software in scope, which IASME's FAQ already treated as preventing certification. And MFA not enabled on a cloud service where it is available, free, included or paid. IASME's FAQ says you need compliance in nearly all questions, and names unsupported software in scope as the clearest bar.

## What counts as unsupported software?

NCSC defines licensed and supported software as software you have a legal right to use and that a vendor has committed to support with regular vulnerability fixes. The vendor must publish the future date when support will stop. An operating system whose support date has passed is unsupported. IASME's table showed all Windows 10 support finishing on 14 October 2025, after which only Windows 11 receives security updates.

You can keep an unsupported item only if you remove it from scope by putting it in a defined sub-set that prevents all traffic to or from the internet. The Plus test specification adds that virtual patching is not an acceptable long-term mitigation for legacy unsupported operating systems.

## How does the Plus audit check patching?

Test case 2 of the Plus Test Specification v3.2 runs an authenticated vulnerability scan on sampled devices, servers and cloud instances you manage. The Assessor looks for flaws that meet any of the same three criteria: vendor-rated critical or high, CVSS v3 of 7 or above, or no severity detail. If one of them has a vendor fix that has been available for more than 14 days, the sub-test fails.

Since April 2026 a failure triggers a retest with the original sample plus a new random one. See the [retest guide](/guides/failing-plus-and-retesting/). Patch the whole scope on the same schedule.

## What date counts: release, install or certificate?

Two dates matter. The 14 days start at the vendor's release of the fix. And IASME states that the point in time of the assessment is the date the certificate is issued, so everything in scope must be supported on that date. A device that goes out of support between your answers and the issue date is a risk.

If a vendor releases one update that covers several issues, NCSC's caution applies: if it covers any critical or high-risk issue, install it within 14 days.

## Which recent alerts show the rule in practice?

Three NCSC items in our window concern fixes that would start a 14-day clock. On 21 Oct 2026 NCSC urged action on a PHP issue, tracked as CVE-2026-109618 and CVE-2026-109619. On 28 Sep 2026 it urged prompt mitigation of Citrix NetScaler ADC and Gateway flaws, two of them under active exploitation. On 27 Aug 2026 it encouraged owners of operational technology to fix avoidable vulnerabilities in internet-exposed systems and edge devices. If you run those products, the 14 days run from the vendor's fix, not from the alert.

Whether a given flaw is rated high by the vendor is something to read in its advisory. We did not rate these three.

## How can a small company meet the rule?

Turn on automatic updates wherever the product allows it, as the requirements ask. Keep a list of devices and firmware, including the router and firewall, with a column for the last fix date. Record when each high-risk fix was released and when it went on. Platforms such as [CyberSmart](/platforms/cybersmart/) and [Sprinto](/platforms/sprinto/) say on their own pages that they record patch status per device; read the evidence they give before relying on it. See the [security update management page](/controls/security-update-management/) for the readiness checks.

## Questions from the issuers' own FAQ pages

Are there any automatic fail questions?

Unsupported software in scope fails the assessment. The April 2026 update adds MFA for cloud services and the 14-day patching questions A6.4 and A6.5.

How many of the questions do I need to get right to pass?

Compliance in nearly all questions. Unsupported software in scope prevents certification.

## Sources

- [NCSC: Requirements for IT Infrastructure v3.3](https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf) ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essential..., read 18 Nov 2026
- [IASME: changes to Cyber Essentials for April 2026](https://iasme.co.uk/articles/important-update-changes-to-cyber-essentials-for-april-2026/) iasme.co.uk/articles/important-update-changes-to-cyber-..., read 18 Nov 2026
- [NCSC: Cyber Essentials Plus test specification v3.2](https://www.ncsc.gov.uk/sites/default/files/2026-05/cyber-essentials-plus-test-specification-v3-2%20english.pdf) ncsc.gov.uk/sites/default/files/2026-05/cyber-essential..., read 18 Nov 2026
- [IASME: Cyber Essentials frequently asked questions](https://iasme.co.uk/cyber-essentials/frequently-asked-questions/) iasme.co.uk/cyber-essentials/frequently-asked-questions/, read 18 Nov 2026
- [IASME: Windows 10 update information](https://iasme.co.uk/articles/windows-10-important-update-information/) iasme.co.uk/articles/windows-10-important-update-inform..., read 18 Nov 2026
- [NCSC: critical security issue affecting PHP](https://www.ncsc.gov.uk/news/critical-security-issue-affecting-php) ncsc.gov.uk/news/critical-security-issue-affecting-php, read 18 Nov 2026
- [NCSC: Citrix NetScaler vulnerabilities exploited](https://www.ncsc.gov.uk/news/exploitation-of-vulnerabilities-affecting-citrix-netscaler-adc-and-citrix-netscaler-gateway) ncsc.gov.uk/news/exploitation-of-vulnerabilities-affect..., read 18 Nov 2026

Last reviewed 18 Nov 2026.

## Keep reading

- [Failing Cyber Essentials Plus and retesting](/guides/failing-plus-and-retesting/)
- [MFA for cloud services in Cyber Essentials](/guides/mfa-for-cloud-services/)
- [What Danzell changed in Cyber Essentials](/guides/what-danzell-changed/)
- [All guides](/guides/)
- [Platforms ranked for Cyber Essentials](/platforms/)
- [Glossary](/glossary/)
