managed software repositories or from trusted application marketplaces. Furthermore, to prevent unprivileged users
from removing security functionality, or breaking system functionality, unprivileged users should not have the ability to
uninstall or disable approved software.
Security Control: ISM-1592; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Unprivileged users do not have the ability to install unapproved software.
Security Control: ISM-0382; Revision: 7; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Unprivileged users do not have the ability to uninstall or disable approved software.
Application control
Application control can be an effective way to not only prevent malicious code from executing on workstations and
servers, but also to ensure only approved applications can execute. When developing application control rulesets,
determining approved executables (e.g. .exe and .com files), software libraries (e.g. .dll and.ocx files), scripts (e.g. .ps1,
.bat, .cmd, .vbs and .js files), installers (e.g. .msi, .msp and .mst files), compiled HTML (e.g. .chm), HTML applications
(e.g. .hta), control panel applets (e.g. .cpl) and drivers based on business requirements is a more secure method than
simply approving those already residing on a workstation or server. Furthermore, it is preferable that an organisation
defines their own application control rulesets, rather than relying on those from application control vendors, and
validate them on an annual or more frequent basis.
In implementing application control, an organisation should use a reliable method, or combination of methods, such as
cryptographic hash rules, publisher certificate rules or path rules. Depending on the method chosen, further hardening
may be required to ensure that application control mechanisms and application control rulesets cannot be bypassed by
an adversary.
Finally, to assist with incident response activities, it is important that application control event logs are centrally stored
and protected from unauthorised modification and deletion, monitored for signs of compromise, and actioned when
cyber security events are detected.
Security Control: ISM-0843; Revision: 9; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Application control is implemented on workstations.
Security Control: ISM-1490; Revision: 3; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Application control is implemented on internet-facing servers.
Security Control: ISM-1656; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML3
Application control is implemented on non-internet-facing servers.
Security Control: ISM-1657; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Application control restricts the execution of executables, software libraries, scripts, installers, compiled HTML, HTML
applications and control panel applets to an organisation-approved set.
Security Control: ISM-1658; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML3
Application control restricts the execution of drivers to an organisation-approved set.
Security Control: ISM-0955; Revision: 6; Updated: Apr-20; Applicability: All; Essential Eight: N/A
Application control is implemented using cryptographic hash rules, publisher certificate rules or path rules.
Security Control: ISM-1582; Revision: 1; Updated: Sep-21; Applicability: All; Essential Eight: ML3
Application control rulesets are validated on an annual or more frequent basis.
Security Control: ISM-1471; Revision: 2; Updated: Apr-20; Applicability: All; Essential Eight: N/A
When implementing application control using publisher certificate rules, both publisher names and product names are
used.
Security Control: ISM-1392; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A
77
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents