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 PossibleAutomatic 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.
Cyber Essentials SU.3Critical and High Updates within 14 DaysCritical 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.
Cyber Essentials Plus PM-01High and Critical Vulnerability PatchingHigh 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.
CIS Controls v8 7.4Perform Automated Application Patch ManagementPerform Automated Application Patch Management. Keep applications on enterprise assets updated by automated patch management, running at least once a month.
PCI DSS 4.0 6.3.3Timely installation of security patches6.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.
NIST SP 800-53 SI-2Flaw RemediationSI-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.
ISO/IEC 27001 A.8.8Management of technical vulnerabilitiesManagement 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.
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 releasePatch 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).
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 existPatch 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).
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 existPatch 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).