Unsupported Software Findernotice of vendor support

1. Past vendor security support, still installed

The lifecycle record (endoflife.date, community-maintained) puts the end of security support for this version on or before the as-at date, with no extended support running past it. Each scheme you ticked asks the same thing of software in that state: remove it or replace it, or for Cyber Essentials segregate it into a sub-set the assessment does not cover. Which of those you choose, and whether a device sits in scope, is your decision.

When it is raised
security end date on or before the as-at date, with no extended support running past it
The question
Can this version be upgraded, retired or removed before the assessment, and if it has to stay, what is the plan, where does it sit, and who signs it off?
For
your IT operations lead

The clauses it can cite

Cyber Essentials SU.1Software Licensed and Supported

Software Licensed and Supported. All software on in-scope devices must be licensed and supported by the vendor (i.e. receiving security updates). Unsupported software must be removed or segregated.

What an assessor asks to see: SCCM/Intune software inventory; EOL/EOSL register; Segregation evidence for unsupported
Where software lists usually fall short: Windows 7/Server 2012 still in use; EOL Java runtimes
Source: Cyber Essentials (NCSC and IASME), read 30 Sep 2026
Cyber Essentials SU.4Remove Out-of-Support Software

Remove Out-of-Support Software. Remove software that is no longer receiving security updates from in-scope devices, or fully segregate it from the rest of the network.

What an assessor asks to see: EOL removal log; Segregated VLAN evidence; Compensating control documentation
Where software lists usually fall short: EOL kept on production network; No plan to retire
Source: Cyber Essentials (NCSC and IASME), read 30 Sep 2026
Cyber Essentials Plus PM-02Unsupported Software Removal

Unsupported Software Removal. Software and operating systems that are no longer supported by the vendor must be removed from in scope devices or isolated with compensating controls.

What an assessor asks to see: Software inventory with vendor support status; EOL remediation plan; Isolation network diagrams
Where software lists usually fall short: Windows 7 or unsupported Server still in scope; EOL Java runtimes on user devices; No inventory accuracy check
Source: Cyber Essentials Plus (NCSC and IASME), read 30 Sep 2026
CIS Controls v8 2.2Ensure Authorized Software is Currently Supported

Ensure Authorized Software is Currently Supported. Only software that still receives vendor support may be marked as authorised in the enterprise software register. Where unsupported software is still needed for the mission, record an exception that sets out the compensating controls and the acceptance of remaining risk. Unsupported software with no recorded exception is to be marked unauthorised. Check the list for support status no less often than monthly.

What an assessor asks to see: Authorised software list compared with vendor support status, showing only supported software authorised; Exception register for unsupported software with mitigating controls and residual risk acceptance; Monthly support status check record comparing each authorised title with vendor end-of-life announcements; Software register entries for end-of-support titles marked unauthorised where no exception exists; Risk acceptance sign-offs by a named business owner for each unsupported title kept for the mission
Where software lists usually fall short: End-of-life operating systems or Java runtimes still listed as authorised after vendor support ended; Exceptions recorded without compensating controls or an expiry and review date; Support status checked only at annual audit time instead of monthly
Source: CIS Controls v8 (Center for Internet Security), read 30 Sep 2026
PCI DSS 4.0 12.3.4Annual review of hardware and software technologies

12.3.4 Annual review of hardware and software technologies. Hardware and software in use must undergo a check at least every 12 months, covering at minimum: analysis that vendors still supply timely security fixes; analysis that the technologies still support, and do not obstruct, PCI DSS compliance; documentation of industry announcements or trends about a technology, for instance a vendor's end-of-life notice; and a remediation plan for outdated technologies, including those with announced end-of-life, approved by senior management. Objective under the customized approach: hardware and software stay current and vendor supported, and plans to retire or replace unsupported components are reviewed periodically. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

What an assessor asks to see: Technology review report covering support status and patch availability; End-of-life tracking register with vendor announcements; Senior management approved remediation plan for outdated technologies; Firmware and version inventory
Where software lists usually fall short: Review omits network device firmware or embedded systems; End-of-life systems identified but no approved remediation plan; Plan exists but lacks senior management approval
Source: PCI DSS 4.0 (PCI Security Standards Council), read 30 Sep 2026
PCI DSS 4.0 A3.3.2A3.3.2 Annual review of hardware and software technologies

A3.3.2 Annual review of hardware and software technologies. Hardware and software technologies must be reviewed every 12 months at a minimum to confirm whether they continue to satisfy the PCI DSS needs of the organization. Applicability: the process includes a plan to remediate any technology that no longer meets those requirements, up to replacing it where appropriate. Related PCI DSS requirements 2, 6 and 12. Guidance: consider vendor support status, firmware currency and vendor changes to products or processes. Applies only to designated entities. Objective under the customized approach: not eligible for the customized approach; only the defined approach can be used.

What an assessor asks to see: Annual technology review report; Hardware and software inventory with vendor support and end-of-life dates; Firmware version currency report; Remediation or replacement plans for non-compliant technologies
Where software lists usually fall short: Review done but no remediation plan for end-of-life items; Firmware and embedded devices left out of the review; Review older than 12 months
Source: PCI DSS 4.0 (PCI Security Standards Council), read 30 Sep 2026
NIST SP 800-53 SA-22Unsupported System Components

SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support for unsupported components [Selection (one or more): in-house support; [Assignment: organization-defined support from external providers]].

What an assessor asks to see: System and services acquisition policy; Procedures addressing the replacement or continued use of unsupported system components; Documented evidence of replacing unsupported system components; Documented approvals (including justification) for the continued use of unsupported system components; System security plan; Supply chain risk management plan; Test of Organizational processes for replacing unsupported system components; mechanisms supporting and/or implementing the replacement of unsupported system components
Where software lists usually fall short: Components past developer or vendor end of support remain in service without a replacement plan; No in-house or external alternative support arrangement is documented for unsupported components still in use
Source: NIST SP 800-53 Rev 5, read 30 Sep 2026
ISO/IEC 27001 A.8.8Management of technical vulnerabilities

Management of technical vulnerabilities. The organization is to gather information about technical vulnerabilities in the information systems it uses, assess how exposed it is, and take suitable action. Purpose (stated in ISO/IEC 27002:2022): prevents exploitation of technical vulnerabilities. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.8.

What an assessor asks to see: Statement of Applicability entry for control A.8.8, showing inclusion or justified exclusion, implementation status and the risks it treats; A software asset inventory with vendor, product, version, deployment location and responsible owner; Defined vulnerability management roles and a list of monitored vulnerability information sources; Authenticated scan results and penetration test reports by authorized testers, with verification scans after patching; Remediation timelines by severity with measured performance, and risk records weighing the vulnerability against update risk
Where software lists usually fall short: The asset inventory is incomplete, so unknown software is never scanned or patched; Remediation timelines are routinely missed with no risk acceptance; Third-party libraries in in-house code are not tracked for vulnerabilities; There is no way for external researchers to report vulnerabilities
Source: ISO/IEC 27001 (Annex A), read 30 Sep 2026
ISO/IEC 27001 A.8.19Installation of software on operational systems

Installation of software on operational systems. Procedures and measures are to be put in place so that installing software on operational systems is managed securely. Purpose (stated in ISO/IEC 27002:2022): ensures the integrity of operational systems and prevents exploitation of technical vulnerabilities. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.19.

What an assessor asks to see: Statement of Applicability entry for control A.8.19, showing inclusion or justified exclusion, implementation status and the risks it treats; Procedures for installing and updating operational software, including authorization, testing and rollback planning; Change and deployment records showing management authorization, successful testing and the administrator who performed the installation; Configuration control records for operational software and documentation, and an audit log of updates; Evidence that development tools and compilers are absent from production systems
Where software lists usually fall short: Users can install any software on servers or workstations; Production systems contain compilers and development code; Unsupported software versions remain in production without a risk decision; Externally hosted dependencies are pulled at build or run time without integrity controls
Source: ISO/IEC 27001 (Annex A), read 30 Sep 2026
Essential Eight Patch applications ISM-1905Online services that are no longer supported by vendors are removed

Patch applications (ISM-1905): Online services that are no longer supported by vendors are removed. Online services that are no longer supported by vendors are removed. Required at Maturity Levels One, Two and Three of the Patch applications mitigation strategy (Appendices A, B and C); ISM control ISM-1905 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Inventory of online services in use with vendor support status and end-of-support dates; Decommissioning records for online services that reached end of support
Where software lists usually fall short: Legacy online service kept running because no owner will authorise its removal
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch applications ISM-1704Office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed

Patch applications (ISM-1704): Office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed. Office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed. Required at Maturity Levels One, Two and Three of the Patch applications mitigation strategy (Appendices A, B and C); ISM control ISM-1704 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Software inventory of office suites, browsers and extensions, email clients, PDF software and security products checked against vendor support lifecycles; Evidence that Adobe Flash Player is removed (hotfix KB4577586 or equivalent removal record)
Where software lists usually fall short: Unsupported browser extensions or old PDF readers left on a subset of workstations
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch applications ISM-0304Applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed

Patch applications (ISM-0304): Applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed. Applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed. Required at Maturity Level Three of the Patch applications mitigation strategy (Appendix C); ISM control ISM-0304 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Complete software inventory checked against vendor support lifecycles for all other applications; Removal records for unsupported applications with dates
Where software lists usually fall short: Unsupported line-of-business application retained with no approved exception or compensating control
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch operating systems ISM-1501Operating systems that are no longer supported by vendors are replaced

Patch operating systems (ISM-1501): Operating systems that are no longer supported by vendors are replaced. Operating systems that are no longer supported by vendors are replaced. Required at Maturity Levels One, Two and Three of the Patch operating systems mitigation strategy (Appendices A, B and C); ISM control ISM-1501 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Operating system version inventory (for example winver output or scanner OS fingerprinting) compared with vendor support lists; Replacement or upgrade records for operating systems that reached end of support
Where software lists usually fall short: Unsupported operating systems kept on isolated but still connected hosts with no approved exception
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch operating systems ISM-1407The latest release, or the previous release, of operating systems are used

Patch operating systems (ISM-1407): The latest release, or the previous release, of operating systems are used. The latest release, or the previous release, of operating systems are used. Required at Maturity Level Three of the Patch operating systems mitigation strategy (Appendix C); ISM control ISM-1407 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Operating system release inventory showing each host on the latest or previous release; Upgrade plan for hosts approaching a two-release gap
Where software lists usually fall short: Hosts on supported but older feature releases beyond the previous release
Source: Essential Eight (ASD), read 30 Sep 2026

See the specimen list runCheck your own list