Skip to content
Application control
Essential EightE8-AC-ML2.2

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).

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

  1. 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.

  2. 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.

  3. 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

  1. 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.

  2. 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 27001

ISO/IEC 27001: 2 mappings

  • A.8.18Use of privileged utility programsPartially overlaps
ASD ISM

ASD Information Security Manual: 10 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.