example, by using a centralised and managed approach that maintains the integrity of patches or updates, and confirms
that they have been applied successfully.
Security Control: ISM-1143; Revision: 8; Updated: Dec-21; Applicability: All; Essential Eight: N/A
Patch management processes, and supporting patch management procedures, are developed and implemented.
Security Control: ISM-0298; Revision: 8; Updated: Mar-22; Applicability: All; Essential Eight: N/A
A centralised and managed approach that maintains the integrity of patches or updates, and confirms that they have
been applied successfully, is used to patch or update applications, operating systems, drivers and firmware.
Software register
To assist with monitoring information sources for details of relevant patches or updates, an organisation should
maintain and regularly verify software registers for workstations, servers, network devices and other ICT equipment.
Security Control: ISM-1493; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Software registers are maintained for workstations, servers, network devices and other ICT equipment and verified on a
regular basis.
Security Control: ISM-1643; Revision: 0; Updated: Jun-21; Applicability: All; Essential Eight: N/A
Software registers contain versions and patch histories of applications, drivers, operating systems and firmware.
When to patch security vulnerabilities
When patches or updates are released by vendors for security vulnerabilities, an organisation should apply them in a
timeframe commensurate with the likelihood of attempted exploitation by an adversary. For example, by prioritising
patches or updates for security vulnerabilities in internet-facing services and their operating systems, especially when
exploitation code exists or active exploitation is occurring.
If no patches or updates are available for security vulnerabilities, mitigation advice from vendors, trusted authorities or
security researchers may provide some protection until patches or updates are made available. Such mitigation advice
may be published in conjunction with, or soon after, announcements made relating to security vulnerabilities.
Mitigation advice may cover how to disable or block access to vulnerable functionality, how to reconfigure vulnerable
functionality, or how to detect attempted or successful exploitation of vulnerable functionality.
If a patch or update is released for high assurance ICT equipment, the ACSC will conduct an assessment of the patch or
update. Subsequently, if the patch or update is approved for deployment, the ACSC will provide guidance on the
methods and timeframes in which it is to be applied.
Security Control: ISM-1690; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Patches, updates or vendor mitigations for security vulnerabilities in internet-facing services are applied within two
weeks of release, or within 48 hours if an exploit exists.
Security Control: ISM-1691; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Patches, updates or vendor mitigations for security vulnerabilities in office productivity suites, web browsers and their
extensions, email clients, PDF software, and security products are applied within two weeks of release.
Security Control: ISM-1692; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML3
Patches, updates or vendor mitigations for security vulnerabilities in office productivity suites, web browsers and their
extensions, email clients, PDF software, and security products are applied within 48 hours if an exploit exists.
Security Control: ISM-1693; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Patches, updates or vendor mitigations for security vulnerabilities in other applications are applied within one month.
Security Control: ISM-1694; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Patches, updates or vendor mitigations for security vulnerabilities in operating systems of internet-facing services are
applied within two weeks of release, or within 48 hours if an exploit exists.
94
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents