Unsupported Software Findernotice of vendor support

10. Evergreen product behind the current release

Browsers and other auto-updating clients are supported on the current release only, so an older version is not past support in the way a retired product is: it is behind. The question is how far behind the fleet is allowed to run, which is what the patch-window clauses set.

When it is raised
an evergreen product on a release older than the newest one released on or before the as-at date
The question
How far behind the current release is this fleet allowed to run, and are automatic updates on where the option exists?
For
your desktop support lead

The clauses it can cite

Cyber Essentials SU.2Automatic Updates Enabled Where Possible

Automatic Updates Enabled Where Possible. Automatic updates must be enabled on devices and software where the option exists, to ensure security updates are applied without delay.

What an assessor asks to see: Windows Update for Business policy; MacOS auto-update screenshot; WSUS/Intune config
Where software lists usually fall short: Auto-update deferred indefinitely; Users can opt out
Source: Cyber Essentials (NCSC and IASME), read 30 Sep 2026
Cyber Essentials SU.3Critical and High Updates within 14 Days

Critical and High Updates within 14 Days. All high or critical security updates (CVSS 7.0+ or vendor critical/high rating) must be applied within 14 days of release.

What an assessor asks to see: Patch compliance dashboard (Defender/Tenable/Qualys); 14-day SLA report; Exception register
Where software lists usually fall short: Patch backlog beyond 14 days; No CVSS-based tracking
Source: Cyber Essentials (NCSC and IASME), read 30 Sep 2026
Cyber Essentials Plus PM-01High and Critical Vulnerability Patching

High and Critical Vulnerability Patching. Security updates rated high or critical must be applied within 14 days of release for operating systems and supported applications, or vulnerable software removed.

What an assessor asks to see: Patch deployment reports; Internal authenticated scan results; Exception register with risk owner sign off
Where software lists usually fall short: Scan shows 14+ day breaches; No scan of servers; Patches deferred without documented risk acceptance
Source: Cyber Essentials Plus (NCSC and IASME), read 30 Sep 2026
CIS Controls v8 7.4Perform Automated Application Patch Management

Perform Automated Application Patch Management. Keep applications on enterprise assets updated by automated patch management, running at least once a month.

What an assessor asks to see: Application patch management configuration with automated monthly deployment; Application patch compliance reports; Patch standard covering third-party applications, not only operating system updates; Third-party patching tool catalogue showing which applications are auto-updated; Monthly application version compliance report for browsers, runtimes, PDF readers and office suites
Where software lists usually fall short: Only Microsoft products patched automatically while Java, Adobe and browsers lag behind; Server-side applications and databases patched only during annual upgrades; Software installed outside the software distribution tool never updated
Source: CIS Controls v8 (Center for Internet Security), read 30 Sep 2026
PCI DSS 4.0 6.3.3Timely installation of security patches

6.3.3 Timely installation of security patches. All system components must be shielded from known vulnerabilities by applying relevant security patches or updates such that: patches or updates addressing critical vulnerabilities, as ranked under Requirement 6.3.1, must go in within one month of their release; and every other relevant security patch or update is installed within a suitable time frame set by the entity's own assessment of how critical the risk is to its environment, using the Requirement 6.3.1 ranking process. It applies to all entities and all system components. Customized approach objective: exploitation of a known vulnerability cannot be used to compromise system components.

What an assessor asks to see: Patch management procedure stating the one-month deadline for critical patches and time frames for others; Patch compliance reports per system component showing install dates against vendor release dates; Risk-based rationale or targeted risk analysis for non-critical patch time frames; Exception register for patches that could not be applied, with compensating measures; Sample of critical advisories traced to installation evidence
Where software lists usually fall short: Critical patches applied more than one month after release because of change freeze windows; Network devices, hypervisors or appliances excluded from patch reporting; No defined time frame for non-critical patches, so they accumulate indefinitely
Source: PCI DSS 4.0 (PCI Security Standards Council), read 30 Sep 2026
NIST SP 800-53 SI-2Flaw Remediation

SI-2 Flaw Remediation. a. Identify, report, and correct system flaws; b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Install security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and d. Incorporate flaw remediation into the organizational configuration management process.

What an assessor asks to see: System and information integrity policy; System and information integrity procedures; Procedures addressing flaw remediation; Procedures addressing configuration management; List of flaws and vulnerabilities potentially affecting the system; List of recent security flaw remediation actions performed on the system (e.g., list of installed patches, service packs, hot fixes, and other software updates to correct system flaws); Test results from the installation of software and firmware updates to correct system flaws; Installation/change control records for security-relevant software and firmware updates; System security plan; Test of Organizational processes for identifying, reporting, and correcting system flaws; organizational process for installing software and firmware updates; mechanisms supporting and/or implementing the reporting and correcting of system flaws; mechanisms supporting and/or implementing testing software an
Where software lists usually fall short: Security-relevant updates installed outside the organization-defined time period with no recorded exception or risk acceptance; Updates deployed to production without the testing for effectiveness and side effects that SI-2 b requires
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
Essential Eight Patch applications ISM-1691Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release

Patch applications (ISM-1691): Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release. Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release. Required at Maturity Levels One and Two of the Patch applications mitigation strategy (Appendices A and B); ISM control ISM-1691 in ASD's Essential Eight to ISM mapping (December 2023). At Maturity Level Three this requirement is replaced by ISM-1692 (48 hours when critical or exploited) and ISM-1901 (two weeks when non-critical).

What an assessor asks to see: Installed-version reports for office suites, browsers, email clients, PDF software and security products against vendor release dates; Deployment tool report showing successful installation within two weeks
Where software lists usually fall short: Deployment tool shows patches sent but not installed or awaiting reboot
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch applications ISM-1692Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist

Patch applications (ISM-1692): Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist. Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist. Required at Maturity Level Three of the Patch applications mitigation strategy (Appendix C); ISM control ISM-1692 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Records of critical or exploited vulnerabilities in office suites, browsers, email clients, PDF software and security products with 48-hour application; Emergency change records for out-of-cycle browser and office updates
Where software lists usually fall short: Critical browser updates wait for the standard two-week deployment ring
Source: Essential Eight (ASD), read 30 Sep 2026
Essential Eight Patch applications ISM-1901Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist

Patch applications (ISM-1901): Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist. Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist. Required at Maturity Level Three of the Patch applications mitigation strategy (Appendix C); ISM control ISM-1901 in ASD's Essential Eight to ISM mapping (December 2023).

What an assessor asks to see: Records of non-critical vulnerabilities in the named application classes applied within two weeks of release; Deployment ring schedule showing the full estate completes within two weeks
Where software lists usually fall short: Final deployment ring completes after the two-week window
Source: Essential Eight (ASD), read 30 Sep 2026

See the specimen list runCheck your own list