Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Essential Eight Maturity Model

Reviewed 13 November 2026Concept 3 min read

Quick answer

The Essential Eight Maturity Model is the Australian Signals Directorate's framework for measuring how well an organisation has implemented eight baseline mitigation strategies. Each strategy is rated from Maturity Level Zero to Maturity Level Three, where each level is designed to resist a progressively more capable adversary. Organisations choose a target level based on the threats they face.

On this page
01

How It Works

The model takes ASD's eight baseline strategies and defines what each must look like at three maturity levels:

  • Application control
  • Patch applications
  • Configure Microsoft Office macro settings
  • User application hardening
  • Restrict administrative privileges
  • Patch operating systems
  • Multi-factor authentication
  • Regular backups

Each level is built around the adversary it is meant to stop:

LevelDesigned to resist
ML0Nothing reliably. The requirements of ML1 are not fully met.
ML1Opportunistic attackers using commodity tools and publicly available exploits against whoever is vulnerable.
ML2Attackers willing to invest more time and use well-known tradecraft, such as credential phishing, to bypass controls.
ML3Adaptive adversaries who target specific organisations, exploit weaknesses quickly and work to evade controls and detection.

Levels are cumulative: ML2 includes everything in ML1 plus more, and ML3 includes everything in ML2. Requirements escalate in predictable ways as you climb. Patching timeframes shorten, application control extends from workstations to servers, MFA expands from internet-facing services to privileged users and important data repositories, phishing-resistant MFA becomes the expectation, and event logging moves from optional to centralised and actively analysed.

The model is written primarily for Microsoft Windows based, internet-connected networks. It can be applied to other environments, but some controls need interpretation.

02

How Maturity Is Assessed

ASD publishes an assessment process guide that describes how assessors should gather and weigh evidence. In broad terms:

  1. Agree the scope: which systems, networks and business units are being assessed.
  2. Test each control against every requirement of the target level, strategy by strategy.
  3. Weigh the evidence. ASD's guidance treats directly testing a control, for example attempting to run an unapproved program, as stronger evidence than reviewing configuration, which in turn is stronger than reading a policy or interviewing staff.
  4. Record a maturity level for each strategy. A strategy only reaches a level when every requirement of that level is met, and documented exceptions are considered.
  5. Report the gaps that prevent the next level, with a plan to close them.

ASD also provides free tooling to help gather technical evidence, and a maturity level assessment uses this kind of structured approach to give you a reliable baseline.

03

Why It Matters

Self-assessments routinely overstate maturity. A control may be configured on most machines but not all, an exception may have quietly become permanent, or MFA may be bypassable through a legacy protocol. Because a level is only met when every requirement is met everywhere in scope, small gaps decide the result.

04

How Testing Fits

A maturity assessment shows whether controls are in place. Offensive testing shows whether they hold. Operators attempt to run code past application control, escalate privileges, defeat MFA and reach backups, and the results are mapped back to the relevant strategies. Our guide to Essential Eight penetration testing covers this in depth, and ASD Essential Eight explained covers the strategies and who must comply.

05

Regulatory and Framework Context

The Essential Eight is mandated for non-corporate Commonwealth entities under the Protective Security Policy Framework, adopted by many state and territory governments, and listed at Maturity Level One as one of the frameworks a responsible entity can use under the SOCI Act risk management program rules. APRA-regulated entities commonly use it as evidence of control effectiveness under CPS 234. Always check requirements against the current model and assessment guidance published by ASD on cyber.gov.au.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

Is the Essential Eight mandatory?

It is mandated for non-corporate Commonwealth entities under the Protective Security Policy Framework. For most other organisations it is voluntary, but it is widely expected by state agencies, insurers, customers and boards, and it is one of the cyber frameworks recognised under the SOCI Act risk management program rules.

Can we be at different levels for different strategies?

Yes. Each strategy is assessed on its own, so a typical result is a profile such as ML2 for backups and MFA but ML1 for application control. ASD recommends reaching your target level across all eight strategies before aiming higher on any one of them.

How often does ASD update the model?

ASD revises the model periodically to reflect how adversaries operate, and recent updates have tightened patching timeframes and expanded phishing-resistant MFA. Always assess against the current version published on cyber.gov.au rather than an older copy.

Change log

  1. 13 November 2026First published.
1300 654 898