Cyber Essentials audit flagged unsupported software in a business application we can't easily upgrade. What are the options?
Cyber Essentials requires software on in-scope devices to be supported, so the choices are to upgrade the unsupported component or the platform under it, to segregate the system so it is out of scope, or to replace the application; most 'can't easily upgrade' cases need a smaller upgrade than feared once someone has assessed what is actually blocking it. This page is for IT managers at UK organisations whose Cyber Essentials assessment has flagged a business application that depends on out-of-support software.
By Graham Church, founder and managing director. Updated 15 October 2026.
What Cyber Essentials actually requires
Of the five Cyber Essentials technical controls, the one that catches old applications is security update management. The NCSC’s requirements document, Cyber Essentials: Requirements for IT Infrastructure (v3.2, April 2025, current when this page was written), says that all software on in-scope devices must be licensed and supported, and must be removed from the device when it becomes unsupported, or removed from scope by placing it in a defined sub-set that prevents all traffic to and from the internet. Critical and high-risk vulnerability fixes must be applied within 14 days of release.
Three definitions matter here.
- Software includes operating systems, off-the-shelf applications, interpreters, scripts, libraries, network software and firmware. A finding against “the application” is usually a finding against one of these underneath it.
- Licensed and supported software is software a vendor has committed to support with regular vulnerability fixes, with a published date for when that will stop. The vendor need not be the original author, but must be able to modify the software to produce fixes.
- A sub-set is a part of the organisation whose network is segregated from the rest by a firewall or VLAN. Scope must be agreed with your certification body before the assessment begins.
The document also says that bespoke and custom components of web applications are out of scope. The code your developer wrote is not the problem; the Windows version, database, .NET runtime, web server or third-party library it depends on is. The requirements are revised from time to time; check the current document and your certification body before relying on this summary.
The options, in order of cost
Upgrade the component. Replace the one piece that is out of support and leave the rest alone: install a supported .NET Framework runtime, move the database to a current SQL Server version, swap a library for its current release. Often the application needs little or no change, but it must be tested by the people who use it. This is the cheapest route wherever the vendor offers an in-place upgrade.
Upgrade the platform under it. A new Windows Server, a current database and web server, and the application moved on top. It is a larger piece of work, rehearsed on a copy first, and it is often needed anyway because the old server is the thing nobody can patch. Microsoft sells Extended Security Updates for some products, for example SQL Server 2016 until 17 July 2029 and Windows Server 2016 until 12 January 2030; whether a paid programme counts as supported for your assessment is a question for your certification body.
Segregate the system. Put it in a sub-set with no traffic to or from the internet and take it out of scope. Technically cheap; the cost is in use. No remote access, no email sent by the system, no integrations over the internet. It suits a system that is near retirement or used only on site. The finding goes away, but the software is still unsupported, and the exposure has shrunk rather than gone.
Replace the application. Where the platform has no upgrade route, replacement or staged modernisation is what remains. It is the largest cost and the longest timescale, so establish first that the cheaper options are closed.
What “can’t easily upgrade” usually means
The phrase covers three situations.
An old .NET Framework. This is less of a block than it sounds. .NET Framework 4.x versions upgrade in place, so an application built for 4.5 generally runs on the 4.8 runtime, and versions 4.7 to 4.8.1 are supported for as long as the Windows version they are installed on. .NET Framework 4.5.2, 4.6 and 4.6.1 ended support on 26 April 2022, and 4.6.2 ends on 12 January 2027. Installing 4.8 on a supported Windows Server and testing the application is often the whole job. The harder case is modern .NET: .NET 8 and .NET 9 both ended on 10 November 2026, and an application on either must be retargeted and rebuilt.
A database version. SQL Server 2016 ended support on 14 July 2026. Moving a database to a current version usually needs few changes to the application, and the compatibility level can be kept during the move. The work is in testing the reports and stored procedures.
A component with no newer release. A reporting control, PDF library, grid or ActiveX control whose maker has gone. This is the case that is genuinely hard, because the work is inside the application: a substitute component, or the function rebuilt.
An assessment settles which you have. List every component with its version, support date and exposure, build the application on a copy of a current platform, and see what fails. Most of the list turns out to be upgrade-and-test, and a few items need real work. CodeFirst, a UK software company, does this for .NET applications as a fixed-price .NET upgrade assessment. For anything else a code audit covers the same ground, and our page on unsupported software describes the order we work in.
The timing problem
The finding usually arrives with a date attached: a tender that requires certification, a contract renewal, a cyber-insurance proposal. The upgrade takes longer than the date allows, and the pressure is to pick the fastest option rather than the right one.
The usual answer is to separate the two. Segregate the system, or narrow the scope, to get certified by the date, with your certification body’s agreement, and run the upgrade on its own timetable behind that. Bear in mind that some benefits of the scheme depend on whole-organisation scope. Do not let the deadline pick a rewrite; a replacement started in a hurry misses the rules nobody wrote down.
If you are not sure what you are running, our free end-of-support check lists the versions on a server and when each stops getting fixes, and our answer on what happens when software reaches end of support explains why the date matters.
Related questions
Does Cyber Essentials cover our bespoke application itself?
Under the requirements document current when this page was written, bespoke and custom components of web applications are out of scope, but the operating system, database, runtime, web server and third-party libraries they run on are software on in-scope devices and must be supported. In practice the finding is almost always about one of those. Check the current requirements document, because the wording is revised from time to time.
If we take the system off the internet, is it out of scope?
The requirements allow unsupported software to be removed from scope by placing it in a defined sub-set, segregated by a firewall or VLAN, that prevents all traffic to and from the internet. Whether your arrangement meets that is for your certification body to confirm, and the scope must be agreed with them before the assessment. The software is still unsupported: the finding goes away, the exposure only shrinks.
Does paying Microsoft for Extended Security Updates count as supported?
The requirements define supported software as software a vendor has committed to support with regular vulnerability fixes and a published end date, which a paid programme provides for a limited period. Whether your assessor accepts it is a question to put to the certification body against the current requirements document. Either way the programme ends, so treat it as time bought for the upgrade.
How quickly do updates have to be applied once we are on supported versions?
Under v3.2 of the requirements, updates that fix vulnerabilities the vendor rates critical or high risk, or with a CVSS v3 base score of 7 or above, must be applied within 14 days of release, with automatic updates enabled where possible. That has a consequence for an old application: whoever supports it must be able to test and release a platform update within that window. Build it into the support arrangement.
Want the answer for your system?
Tell us what the software does and what you are trying to decide. We will reply with a straight answer and what we would need to know to be more precise.