🇦🇺 Australia · Framework guide

Essential Eight: what each maturity level actually requires

The Essential Eight is the Australian Cyber Security Centre’s baseline of eight mitigation strategies, assessed at four maturity levels. This guide explains the strategies, the levels, who is mandated to meet them and how to get from a self-assessment to evidence an assessor will accept.

PublisherAustralian Cyber Security Centre (ACSC), part of the Australian Signals Directorate
Current modelEssential Eight Maturity Model, November 2023 update
Structure8 mitigation strategies × Maturity Levels 0–3
Mandated forNon-corporate Commonwealth entities (PSPF requires ML2 across all eight)
AssessmentACSC Essential Eight Assessment Process Guide; self-assessed or assessed by an ASD-endorsed assessor
Platform focusDesigned for Microsoft Windows enterprise networks

The Essential Eight was chosen because these eight controls, done properly, block the large majority of commodity intrusions the ACSC sees. The model is deliberately prescriptive: for each strategy it says exactly what “done” looks like at each maturity level, down to the setting. That is what makes it easy to assess and hard to fake.

Maturity is scored per strategy, and your overall maturity is the lowest level you reach across all eight. An organisation at ML3 on seven strategies and ML1 on backups is at ML1.

The eight strategies

Application control

Only approved executables, scripts, installers and DLLs run on workstations and servers. From ML2, Microsoft’s recommended block rules are applied; at ML3, driver control and centralised logging are added. In practice this means Windows Defender Application Control (WDAC) or AppLocker with a maintained allow-list.

Patch applications

Vulnerability scanning plus patching of internet-facing services within 48 hours when an exploit exists (within two weeks otherwise), and removal of applications the vendor no longer supports.

Configure Microsoft Office macro settings

Macros blocked for users with no business need, blocked from internet-sourced files, antivirus scanning of macros, and users unable to change the settings. Higher levels require macros to run only from trusted locations or be digitally signed.

User application hardening

Web browsers cannot process Java or web advertisements, Internet Explorer 11 is disabled or removed, Office cannot create child processes or inject code, PowerShell is constrained and logged.

Restrict administrative privileges

Privileged access is requested and validated, reviewed at least annually, separated from internet and email use, and uses dedicated privileged operating environments. Local administrator passwords are unique and managed (LAPS); at ML3 just-in-time administration is required.

Patch operating systems

Same cadence as applications: 48 hours for exploited vulnerabilities on internet-facing systems, no unsupported operating systems, and vulnerability scanning to prove it.

Multi-factor authentication

MFA for all remote access, for all privileged access, for internet-facing services holding sensitive data and, from ML2, phishing-resistant MFA for privileged users. At ML3, MFA is phishing-resistant for everyone and MFA events are logged and monitored.

Regular backups

Backups of data, applications and settings taken and retained according to business continuity requirements, tested as part of disaster recovery exercises, and protected so that unprivileged accounts cannot modify or delete them.

The maturity levels

  1. Maturity Level 0. Weaknesses that a commodity adversary could exploit. The starting point for most organisations that have never been assessed.
  2. Maturity Level 1. Mitigates adversaries using widely available tooling and opportunistic techniques. The minimum most insurers and supply-chain questionnaires now ask about.
  3. Maturity Level 2. Mitigates adversaries willing to invest more time and tooling in a target. The level the Protective Security Policy Framework requires of non-corporate Commonwealth entities.
  4. Maturity Level 3. Mitigates adaptive adversaries who develop custom tooling. Required for systems of national significance and increasingly expected of critical infrastructure.

Who it applies to

Non-corporate Commonwealth entities must implement all eight strategies at ML2 under the PSPF. State and territory governments, critical infrastructure operators under the SOCI Act, Defence Industry Security Program members and APRA-regulated firms are not legally bound to the model but are routinely measured against it by auditors, insurers and customers. Most private-sector boards now set ML1 or ML2 as an explicit target.

How GRCorb covers ACSC Essential Eight

From scope to evidence, in one system

Engineering depth, not a checklist

GRCorb Engineering carries build instructions for each strategy at each level: WDAC policy structure for application control, Intune compliance and update rings for patching, Office cloud policies for macros, Conditional Access and authentication strengths for MFA, LAPS and Privileged Identity Management for administrative privileges. Each instruction has a validation test and the evidence an assessor expects.

Evidence collected from Microsoft

Read-only adapters for Microsoft Entra ID, Intune and Defender pull the settings and device state that prove each strategy, timestamp and hash them, and mark them fresh, stale or missing. No screenshots emailed to anyone.

Maturity scored the ACSC way

Scoring follows the Assessment Process Guide: per strategy, per level, with the overall result set by the weakest strategy, so the number you report matches what an ASD-endorsed assessor would find.

Client-branded assessment report

For MSSPs and consultants, every assessment prints as a client-branded report with the maturity position, the gaps and the engineering work to close them, in one click.

Frequently asked questions

Which maturity level should we target?

ML2 if you are a Commonwealth entity or sell to one, or if the board wants a defensible target. ML1 is a reasonable first milestone for an organisation that has never been assessed; the November 2023 update made ML1 harder than it used to be, so do not assume it is trivial.

Is the Essential Eight mandatory for private companies?

Not by statute. It becomes mandatory by contract, by insurer requirement or by board policy. Supply-chain questionnaires from government and large enterprises almost always ask for your maturity level.

How often should we reassess?

The ACSC recommends assessing continuously rather than annually, since maturity is lost the moment a patch window is missed. GRCorb re-validates the technical strategies from live Microsoft data on a schedule you set.

Does it cover macOS and Linux?

The model is written for Windows-based networks. The principles apply elsewhere, but the maturity criteria assume Microsoft tooling. Organisations with mixed estates usually pair the Essential Eight with the ISM or ISO 27001 for the rest.

Related frameworks

Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.