Cyber Essentials v3.3 requires all in-scope software to be licensed and supported. Unsupported software must be removed or moved to a sub-set, separated by a firewall or VLAN, that prevents all traffic to or from the internet. Paying for extended security updates keeps a product supported. If the isolated sub-set still reaches the internet, only partial certification is possible.
Key takeaways
- NCSC Requirements v3.3 say all software on in-scope devices must be licensed and supported, and removed when it becomes unsupported or moved to a defined sub-set that prevents all traffic to or from the internet.
- A6.3 and A6.6 carry no automatic-fail wording in the Danzell question set, but IASME's FAQ says any company using unsupported software in scope will fail to achieve certification.
- A6.7 says that if an out-of-scope sub-set remains connected to the internet, you cannot achieve whole-company certification and must select Partial Organisation in A2.1.
- Extended security updates keep a product supported while you pay for them; the A6.1 guidance applies this to Windows 10 after 14 October 2025.
- The CE Plus test specification v3.2 says virtual patching will not be recognised as compliance for legacy unsupported operating systems.
- The rule
- Licensed and supported, or removed, or moved to a sub-set that prevents all traffic to or from the internet (v3.3)
- Sub-set
- Part of the organisation whose network is segregated from the rest by a firewall or VLAN (v3.3 definition)
- Questions
- A6.3 and A6.6 (not automatic fails), A6.7 (notes on how you isolate), A2.1, A2.2, A2.2.1 and A2.2.2 (partial scope and how sub-sets are built)
- Extended support
- The A6.1 guidance accepts Windows 10 enrolled in Extended Security Updates; our interpretation is that any vendor extended support programme counts while you keep the subscription
- Not accepted
- Virtual patching for legacy unsupported operating systems (CE Plus test specification v3.2)
Almost every organisation has one: the old server that runs the stock system, the PC attached to a lab instrument, the accounts package nobody has upgraded since 2015. Cyber Essentials does not have a hardship exemption for these. It does give you three ways to deal with them. This guide explains the rule, the questions it appears in, and how to decide between replacing, isolating and descoping. Scheme facts come from the NCSC Requirements for IT Infrastructure v3.3 and the IASME Danzell question set v16.3, checked on 9 November 2026.
What does Cyber Essentials say about unsupported software?
The scheme requires all software on in-scope devices to be licensed and supported, and unsupported software to be removed or moved out of scope.
The Requirements for IT Infrastructure v3.3 say all software on in-scope devices must:
- "be licensed and supported"
- "be removed from devices when it becomes unsupported, or removed from scope by using a defined sub-set that prevents all traffic to or from the internet"
v3.3 defines licensed and supported software as software you have a legal right to use "and that a vendor has committed to support by providing regular vulnerability fixes. The vendor must provide the future date when they will stop providing these." Software includes "operating systems, commercial off-the-shelf applications, extensions, interpreters, scripts, libraries, network software and firewall and router firmware". That list is why an old Java runtime or a forgotten browser plug-in counts as much as an old operating system.
Which questions ask about legacy systems?
Five questions in the security update management section cover it, plus A2.1 to A2.2.2 if you descope part of the network: A6.1 and A6.2 ask whether everything is supported, A6.3 and A6.6 ask about unsupported software, and A6.7 asks how you took it out of scope.
| Question | What it asks | Compliant answer | Automatic fail? |
|---|---|---|---|
| A6.1 | Are all operating systems, including router and firewall firmware, vendor-supported? | Yes | No |
| A6.2 | Is all software supported, including frameworks and extensions? | Yes | No |
| A6.3 | Are any in-scope software or cloud services unlicensed or unsupported? | No | No: a yes means the requirement is not met |
| A6.6 | Have you removed software that is no longer supported? | Yes | No: a no means the requirement is not met |
| A6.7 | Where you need unsupported software, have you moved it out of scope? Explain how | A notes answer describing the sub-set, or a statement that no unsupported software is used | No |
| A2.2.1 | Describe any networks excluded from the assessment by creating a sub-set (asked when you choose partial scope) | A description of each excluded network; IASME does not publish it | No |
| A2.2.2 | Describe how each sub-set was created | "Sub-sets must be created using a firewall or VLAN"; security groups, microsegmentation and software-based methods "are not compliant" | No |
A6.3 and A6.6 are not automatic fails in the question set. That does not make them optional: the question set's introduction to security update management says that if an in-scope device uses an unsupported operating system without regular vulnerability fixes, "then you will not be awarded certification". A non-compliant answer means the licensed-and-supported requirement is not met, and the assessor will expect the software to be upgraded, removed or isolated before certification. Our post on the answers that fail automatically explains the difference.
How do you decide whether to replace, isolate or descope?
Replace or upgrade if you can, isolate with no internet traffic if the business needs the system, and descope only if isolation is not possible and a partial certificate is acceptable.
| Option | When it fits | What the scheme requires | Effect on certificate |
|---|---|---|---|
| Upgrade or replace | A supported version exists and the cost is manageable | Supported software, updates within 14 days for critical fixes | None |
| Buy extended support | The vendor sells an extended security updates programme | Maintain the subscription (A6.1 guidance names Windows 10 ESU; other programmes are our interpretation) | None, while the subscription runs |
| Remove | The software is no longer needed | Uninstall it (A6.6) | None |
| Isolate in a sub-set with no internet | The system must stay and does not need the internet | A sub-set separated by firewall or VLAN that "prevents all traffic to or from the internet" (A6.7) | Whole organisation still possible in our reading of A6.7; confirm with your Certification Body, because A2.1 describes networks excluded by firewall or VLAN as partial |
| Descope a sub-set that keeps internet access | The system must stay and needs the internet | Justify the partial scope to your assessor; describe it in A2.2, A2.2.1 and A2.2.2 | Partial Organisation (A2.1) |
The A6.7 guidance is explicit: "If the out-of-scope sub-set remains connected to the internet, you will not be able to achieve whole company certification and you must select 'Partial Organisation' in question A2.1." v3.3 also says you "will need to justify the reason for a partial scope to your assessor", and that whole-organisation scope gives "the best protection" and maximises customer confidence.
What counts as a sub-set with no internet traffic?
A sub-set is a part of your network segregated from the rest by a firewall or VLAN, and for unsupported software it must block all traffic to and from the internet.
That is the v3.3 definition, and the A6.7 guidance repeats it. A separate VLAN with a rule that still allows the old server to fetch updates or reach a supplier's portal does not qualify, because traffic still flows to the internet. In our reading, remote access by a supplier into the sub-set is also internet traffic. A2.2.2 adds that sub-sets must be built with a firewall or VLAN; security groups, microsegmentation and software-based methods "are not compliant".
Name the system and why it is still needed. Say how it is separated (a dedicated VLAN, a firewall interface). Say what the firewall rules allow, and confirm that no rule permits traffic to or from the internet. Say how staff use it, for example from a dedicated terminal inside the sub-set. Assessors query vague answers such as "it is on a separate network".
An example A6.7 answer, with invented names, that covers each point:
Stock control server SRV-STOCK01 runs Windows Server 2012 R2, which is out of vendor support. We keep it because the stock application has no supported version; its replacement goes live in March 2027. The server sits alone on VLAN 30, created on our boundary firewall listed in A2.5. Firewall rules deny all traffic between VLAN 30 and the internet in both directions, and between VLAN 30 and every other VLAN. There is no supplier remote access. Two staff use it from a dedicated terminal on VLAN 30.
For Cyber Essentials Plus, the test specification v3.2 says the assessor must verify "by technical means" that sub-sets outside a partial scope "have been segregated effectively". It also states that "virtual patching is not an acceptable mitigation to the security vulnerabilities of legacy unsupported operating systems long term". A firewall rule or intrusion prevention signature in front of an old server does not make the server compliant.
How do common legacy systems work out?
Most cases resolve to upgrade, extended support, or isolation; here are the ones we see most often.
Windows 10. Keep it only while it is enrolled in Microsoft's Extended Security Updates programme, as the A6.1 guidance requires after 14 October 2025; Windows 10 and Cyber Essentials covers ESU eligibility and costs.
Windows 11 on unsupported hardware. Microsoft says that if you install Windows 11 on a PC that does not meet the minimum requirements, "your PC will no longer be supported and won't be entitled to receive updates" (Microsoft Support). In our reading that fails the v3.3 licensed-and-supported test, so treat these PCs like any other unsupported device: replace them or isolate them.
Old line-of-business applications. If the vendor no longer issues security fixes or will not give an end date, the application is unsupported. Ask the vendor for a supported version or a published support date first. If neither exists, move the application and its server into an isolated sub-set, or plan a replacement.
Lab, manufacturing and medical kit. Instruments often run an operating system the manufacturer will not let you upgrade. These are good candidates for an isolated sub-set, because they rarely need the internet. Results can move out on a controlled path that does not open internet access to the sub-set.
Old routers and firewalls. Firmware counts as an operating system under A6.1. In our reading, an ISP router or firewall that no longer receives firmware updates has no isolation option, because it controls internet traffic by definition. Replace it.
An organisation lists a Windows 10 laptop in A2.6 and answers yes to A6.1, but has not bought ESU for it. The device list gives it away. Check every operating system against vendor support dates with the is it supported tool before you write the device list, and buy ESU or upgrade first.
Does open-source or third-party-supported software count?
It can, if someone is committed to issuing security fixes and publishes an end date.
A6.3 says "It is acceptable to use free and open-source software as long as you comply with any licensing requirements." The v3.3 definition notes that "the vendor doesn't need to have created the software originally, but they must be able to modify the original software to create fixes." In our reading, a distribution vendor that backports security fixes to an older package can meet that test, while a community project that has stopped releasing fixes cannot.
Keep a short register of every system you have isolated or kept on extended support, with the end date and the replacement plan. It makes the next renewal faster, and it gives your assessor a clear answer to A6.7. Our supported software hub lists end-of-support dates for common products.
What should you do next?
List everything, check support dates, and choose one of the options for each unsupported item before you submit.
Start with the device and software lists the assessment asks for, then check each entry. Our scope guide explains which devices count, and the security update management requirements cover the 14-day rule that applies once everything is supported. Then check your readiness against the full question set. If you want an assessor to review a sub-set design before you rely on it, Precursor Security's gap analysis starts from £500, and Cyber Essentials from £1,500 with the IASME fee included.
- NCSCCyber Essentials Plus Test Specification v3.2Read on ncsc.gov.uk (opens in a new tab)
- Microsoft LearnExtended Security Updates (ESU) program for Windows 10Read on learn.microsoft.com (opens in a new tab)
- MicrosoftMicrosoft Support, Windows 11 on devices that don't meet minimum system requirements · Checked 9 November 2026Read on support.microsoft.com (opens in a new tab)
- NCSCCyber Essentials: Requirements for IT Infrastructure v3.3 · April 2026Read on ncsc.gov.uk (opens in a new tab)
- IASMECyber Essentials Danzell Question Set 2026 (v16.3)Read on iasme.co.uk (opens in a new tab)
Frequently asked questions
Then A6.4 or A6.5 is a no, and both are automatic fails. The question set says you must install high and critical updates 'within 14 days in all circumstances'. v3.3 counts vendor-approved fixes such as configuration changes or scripts as vulnerability fixes, so a vendor's documented workaround applied within 14 days can meet the rule. If neither is possible, the system has to be removed or moved to a sub-set with no internet traffic.
Not safely for Cyber Essentials. Microsoft says that if you install Windows 11 on such a PC, 'your PC will no longer be supported and won't be entitled to receive updates', and that these devices 'aren't guaranteed to receive updates, including but not limited to security updates'. In our reading that fails the v3.3 licensed-and-supported test, so replace the device or keep it in an isolated sub-set.
Yes. A standalone machine that cannot make or accept internet connections falls outside the v3.3 scope conditions, so it is out of scope without a sub-set. A networked machine running unsupported software must sit in a sub-set, separated from the rest of your network by a firewall or VLAN, that prevents all traffic to or from the internet; describe it in A6.7.
Then it cannot be out of scope while your certificate covers the whole organisation. The A6.7 guidance says that if the out-of-scope sub-set remains connected to the internet, you will not be able to achieve whole company certification and must select Partial Organisation in A2.1. The certificate then reads 'Partial Organisation', so confirm that your customer accepts a partial scope before you choose this route.
No. The CE Plus test specification v3.2 says virtual patching is not an acceptable long-term mitigation for legacy unsupported operating systems and will not be recognised as compliance with Cyber Essentials requirements. The software itself must be supported, removed, or in a sub-set with no internet traffic.
It can. A6.3 says free and open-source software is acceptable if you meet its licensing terms. v3.3 defines supported software as having a vendor committed to regular vulnerability fixes, with a published future date when fixes stop. The vendor need not have written the software, but must be able to modify it to create fixes.
Would you pass the 2026 question set?
Answer 24 yes or no questions, built by Precursor Security, an IASME Cyber Essentials Certification Body, and get a readiness score in about five minutes, with any auto-fail questions you miss flagged first in your results.
- IASME Certification Body
- CREST accredited
- UK offices in Leeds, Newcastle, London and Edinburgh
Help from Precursor Security
Behind on patching or unsupported software?
The 14-day rule (A6.4, A6.5) and unsupported software are where most applications stall. We can review your estate against them, then assess and certify you. Gap analysis from £500 + VAT.
Share or cite this page