Application control at Essential Eight Maturity Level Two
At Maturity Level Two, application control must cover workstations and internet-facing servers, apply to all locations on disk and restrict executables, libraries, scripts, installers, compiled HTML, HTML applications and control panel applets to an approved set. Microsoft's recommended blocklist is added, rulesets are validated at least annually, and allowed and blocked events are centrally logged. Read 18 Nov 2026 from ASD's maturity model and assessment guide.
What does application control require at each level?
Level One requires application control on workstations, applied at least to user profiles and temporary folders, restricting executables, software libraries, scripts, installers, compiled HTML, HTML applications and control panel applets to an organisation-approved set. Level Two adds internet-facing servers and all other locations, Microsoft's recommended application blocklist, annual ruleset validation, and central logging and analysis of allowed and blocked events.
Level Three adds non-internet-facing servers, restricts drivers to an approved set, implements Microsoft's vulnerable driver blocklist and extends log analysis to non-internet-facing servers and workstations. The strategy page sets the three levels side by side and shows which platforms evidence the strategy.
How does an assessor test application control?
The assessment guide says application control assessments can be done without tools, but the effort is severely limited and likely to miss edge cases. The most effective check is to write to and execute from every location a user can reach. For user profiles and temporary folders the guide lists the paths %userprofile%, %temp%, %tmp% and %windir%\Temp, and says to try benign files of each type: exe, com, dll, ocx, ps1, bat, vbs, js, msi, mst, msp, chm, hta and cpl. If any file runs there, application control is ineffective.
The guide names free tools for the test, among them ASD's Essential Eight Maturity Verification Tool and Application Control Verification Tool, AirLock Digital's Application Whitelist Auditor and CyberArk's Evasor. Where tools cannot run, assessors can ask for screenshots of effective access permissions, but the guide warns that unless every folder is shown, coverage will be incomplete. It also notes that some solutions do not support chm, hta or cpl files, which an assessor must then test separately.
Why does Level Two cover all locations?
Path-based rules protect only the paths they name. The guide says any path-based implementation must provide coverage for all locations on disk at Level Two, and that publisher-based and hash-based rules apply across the whole system already. The extra locations matter because an attacker who can write to a folder that is allowed to run code defeats the control.
ASD cites the in-built Microsoft solutions, AppLocker and Windows Defender Application Control, and third-party products such as AirLock Digital, Ivanti, Trend Micro and VMware Carbon Black, as examples. The examples are for illustration and are not an endorsement. ASD's FAQ also says it provides no list of approved products.
What do rulesets and logs need to show?
The assessor requests a copy of the rulesets and checks that Microsoft's recommended application blocklist is specified. For annual validation the assessor discusses how rulesets are validated, how often, and what governance surrounds changes, including testing after applications are added or removed. A ruleset that is never reviewed drifts: exploitable applications stay approved, compromised code-signing certificates stay trusted, and administrators add exceptions.
For logs the assessor asks for screenshots of records showing executable content that was allowed and content that was blocked, and checks the logs are stored centrally and protected from change. The shared Level Two items follow: events from internet-facing servers are analysed in a timely manner, incidents reach the CISO and ASD as soon as possible, and the response plan is enacted.
How does this map to ASD Essentials?
ASD's transition paper maps Application control to two enterprise IT principles, Trustworthy software and Secure configuration management. The paper also lists Application control among the principles that the Regular backups strategy contributes to. Existing application control evidence is a starting point, not a rating. Under the Essentials the same control is assessed by domain, with coverage, consistency, currency and evidence quality each affecting the rating. User devices and Business systems sit in priority phase 3 in enterprise IT. See the transition guide.
Which platforms evidence application control?
On 18 Nov 2026 Drata marks application control supported, with manual evidence examples in its help centre. Vanta marks it partial: the strategy is named as covered by the template, with no detail on the product page. 6clicks, Scrut Automation, Huntsman Security, Scytale, Secureframe and Avertro are partial. 6clicks names application allow-listing gaps on servers and operational technology as a common Level Two gap in its May 2026 blog.
None of these pages describes running ASD's write-and-execute test across user-reachable locations. A platform can hold the ruleset export and the log screenshots, and can remind a team when the annual validation falls due, which is useful because the review is easy to miss. The test itself is run by the assessor or by your team, on your machines.
Frequently asked questions
Does ASD provide a list of approved products for implementing the Essential Eight?
No. ASD says organisations should decide which products suit their own requirements. Its assessment guide names products only as illustrations and says they are not an endorsement.
Sources
- ASD, Essential Eight maturity model (November 2023), Internet Archive snapshot of cyber.gov.au, read 18 Nov 2026
- ASD, Essential Eight assessment process guide (October 2024), Internet Archive snapshot of cyber.gov.au, read 18 Nov 2026
- ASD, Essential Eight maturity model FAQ, Internet Archive snapshot of cyber.gov.au, read 18 Nov 2026
- ASD, Transitioning from the Essential Eight, Internet Archive snapshot of cyber.gov.au, read 18 Nov 2026
- Drata help centre, example evidence for not monitored controls, Essential Eight, read 18 Nov 2026
- Vanta, Essential Eight product page, read 18 Nov 2026
- 6clicks, Essential Eight Maturity Level 2 baseline blog (8 May 2026), read 18 Nov 2026
Last reviewed 18 Nov 2026