To pass Cyber Essentials, you must install security updates within 14 days of release when they fix high or critical vulnerabilities. You must also run only licensed, supported software and turn on automatic updates wherever you can. Those rules come from the NCSC's Cyber Essentials Requirements for IT Infrastructure v3.3. This guide explains what they mean for a small team, how to build a process that meets them, and what to do with kit that cannot be patched.
Key Takeaways
- The 14-day window applies to updates that fix vulnerabilities rated critical or high by the vendor, scored CVSS v3 7.0 or above, or released with no severity information.
- The rules cover operating systems, applications, extensions, libraries and router or firewall firmware, not just Windows updates.
- Unsupported software must be removed from devices, or removed from scope by isolating it from the internet entirely.
- A fixed monthly patch day is too slow on its own. Automatic updates plus a quick weekly check is the most practical pattern for small teams.
- Keep simple records of what you patched and when, so you can answer the questionnaire with confidence.
Table of Contents
- What Cyber Essentials requires for patching
- What is in scope for patching
- Building a patching process that works for a small team
- When something cannot be patched
- Common patching mistakes before an assessment
- Patching affordably as a startup, school or charity
- Moving from Cyber Essentials to Cyber Essentials Plus
- How we can help
- FAQ
- Sources
What Cyber Essentials requires for patching
The scheme calls this control Security Update Management. The v3.3 requirements set out four things for all in-scope software:
- It must be licensed and supported.
- It must be removed from devices when it becomes unsupported.
- Automatic updates must be enabled where possible.
- Updates, including vulnerability fixes, must be applied within 14 days of release in the cases below.
The 14-day clock applies when an update does any of the following, according to the NCSC requirements document:
- fixes a vulnerability the vendor describes as critical or high risk;
- addresses a vulnerability with a CVSS v3 base score of 7 or above;
- comes from a vendor that gives no details of the vulnerability's severity.
That last point catches people out. If a supplier ships an update with a note saying only "security improvements", you treat it as urgent. The sensible default is to install everything promptly rather than spend time debating severity.
What counts as a fix
A fix does not always mean a vendor patch. Ian Glennon, quoted by IT Pro, points out that a robust mitigation applied while a patch is tested also counts. He lists configuration changes, registry updates, disabling a vulnerable service and deploying a specific script as valid fixes. This matters when a patch is large and your line-of-business software needs testing first: you can close the exposure within 14 days with a mitigation, then roll out the full update on your own schedule.

What changed in 2026
Version 3.3 of the requirements was published in April 2026 alongside the move to the new assessment model. Patching is one of the areas where the standard became less forgiving. Jon Bance of Leading Resolutions told IT Pro that smaller IT teams will need to be "much more deliberate" about tracking, prioritising and evidencing patching across endpoints, servers and cloud services, and that processes once tolerated as good enough will no longer line up with the standard. We cover the wider changes, including multi-factor authentication, in our guides to the April 2026 Cyber Essentials changes and v3.3 hard fails.
What is in scope for patching
Many small organisations assume patching means Windows Update on the office PCs. The scope is wider. The NCSC says the Security Update Management control applies to servers, desktop computers, laptops, tablets, mobile phones, firewalls, routers, and IaaS, PaaS and SaaS services (see the requirements document).
The requirements apply to in-scope devices and software that can accept incoming internet connections, make outbound internet connections, or control the flow of data between such devices and the internet. Software, in this context, includes:
- operating systems;
- commercial off-the-shelf applications such as browsers, PDF readers and office suites;
- extensions, such as browser add-ons;
- interpreters, scripts and libraries;
- network software;
- firewall and router firmware.
The items people forget
In our experience of assessing small organisations, the same few items turn up as gaps:
- Router and firewall firmware. Often installed once and never touched. Check the vendor's site and set a reminder.
- Browser extensions. Each one is software that must be supported and updated.
- Phones and tablets. Staff devices used for email are in scope. Make sure the operating system is supported and set to update automatically.
- Old laptops in a cupboard. If a device is in scope and still connects, it needs to be current. If it is not used, remove it from the scope or retire it.
- Cloud services. SaaS is in scope too, but the supplier normally handles the patching. Your job is to know which services you use and that you have configured them properly.
Building a patching process that works for a small team
You do not need an enterprise toolset. You need a repeatable routine, a list of what you own, and a record of what happened. Our guides on writing a patch management policy and vulnerability prioritisation go deeper. This is the short version.
Step 1: Know what you have
List every device and application in scope: laptops, desktops, phones, servers, the router and firewall, and key applications. A spreadsheet is fine. Include the operating system and its support status. You cannot patch what you have forgotten, and the assessment asks about it.
Step 2: Update by default

The NCSC's vulnerability management guidance recommends a policy of updating by default: apply software updates as soon as possible, ideally automatically. Turn on automatic updates for operating systems, browsers and common applications. This single step removes most of the effort.
The same guidance gives best-practice timescales that are tighter than the Cyber Essentials minimum:
| Type of software | NCSC best-practice timescale | Cyber Essentials requirement |
|---|---|---|
| Internet-facing services and software | 5 days | 14 days for high or critical fixes |
| Operating systems and applications | 7 days | 14 days for high or critical fixes |
| Internal or air-gapped services and software | 14 days | 14 days for high or critical fixes |
Aiming for the NCSC's shorter figures gives you headroom. If you aim for exactly 14 days, one holiday or one absent IT person can put you over.
Step 3: Stage the rollout rather than delaying it
Testing is a common reason for slow patching. The NCSC's answer is that testing does not have to slow you down. Vendors test their own updates, and you can test on your own systems gradually, using a phased or staged rollout across your estate, or a canary deployment to a small group of users. That approach also lets you pause or roll back if something breaks.
For a ten-person business, this can be as simple as letting two people take updates first, then everyone else a day or two later.
Step 4: Check weekly, not monthly
A fixed monthly patch day is a trap. If a critical update lands the day after your patch day, it waits almost a month, which is about double the allowed window. A short weekly check closes that gap:
- Confirm automatic updates are still switched on and have completed.
- Look for devices that are offline or have been pending a restart.
- Check vendor notices for your router, firewall and key applications.
- Record any exceptions and who owns them.
Restarts matter. An update that is downloaded but waiting for a reboot is not installed. Ask staff to restart at least weekly, or enforce restarts outside working hours.
Step 5: Keep evidence
Cyber Essentials is a self-assessment verified by a certification body, so the answers you give need to be true on the day and defensible later. Keep:
- your device and software inventory with dates last checked;
- screenshots or exports showing automatic updates enabled;
- a log of exceptions, mitigations and the date each was closed;
- your patch management policy, even if it is one page.
You will not usually be asked to upload these for basic Cyber Essentials, but the records make completing the questionnaire quick and give you something to show a customer or insurer. Cyber Essentials Plus is different: a technical auditor tests your devices directly, so what you say must match what the scan finds.
When something cannot be patched
Legacy kit is the hardest part of this control. The NCSC requirement is clear: unsupported software must be removed from devices, or removed from scope using a defined sub-set that prevents all traffic to or from the internet. There is no third option of leaving it and hoping.
Your practical choices are:
- Upgrade or replace. Move to a supported version of the operating system or application. This is usually the cheapest long-term answer.
- Remove the software. If nobody uses that old application, uninstall it from the device.
- Isolate it. Place the device in a sub-set of your network that cannot send or receive internet traffic, and document how that is enforced. A machine controlling lab equipment or a specialist production tool is a typical case.
- Mitigate in the meantime. For a vulnerability with no patch yet, a configuration change, disabled service or script can count as a fix within the window.
For business-critical systems, the NCSC says to balance rollout timescales against availability. Schedule maintenance windows rather than skipping updates.
If you suspect a vulnerability is being exploited
Speed matters more than process here. The NCSC advises investigating for signs of compromise and, if possible, using an assured Cyber Incident Response provider. If that is not possible, the affected system should be erased or destroyed and rebuilt as new. If you need help in a hurry, our incident response service is staffed by the same people who run our testing.
Common patching mistakes before an assessment
The patching questions in the Cyber Essentials assessment are among the ones that can end an attempt, because a "no" on a requirement flagged as an automatic fail means the assessment does not pass. We also see these avoidable problems when we review clients' answers:
- Answering from memory. "We think updates are on" is not an answer. Check a sample of devices first.
- Forgetting firmware. Routers and firewalls are in scope and are rarely updated.
- Counting only Windows. Third-party applications such as browsers, PDF tools and conferencing software need updating too.
- Ignoring personal devices used for work. If staff read company email on a phone, it is in scope.
- Leaving end-of-life software installed. An old copy of an office suite or an out-of-support operating system will cause a failure.
- Relying on a monthly cycle. See the weekly check above.
If you are unsure where you stand, a gap analysis for Cyber Essentials costs £300 and shows where you would fail before you pay for the assessment. Our Cyber Essentials checklist is a free way to do a first pass yourself.
Patching affordably as a startup, school or charity
Budgets are tight, and patching is mostly about habit rather than expensive tools. A few practical points:
- Use what you already have. Windows, macOS, iOS, Android and most browsers have built-in automatic updates. Microsoft 365 and Google Workspace handle their own service patching.
- Standardise devices. Fewer operating systems and applications means fewer things to track.
- Name one owner. Even in a five-person firm, one person should own the weekly check, with a deputy.
- Ask your IT provider for evidence. If an MSP manages your devices, ask them to show you update reports. If you are an MSP, we offer partnership models including white-label delivery.
- Check for funded support. The NCSC has offered 20 hours of free security advice and support through the Funded Cyber Essentials Programme to some small charities and legal-aid businesses. Check the current eligibility rules before relying on it.
Schools and colleges often have large, mixed estates, with student devices, shared machines and older teaching equipment. Our guide to Cyber Essentials for schools covers the scope questions, and the college financial handbook page explains the funding context.
Moving from Cyber Essentials to Cyber Essentials Plus
Basic Cyber Essentials relies on your answers. Cyber Essentials Plus adds a hands-on technical audit, where an assessor checks a sample of your devices and tests whether they are genuinely up to date and correctly configured. Patching is one of the first things that shows up. If a sampled laptop is missing a high-severity update older than 14 days, that is a problem you will see on the day.
That is why a tidy, evidenced patching routine pays off twice: it makes the basic assessment straightforward and the Plus audit uneventful. Not sure which you need? Our comparison of Cyber Essentials and Cyber Essentials Plus explains it, and the Cyber Essentials Plus page covers how we deliver it.
How we can help
We are a CREST-accredited company and a Certification Body for Cyber Essentials. You deal directly with the testers and assessors, not a sales team, and we give plain-English, proportionate recommendations.
Our published Cyber Essentials certification fees run from £320 to £600 depending on organisation size, and a gap analysis is £300. If you need a result quickly for a tender, the urgent turnaround option adds £100. Details are on our Cyber Essentials page, and our urgent Cyber Essentials service explains how same-day assessment works.

If you want patching to be a managed, ongoing job rather than a weekly chore, our vulnerability management service identifies and prioritises what needs fixing so you can meet the 14-day window with evidence to show for it.
FAQ
Does Cyber Essentials require patching within 14 days?
Yes, for updates that fix vulnerabilities the vendor rates critical or high, that score 7 or above on CVSS v3, or that come with no severity information. The requirement comes from the NCSC's v3.3 document. Install other updates promptly too, ideally automatically.
Do we need a patch management tool?
The requirements do not name a tool. For a small organisation, built-in automatic updates, a device inventory and a weekly check can meet the standard. Larger or more varied estates usually benefit from a central management tool that reports on update status.
Does the 14-day rule apply to routers and firewalls?
Yes. Firewall and router firmware are listed as software in the NCSC requirements, so they need to be supported and updated within the same window when a fix addresses a high or critical vulnerability.
What if an application is out of support but we still need it?
Remove it from devices, or move it into a defined sub-set of your network that prevents all traffic to and from the internet. Many organisations replace the application instead, since isolation has to be documented and maintained.
Is a monthly patch cycle enough?
On its own, usually not. A critical update released just after your monthly patch day would wait close to a month, beyond 14 days. Combine automatic updates with a weekly check.
Sources
- NCSC: Cyber Essentials Requirements for IT Infrastructure v3.3
- NCSC: Vulnerability management, update by default
- IT Pro: What businesses need to know about the update to Cyber Essentials
- Computing: NCSC Cyber Essentials to be offered free to some small organisations
Recommended
- Patch Management Policy: What to Include and How to Write It
- Cyber Essentials April 2026 Changes (v3.3 / Danzell)
- Cyber Essentials Checklist: What You Need to Pass (2026)
This article was created with assistance of AI. We never use AI with your data unless given explicit permission.
