Cyber Essentials is the UK government-backed scheme that shows your business has the basic technical controls in place to protect itself against the most common online attacks. More and more customers, public sector buyers and insurers ask for it, and for many small businesses the assessment goes smoothly until it reaches one subject: old software. The Windows 10 PC in the back office, the Access database that runs the bookings, the router nobody has touched in years.
The rules on this are strict, and they became stricter in April 2026. This guide explains what Cyber Essentials actually requires of your software, which older systems commonly cause problems, and the realistic options when something will not pass, from a simple upgrade to modernising a legacy system that the business still depends on.
This article is about systems rather than security or compliance advice. Your Certification Body or assessor is the right person to confirm exactly how the requirements apply to your organisation.
What Cyber Essentials is and who asks for it
The scheme is run by the National Cyber Security Centre (NCSC), with IASME as its delivery partner, and it covers five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. The NCSC’s Cyber Essentials overview sets out the two levels:
- Cyber Essentials is a verified self-assessment. You answer a set of questions about your IT, and an assessor from a Certification Body marks your answers.
- Cyber Essentials Plus adds a technical audit. An assessor runs internal and external vulnerability scans and checks a sample of your devices, so any gaps in your answers will show up.
Certificates last 12 months. IASME’s published prices for the self-assessment are £320 plus VAT for organisations with up to 9 staff, £440 for 10 to 49, £500 for 50 to 249 and £600 for 250 or more. Cyber Essentials Plus is quoted individually by the Certification Body. Certification is required for many central government contracts and across the Ministry of Defence supply chain, and plenty of private sector buyers now ask for it too.
The rule that catches old software
The current version of the NCSC’s Cyber Essentials requirements for IT infrastructure is version 3.3, and assessments now use the question set known as Danzell, which came into use on 27 April 2026. Under security update management, all software in scope must be:
- Licensed and supported. The vendor must still be producing regular fixes for security weaknesses. Once a product reaches its end of support date, it no longer qualifies.
- Removed or taken out of scope when it becomes unsupported. Either it comes off your devices, or it is moved to a separate, well-defined part of your network that blocks all traffic to and from the internet.
- Kept up to date. Automatic updates should be switched on where possible, and critical or high-risk updates must be applied within 14 days of release. The requirements define these as fixes with a CVSS v3 score of 7 or more, or any fix where the vendor gives no severity details.
IASME’s guidance is blunt: unsupported software in scope means an automatic fail. Under Danzell, failing to apply critical and high-risk updates within 14 days is also an automatic fail, where previously it might have counted as a lesser non-compliance. So “it still works fine” is not an answer that will get an old system through.
What counts as software for Cyber Essentials
The definition is wider than most people expect. In Cyber Essentials, software includes:
- operating systems, such as Windows, macOS, iOS and Android;
- applications, including office software, accounting packages and line-of-business systems;
- browser extensions and plug-ins;
- interpreters, scripts and libraries that programs rely on;
- the firmware on routers and firewalls, which acts as their operating system.
There are some important details about scope. Commercial web applications that are publicly accessible on the internet are in scope, but the custom, bespoke components of a web application are not. Cloud services cannot be excluded from scope, and under Danzell, multi-factor authentication must be switched on for every user and administrator of every cloud service that offers it, or the assessment automatically fails. A scope that leaves out the devices your staff actually use is not acceptable, and the final boundary has to be agreed with your Certification Body.
The old software small businesses commonly still run
These are the products and situations that most often cause trouble for a Cyber Essentials assessment at the moment. Check the vendor’s own lifecycle pages for anything not listed here.
- Windows 10. Support ended on 14 October 2025. IASME treats Windows 10 as compliant only if the device is enrolled in Microsoft’s Extended Security Updates (ESU) programme, which requires version 22H2. Businesses buy ESU a year at a time, for up to three years. Microsoft’s Extended Security Updates FAQ lists the end dates: the second year runs to 12 October 2027 and the third to 10 October 2028. Our guide to Windows 10 end of support and your business software goes into more detail.
- Windows Server 2012 and 2012 R2. The final year of Extended Security Updates ended on 13 October 2026, so a server still running either is unsupported.
- Older Microsoft Office. Office 2016 and Office 2019, including Access, Excel and Outlook from those versions, reached end of support on 14 October 2025. Office LTSC 2021 followed on 13 October 2026.
- Websites and web apps on old platforms. If an off-the-shelf platform such as a content management system is in your scope, the platform, its plugins and the PHP version beneath it all need to be supported. PHP 8.2 receives security fixes only until 31 December 2026.
- Old routers and firewalls. A router whose manufacturer has stopped releasing firmware updates is unsupported software, however reliable it seems.
- Older bespoke systems. The custom code may be fine, but older applications often depend on frameworks, runtimes or libraries that have themselves gone out of support, and those components count as software.

Start with an inventory
You cannot judge what will pass Cyber Essentials until you know what you have. IASME’s guidance stresses the value of a software asset list, and it is the single most useful piece of preparation. A spreadsheet is fine to begin with. For every device, record:
- what it is and who uses it;
- the operating system and exact version;
- the applications installed, with versions;
- whether automatic updates are switched on;
- the vendor’s end of support date for each item.

Then do the same for your network equipment and your cloud services, noting for each cloud service whether multi-factor authentication is available and switched on for everyone. This is also the moment to spot software that nobody uses any more. Removing it is the cheapest fix there is.
If you also run a website, our guide to keeping your website secure covers updates, backups and access in more detail.
Your options when something will not pass
Once the inventory is done, every unsupported item needs one of the following. They are listed roughly from quickest to most involved.
1. Remove it
Unsupported software that is no longer needed, a forgotten browser extension, an unused PC in a cupboard: uninstall it, wipe it or recycle it. It is surprising how often this deals with half the list.
2. Update or upgrade it
Many problems are simply a case of moving to the current version: a supported release of Windows, a Microsoft 365 subscription instead of Office 2016, a router firmware update or a replacement router. For Windows 10 devices that cannot run Windows 11, ESU buys time, but it is a bridge rather than a destination.
3. Replace it with a supported product
If an off-the-shelf or cloud product now does what your old system does, moving to it may be the simplest route. Factor in the time to migrate your data and retrain staff, not just the subscription.
4. Modernise the system you depend on
Sometimes the old system is doing something specific to your business that no product does well, and replacing it would mean changing how you work. In that case, the answer is to move it onto supported foundations, either by updating the code and the components it relies on or by rebuilding it. Our guide to whether to rebuild, refactor or replace legacy software explains how to choose.
5. Take it out of scope
If something genuinely cannot be updated or replaced yet, such as a PC that controls a piece of machinery, it can be moved into a separate sub-set of your network using a firewall or a VLAN, so that it cannot send or receive any internet traffic. Your Cyber Essentials certificate then describes the scope precisely, for example “whole organisation excluding the workshop network”. IASME’s guidance on navigating the pitfalls of legacy software notes that it is not unusual to need professional help with this.

Segregation is a legitimate option, but it is not a loophole. The equipment outside your scope is still vulnerable, and anything that needs the internet, email or cloud services cannot be treated this way. Think of it as a holding position while a proper fix is planned.
An illustrative example: the database nobody wants to touch
Here is an illustrative example. The business is made up, but the situation is one we come across often.
A lettings agency with 12 staff wants Cyber Essentials because a housing association it works with has asked for it. The laptops run Windows 11 and the team uses Microsoft 365, so most of the assessment looks straightforward. The problem is a rent and maintenance database built in Access years ago, which runs on one desktop PC with Access 2016 because “it works and nobody wants to break it”. Access 2016 has been unsupported since October 2025, so that PC cannot stay in scope as it is.
The agency looks at its options. Taking the PC off the network is not practical, because staff use the database all day. Opening it in the current version of Access is worth testing first, since some older databases move across with little work, but this one has years of patched-on forms and macros. In the end the agency moves the data into a small web application with proper user logins, which also lets staff use it from the laptops they already have.
The lesson is not that every old database needs rebuilding. It is that the decision is far easier when it is made calmly, months before a renewal date, rather than in the week a tender is due.
Plan ahead, not at renewal time
Because Cyber Essentials certificates last 12 months and vendors announce end of support dates years in advance, most software problems can be seen coming. A few habits make each renewal easier:
- review your inventory every six months and add any end of support dates in the next 18 months to your calendar;
- budget for replacing hardware and software before support ends, not after;
- when you commission bespoke software, ask how its frameworks and libraries will be kept up to date, and who will do it;
- read the requirements and the question set before you start the assessment, so you know exactly what will be asked.
Once you begin, IASME’s guidance gives you six months to complete the assessment, and a short window of two working days to correct answers and resubmit if you fail. Neither is long enough to replace a core business system, which is why the planning matters. Building on modern, maintained technology from the start helps too. When we built the React website and back-end admin dashboard for Eastern Procurement, a not-for-profit procurement framework provider owned by social housing providers in the East of England, the aim was a system its own team could keep up to date.
Cyber Essentials and old software: common questions
Can we pass Cyber Essentials with Windows 10 computers?
Only if each Windows 10 device is enrolled in Microsoft’s Extended Security Updates programme, which needs version 22H2, and is receiving those updates. Without ESU, Windows 10 is unsupported and the assessment will fail.
Does bespoke software stop us passing Cyber Essentials?
Not automatically. The bespoke parts of a web application are out of scope, but the operating system, frameworks, libraries and any commercial software it runs on must all be supported and kept up to date. Older bespoke desktop systems are the most likely to depend on components that are out of support.
Can we just leave an old PC out of the assessment?
Only by technically separating it, using a firewall or VLAN, so it has no route to or from the internet, and describing that clearly in your scope. You cannot simply leave it off the list, and you cannot exclude cloud services or the devices your staff use day to day.
We failed on one unsupported item. What now?
Speak to your Certification Body straight away, because the window to correct and resubmit is short. If the item can be removed or updated quickly, do that. If not, you will need to fix the underlying problem and apply again.
Is Cyber Essentials Plus stricter about old software?
The requirements are the same, but Cyber Essentials Plus checks them. The vulnerability scans and the sample of devices will find missing updates and unsupported software that a self-assessment might have overlooked.
The bottom line
Cyber Essentials does not ask small businesses for anything exotic, but it is uncompromising about old software. Everything in scope has to be supported and kept up to date, and since April 2026 the penalties for getting that wrong are automatic. An honest inventory, made well before your assessment, tells you what needs removing, upgrading, replacing or modernising.
If an old system is the thing standing between you and your certificate, tell us what it does or call us on +441482 212499. We will help you work out whether it can be updated, should be replaced, or is worth rebuilding on foundations that will keep passing for years to come.







