Essential Eight AC-ML3.1 Application control is implemented on non-internet-facing servers
What it says
Application control is implemented on non-internet-facing servers.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure only approved software can run on internal servers.
This control ensures that only software approved by your organisation can run on internal servers that do not face the internet. It matters because unauthorised or harmful software on these servers can lead to data theft, disruptions, or security breaches. Controlling what runs on these servers protects sensitive information and keeps systems secure.
Free. Save your status, tasks and notes.
Why it matters
Without application control, unauthorised software on internal servers can lead to data leaks and compromise critical business operations.
How to implement
The IT team should create a list of approved software for non-internet-facing servers.
To do this, review the software currently used and needed for operations and mark those as approved.
A system administrator should implement application control software on non-internet-facing servers.
This is done by configuring tools like AppLocker or similar to block any software not on the approved list.
Security officers should regularly review and update the list of approved software.
Do this by meeting quarterly with department heads to ensure the list meets current needs and security policies.
The IT team should set up alerts for any attempts to run unapproved software.
Use monitoring tools to ensure notifications are sent immediately to the security team if there is suspicious activity.
Keep it running
Maintain an allow-list for non-internet-facing servers, review it regularly, and alert on any execution outside approved applications.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
Is there an approved list of software for non-internet-facing servers?
Look at
Review the software approval document.
Good evidence
A comprehensive and current list of approved software should be provided.
- Check 2 of 3What an auditor asks for
Ask for
How are application controls configured on non-internet-facing servers?
Look at
Check the application control settings and rules.
Good evidence
The settings should match the list of approved software, blocking all others.
- Check 3 of 3What an auditor asks for
Ask for
How often is the list of approved software updated?
Look at
Examine the update logs or meeting notes.
Good evidence
Evidence of quarterly reviews and updates to the approved software list should be present.
Mappings
Closest match in ASD Information Security Manual: ISM-1656, Implement application control on secure servers, which asks for the same thing.
ASD Information Security Manual: 9 mappings
This control is equivalent to ISM-1656.
E8-AC-ML3.1 requires application control to be implemented on non-internet-facing servers. ISM-1656 states the same requirement, mandating application control on non-internet-facing servers. The scope and intent align closely, with both controls focused on preventing execution of unauthorised software on internal servers.
This control is broader than ISM-0955.
ISM-0955 requires application control to be implemented using cryptographic hash, publisher certificate, or path-based rules. E8-AC-ML3.1 requires application control on non-internet-facing servers, representing a particular environment where ISM-0955's rule types would be used. E8-AC-ML3.1 is about coverage across server classes, whereas ISM-0955 specifies acceptable technical approaches for controlling execution.
This control partially overlaps ISM-1490.
ISM-1490 requires application control to be implemented on internet-facing servers. E8-AC-ML3.1 requires application control on non-internet-facing servers, which is the same control mechanism but applied to a different server exposure category. They overlap on the use of application control for servers, but differ materially in scope because ISM-1490 is specifically about internet-facing servers while E8-AC-ML3.1 is explicitly not.
This control partially overlaps ISM-1657.
E8-AC-ML3.1 requires application control on non-internet-facing servers to ensure only approved software can run. ISM-1657 details the scope of what application control must restrict (executables, libraries, scripts, installers, and related components) to an organisation-approved set, which is directly relevant to achieving E8-AC-ML3.1. The primary control is environment-scoped (non-internet-facing servers), while ISM-1657 is control-mechanism scoped (what must be controlled).
This control partially overlaps ISM-1658.
E8-AC-ML3.1 requires implementing application control on non-internet-facing servers to restrict execution to approved software. ISM-1658 strengthens that implementation by requiring application control to specifically restrict driver execution to an organisation-approved set on those systems. E8-AC-ML3.1 does not explicitly call out drivers, so ISM-1658 is an implementation-hardening requirement rather than the same control.
This control partially overlaps ISM-1871.
E8-AC-ML3.1 requires application control to be implemented on non-internet-facing servers so only approved software can execute. ISM-1871 specifies where application control should be applied, focusing on system locations over writable user paths. Both address effective application control, with E8-AC-ML3.1 scoped to non-internet-facing servers and ISM-1871 as a placement rule across endpoints and servers.
This control supports ISM-1544.
ISM-1544 requires implementation of Microsoft's recommended application blocklist to stop unauthorised applications from executing. E8-AC-ML3.1 requires application control on non-internet-facing servers, and Microsoft's blocklist can be used to harden the deny component of those server application control policies. E8-AC-ML3.1 is about where application control is applied, while ISM-1544 is about which Microsoft-provided block rules are implemented.
This control supports ISM-1926.
ISM-1926 reduces the attack surface of AD servers by ensuring they only perform their intended roles without unrelated services. E8-AC-ML3.1 implements application control on non-internet-facing servers, supporting ISM-1926 by preventing unauthorised executables/installers from running on AD servers. E8-AC-ML3.1 is about execution control, while ISM-1926 is focused on role exclusivity.
This control depends on ISM-1493.
ISM-1493 requires organisations to maintain and regularly verify software registers for servers and other networked equipment, identifying what software is installed. E8-AC-ML3.1 requires application control on non-internet-facing servers, which benefits from accurate knowledge of installed/required applications to define permitted execution. ISM-1493 supports E8-AC-ML3.1 by enabling validation that only approved software exists on servers, but E8-AC-ML3.1 focuses on preventing execution rather than maintaining an inventory.
ASD Essentials for enterprise IT: 1 mapping
- IT.PRO-07.1Restrict execution to supported, verified and authorised software with time-bound exceptionsPartially overlaps
This control partially overlaps IT.PRO-07.1.
IT.PRO-07.1 requires that only supported, verified and organisation-authorised software can execute; E8-AC-ML3.1 requires application control to be implemented on non-internet-facing servers, enforcing the authorisation part on one class of system.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




