Essential Eight AC-ML2.2 Extend application control beyond user profiles and temporary folders
What it says
Application control is applied to all locations other than user profiles and temporary folders used by operating systems, web browsers and email clients.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Application control must also apply in every location beyond user profiles and temporary folders, which stay covered under E8-AC-ML1.2, so no folder is left out.
Application control, which lets only approved files run, must cover all remaining locations: everywhere other than user profiles and the temporary folders that operating systems, web browsers and email clients use. Those folders are covered from Maturity Level One (E8-AC-ML1.2) and stay covered, so this extends coverage rather than excluding anything. At Maturity Level Two every location is covered, including other drives and folders standard users can write to inside the Windows and program folders, on workstations and internet-facing servers (E8-AC-ML2.1).
Free. Save your status, tasks and notes.
Why it matters
Malicious code does not need a profile or temp folder. Without this coverage, any other folder a user or attacker can write to, such as one inside the Windows folder, lets them save and run an unapproved program.
How to implement
Find every folder standard users can write to.
Use a permissions-checking tool on each workstation build and each internet-facing server, across all drives, including folders inside the Windows and program folders. Account for every group a standard user belongs to, and include network shares your rules let programs run from.
Close each gap the list shows.
Where a path rule allows a writable folder, remove the write permission if nothing needs it, or add an exception to the rule so it no longer allows that folder. For software that must sit in a writable folder, allow its files by publisher or hash, which do not depend on location.
Test from every writable folder.
As a standard user, save harmless test files of each type in E8-AC-ML1.3 in each writable folder found, including on removable drives, and try to run them. Anything that runs is a gap. Repeat the profile and temp folder tests, which must still pass.
Keep it running
Rerun the writable-folder check after installing or upgrading software, because installers can create folders that standard users can write to. Keep user profile and temporary folder coverage in place through every rule change.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
A list of folders a standard user can write to, produced by a permissions-checking tool on workstations and internet-facing servers chosen by the assessor.
Look at
Whether a path rule or exclusion lets files run from any of those folders, on any drive.
Good evidence
No folder a standard user can write to, on any drive, is allowed by a path rule or excluded from application control.
- Check 2 of 2What an auditor asks for
Ask for
A demonstration on workstations and internet-facing servers chosen by the assessor, signed in as a standard user, of saving harmless test files of each type in E8-AC-ML1.3 in writable folders the assessor picks, outside the user profile and temporary folders, and trying to run them.
Look at
Whether any test file runs, and whether the same files are still blocked in the user profile and temporary folders.
Good evidence
No test file runs from any writable folder tested, and the same files are still blocked in the user profile and temporary folders.
Mappings
Closest match in ASD Information Security Manual: ISM-1871, Apply application control to all other locations, which asks for the same thing.
ISO/IEC 27001: 2 mappings
This control partially overlaps A.8.18.
Annex A 8.18 requires restrictions and tight control over utilities that can override system and application controls, which includes preventing unauthorised execution paths on operational systems. E8-AC-ML2.2 relates by applying application control broadly and explicitly excluding user profiles and temporary folders, reducing the ability to execute installers or utility programs from common user-writable locations. However, Annex A 8.18 is focused on controlling powerful utilities and administrative override capability, whereas E8-AC-ML2.2 is primarily about execution control coverage across filesystem locations rather than privileged utility governance.
This control partially overlaps A.8.19.
E8-AC-ML2.2 specifies control with folder exclusions, whereas Annex A 8.19 involves managing software installation security. Both address unauthorised code execution but differ in exclusion details.
ASD Information Security Manual: 10 mappings
This control is equivalent to ISM-1871.
ISM-1871 requires application control to be applied to all locations except user profiles and temporary folders used by operating systems, web browsers, and email clients. E8-AC-ML2.2 states the same exclusion approach for application control with the same key locations and rationale. Both controls have matching scope and intent (implementing application control broadly while excluding high-churn user/temp paths).
This control partially meets ISM-0843.
E8-AC-ML2.2 requires application control to be applied across system locations, explicitly excluding user profiles and temporary folders used by operating systems, web browsers and email clients. ISM-0843 requires application control to be implemented on workstations, which is a platform-scoped requirement that would typically include applying controls across workstation execution paths. ISM-0843 does not express the specific location-based scoping/exclusions that E8-AC-ML2.2 mandates.
This control partially overlaps ISM-0846.
E8-AC-ML2.2 requires application control coverage across locations (with defined exclusions for user profiles and temporary folders). ISM-0846 requires that users (except local administrators and break glass accounts) cannot disable, bypass or be exempted from application control, which helps ensure the location-based enforcement in E8-AC-ML2.2 cannot be circumvented by standard users. E8-AC-ML2.2 is about where application control is applied, while ISM-0846 is about preventing user-driven weakening of that control.
This control partially overlaps ISM-0955.
ISM-0955 requires implementing application control using hash, publisher certificate, or path rules to control what can execute. E8-AC-ML2.2 specifies where application control must be applied by excluding user profiles and temporary folders from enforcement at that maturity level, which affects the scope of application control deployment. ISM-0955 is about rule types and does not define location-based exclusions, while E8-AC-ML2.2 is primarily about coverage boundaries rather than rule mechanics.
This control partially overlaps ISM-1657.
ISM-1657 requires application control that restricts execution to an organisation-approved set of executable artefacts. E8-AC-ML2.2 requires application control be applied to all locations other than user profiles and temporary folders, which is a particular scoping decision about where enforcement occurs. They overlap because both are about implementing execution control, but ISM-1657 is agnostic about location scoping while E8-AC-ML2.2 focuses on enforcement coverage decisions rather than the approved-set definition itself.
This control supports ISM-1544.
ISM-1544 requires implementing Microsoft's recommended application blocklist to block known undesirable/unauthorised applications. E8-AC-ML2.2 requires application control to be applied broadly (to all locations other than user profiles and temporary folders), and the Microsoft blocklist can be embedded within those rules to improve blocking effectiveness. E8-AC-ML2.2 is primarily about ruleset coverage by location, while ISM-1544 is about adopting Microsoft's recommended block content.
This control depends on ISM-1392.
E8-AC-ML2.2 requires broad application control with folder exclusions. ISM-1392 complements by ensuring only approved users can modify files, reducing risks like path-rule bypass.
This control depends on ISM-1490.
ISM-1490 requires implementing application control on internet-facing servers. E8-AC-ML2.2 refines how application control is applied by excluding user profiles and temporary folders, which affects the effectiveness and operational design of application control rules. E8-AC-ML2.2 supports ISM-1490 by providing a specific scoping approach for rulesets, but ISM-1490 does not mandate this particular location-based treatment.
This control depends on ISM-1656.
ISM-1656 requires application control to be implemented on non-internet-facing servers to stop unapproved code from running. E8-AC-ML2.2 specifies how application control is applied across locations (excluding user profiles and temporary folders), which influences the effectiveness and coverage of application control where it is implemented. It supports ISM-1656 by guiding deployment scope decisions for application control, but it is not the same requirement as implementing it on non-internet-facing servers.
This control depends on ISM-1746.
E8-AC-ML2.2 enforces control excluding certain folders, while ISM-1746 maintains file system integrity, preventing unauthorised permission changes, supporting application control effectiveness.
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-ML2.2 applies application control to all locations other than user profiles and temporary folders used by operating systems, web browsers and email clients, enforcing the authorisation part in the remaining locations.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




