Essential Eight
User Application Hardening in the Essential Eight Explained
30 Aug 2026 · Updated 30 Aug 2026
User application hardening reduces the attack surface of the applications attackers target most, browsers, Microsoft Office and PDF software, by turning off risky and legacy features. It moves from disabling Internet Explorer, Java and web ads at Maturity Level One, through blocking Office and PDF from spawning processes and logging PowerShell at Level Two, to removing old .NET and PowerShell and constraining PowerShell at Level Three.
Attackers go where the users are, and users spend their day in a browser, in Office and in PDFs. This strategy makes those applications harder to exploit by switching off the features attackers reach for.
What is user application hardening in the Essential Eight?
User application hardening is the Essential Eight strategy that reduces the attack surface of the applications most often targeted, chiefly web browsers, Microsoft Office and PDF software. Rather than adding a new control on top, it removes capabilities these applications have that attackers abuse and that most users never need.
The idea is that a lot of an application’s risk comes from features that are legacy, rarely used, or dangerous by design. A browser that can run Java from the internet, an Office application that can spawn other programs, an old scripting engine left enabled, each is a capability an attacker can turn against the organisation. Hardening switches these off. It starts with the browser, the application most exposed to hostile content, and extends to Office and PDF software and to the Windows scripting environment. Because it works by disabling and configuring rather than deploying new tools, much of it can be delivered through group policy, though the higher levels require careful testing so legitimate work is not broken.
What does user application hardening require at each maturity level?
The strategy moves from disabling obvious risks in the browser at Level One, to hardening Office and PDF and logging script activity at Level Two, to removing legacy runtimes and constraining PowerShell at Level Three. Each level includes the ones below.
| Level | What is required |
|---|---|
| Maturity Level One | Internet Explorer 11 disabled or removed; web browsers do not process Java or advertisements from the internet; users cannot change browser security settings |
| Maturity Level Two | Browsers, Office and PDF software hardened using ASD and vendor guidance; Office and PDF blocked from creating child processes, creating executable content and injecting code; Office prevented from activating OLE packages; PowerShell and command line process creation centrally logged |
| Maturity Level Three | .NET Framework 3.5 and Windows PowerShell 2.0 disabled or removed; PowerShell configured to use Constrained Language Mode |
The progression narrows what these applications can do, and adds visibility over the scripting an attacker would use. How the levels map to attacker capability is set out in the Essential Eight maturity levels.
Why does the Essential Eight block web advertisements and Java?
Web advertisements and Java in the browser are historic sources of drive by compromise, where loading a page is enough to run malicious code without any further user action. Blocking both at Maturity Level One removes two of the oldest and most reliable browser attack paths.
Malicious advertising, or malvertising, is the reason ads are blocked. Ad networks serve content from many sources onto otherwise legitimate sites, and attackers have repeatedly used them to deliver exploit code to visitors of trusted pages. The user does nothing wrong, they visit a normal site, and a poisoned ad does the rest. Java in the browser is blocked for a similar reason: it has a long history of serious, widely exploited vulnerabilities, and very few modern sites still need it. Note the precision here, the control blocks Java, not JavaScript, which is a different technology the web depends on. By stopping browsers from processing Java and internet advertisements, the strategy closes paths that require no user mistake at all.
What does user application hardening do with PowerShell?
User application hardening targets PowerShell because it is one of the tools attackers rely on most. PowerShell is powerful, built into Windows, and trusted, which makes it ideal for running malicious code while blending in with legitimate administration, a technique that evades signature based detection.
The strategy handles PowerShell in two stages. At Maturity Level Two, it requires PowerShell module logging, script block logging and transcription events to be centrally logged, along with command line process creation, so that malicious use is visible and can be investigated. At Maturity Level Three, it disables or removes the old Windows PowerShell 2.0, which lacks these logging capabilities and is often abused to evade them, and it configures PowerShell to use Constrained Language Mode, which limits the more dangerous things a script can do while still allowing normal administrative tasks. The combination means an attacker cannot easily fall back to an unlogged, unrestricted version of PowerShell. For an organisation hardening user applications to meet an Essential Eight target, Cybernion helps through Essential Eight advisory and assessment.
Frequently asked questions
What is user application hardening in the Essential Eight?
User application hardening is the Essential Eight strategy that reduces the attack surface of the applications attackers target most, chiefly web browsers, Microsoft Office and PDF software, by disabling risky and legacy features. At Maturity Level One it requires Internet Explorer 11 to be disabled or removed, web browsers to not process Java or web advertisements from the internet, and users to be unable to change browser security settings.
What does user application hardening require at each maturity level?
At Maturity Level One, Internet Explorer 11 is disabled or removed, browsers do not process Java or advertisements from the internet, and users cannot change browser security settings. At Maturity Level Two, browsers, Office and PDF software are hardened using ASD and vendor guidance, Office and PDF are blocked from creating child processes and executable content, and PowerShell and command line activity is logged. At Maturity Level Three, .NET Framework 3.5 and Windows PowerShell 2.0 are removed and PowerShell runs in Constrained Language Mode.
Why does the Essential Eight block web advertisements and Java?
Web advertisements and Java are historic sources of drive by compromise, where simply loading a page can run malicious code. Malicious advertising, known as malvertising, can serve exploit code through ad networks on otherwise legitimate sites, and Java in the browser has a long record of serious vulnerabilities. Blocking browsers from processing Java and advertisements from the internet removes two well worn paths for compromising a user without any action beyond visiting a page.
What does user application hardening do with PowerShell?
User application hardening targets PowerShell because attackers use it heavily to run code while blending in with legitimate administration. At Maturity Level Two, PowerShell module logging, script block logging and transcription events are centrally logged, along with command line process creation. At Maturity Level Three, the old Windows PowerShell 2.0 is disabled or removed and PowerShell is configured to use Constrained Language Mode, which limits what scripts can do while preserving normal administrative use.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Essential Eight maturity model, Australian Signals Directorate, 27 November 2023
- Essential Eight assessment process guide, Australian Signals Directorate, 2 October 2024
- Essential Eight maturity model FAQ, Australian Signals Directorate, 28 October 2024
Last updated: 30 August, 2026
