Essential Eight and Maturity Model: ML1 to ML3 Explained
Skip to content

The Essential Eight and Its Maturity Model

The Essential Eight is the Australian Signals Directorate’s (ASD) set of eight baseline cyber security mitigation strategies for internet-connected IT networks.

The Essential Eight Strategies

The Essential Eight Maturity Model rates how fully an organisation has implemented those strategies, from Maturity Level Zero to Maturity Level Three, with each level designed to resist a more capable adversary.

The November 2023 model still matters after the publication of ASD Essentials on October 15, 2026, because Commonwealth, Defence and critical infrastructure obligations continue to rely on it. ASD Essentials is ASD’s evolution of the Essential Eight and carries broader guidance, but existing Essential Eight requirements continue to apply where mandated.

The Essential Eight strategies help prevent common cyber attacks, limit the impact of a compromise and support recovery. ASD publishes them, and the same set is also known as the Essential 8, ASD Essential Eight or ACSC Essential Eight, after the Australian Cyber Security Centre.

The strategies, using ASD’s names, are:

Patch applications

Fix known application vulnerabilities within defined timeframes. Vulnerability scanning identifies missing patches and applications that need attention.

Patch operating systems

Address operating system vulnerabilities and replace operating systems no longer supported by their vendors.

Multi-factor authentication

Require authentication beyond a password for relevant online services, extending protection to privileged and unprivileged system users at higher maturity levels.

Restrict administrative privileges

Limit privileged access, use dedicated administrative accounts and environments, validate access rights and record privileged activity.

Application control

Restrict the execution of programs, scripts and installers to an organisation-approved set.

Restrict Microsoft Office macros

Disable macros where users have no business requirement and block macros in files originating from the internet.

User application hardening

Prevent browsers from processing web advertisements and Java, and apply security restrictions to browsers, Office applications and PDF readers.

Regular backups

Back up important data, applications and settings, protect backup repositories and test that information can be restored.

The strategies complement one another. Patching, application control and hardening reduce the opportunities for malicious code to run. Multi-factor authentication (MFA) and privileged access restrictions limit unauthorised access. Backups provide a way to recover when preventive controls fail.

ASD introduced the Essential Eight in 2017 as part of its broader Strategies to Mitigate Cyber Security Incidents. It was designed for internet-connected IT networks. Enterprise mobility and operational technology were outside that design.

The Essential Eight is a baseline. It was never ASD’s complete set of security recommendations, and an organisation may need additional controls based on the threats affecting its environment.

Maturity Levels and Adversary Tradecraft

Each Essential Eight maturity level is defined by the adversary tradecraft it is meant to resist. The Essential Eight Maturity Model runs from Maturity Level Zero (ML0) to Maturity Level Three (ML3). Levels One to Three address increasingly capable adversaries, and Level Zero marks weaknesses that prevent an organisation from meeting Level One.

Maturity Level Zero (ML0)

Weaknesses in the organisation’s overall cyber security posture could allow adversaries using Maturity Level One tradecraft to compromise systems or data.

Maturity Level One (ML1)

Designed to resist opportunistic attackers using widely available tools, common exploits, stolen credentials and commodity tradecraft.

Maturity Level Two (ML2)

Addresses more selective attackers who invest additional effort in phishing credentials, bypassing weak MFA and evading security controls.

Maturity Level Three (ML3)

Addresses adaptive attackers targeting particular organisations, exploiting monitoring weaknesses, using more sophisticated techniques and stealing authentication tokens to bypass stronger MFA.

The levels describe the tradecraft and targeting an organisation aims to resist. They do not identify specific threat groups, and achieving Maturity Level Three does not guarantee protection against every attacker.

How Overall Maturity Is Calculated

The Essential Eight strategies work as a package. ASD expects organisations to reach the same maturity level across all eight before progressing to the next.

Overall maturity is determined by the lowest-rated strategy.

For example, an organisation may satisfy Maturity Level Three requirements for application control, MFA and patching but meet only Level One requirements for backups. Its overall Essential Eight rating cannot exceed Maturity Level One.

An average score would hide that weakness. Under the model, gaps across the complete set of strategies have to be closed before an organisation claims a higher overall level.

The November 2023 Maturity Model

The Essential Eight Maturity Model was first published in June 2017 and last reviewed on November 27, 2023. ASD reported no updates during 2024-25.

The main changes in the November 2023 revision were:

Phishing-resistant MFA

Strengthened authentication requirements against credential phishing and authentication bypass.

Application control

Moved Microsoft’s recommended application blocklist from Maturity Level Three to Level Two and introduced annual ruleset reviews.

Regular backups

Aligned backup requirements with business criticality.

The November 2023 model is still the published Essential Eight maturity reference after the introduction of ASD Essentials in October 2026.

Requirements Across Maturity Levels

Each Essential Eight maturity level builds on the one before. Maturity Level Two includes the Level One requirements, and Level Three adds controls against more adaptive attackers and techniques.

The comparison below summarises requirements from the Information Security Manual (ISM) controls ASD associates with each maturity level. Related strategies are grouped for readability.

StrategyMaturity Level OneMaturity Level Two AddsMaturity Level Three Adds
Patch applications and operating systemsOnline services and internet-facing servers patched within 48 hours for critical or exploited vulnerabilities, and two weeks otherwise. Office suites, browsers, email clients, PDF software and security products patched within two weeks.Other applications patched within one month, with fortnightly vulnerability scanning.Office suites, browsers, workstations and internal servers patched within 48 hours for critical or exploited vulnerabilities. Drivers and firmware patched, and other unsupported applications removed.
Multi-factor authenticationMFA for online services handling sensitive data, including applicable third-party and customer services.Phishing-resistant MFA for privileged and unprivileged users of systems, with MFA events centrally logged.Phishing-resistant MFA extended to users of data repositories.
Restrict administrative privilegesDedicated privileged accounts, separate privileged environments, restrictions on privileged email and web access, and validation when access is first requested.Jump servers, revalidation after 12 months, disabling access after 45 days of inactivity, managed break-glass and service account credentials, and privileged activity logging.Just-in-time administration, Secure Admin Workstations, Credential Guard and LSA protection.
Application controlApplication control on workstations, including user profiles and temporary folders.Coverage extended to internet-facing servers. Microsoft’s recommended application blocklist, annual ruleset validation and centralised event logging.Coverage extended to non-internet-facing servers, drivers and Microsoft’s vulnerable driver blocklist.
Office macros and application hardeningMacros disabled without a business requirement and blocked in files originating from the internet. Browsers prevent processing of web advertisements and Java.Macros prevented from making Win32 API calls. Browsers, Office and PDF software hardened according to ASD and vendor guidance. PowerShell and command-line events logged.Only sandboxed, trusted-location or trusted-signed macros permitted. PowerShell Constrained Language Mode applied.
Regular backupsBackups based on business criticality, synchronised to a common point in time, stored securely, with restoration tested through disaster recovery exercises.Privileged accounts other than backup administrators prevented from accessing other accounts’ backups and from modifying or deleting backups.Privileged accounts other than backup administrators prevented from accessing their own backups. Backup administrator accounts prevented from modifying or deleting backups during retention.
Logging and incident responseNo logging requirements within the maturity model at this level.Logs protected against modification and deletion, internet-facing server logs analysed, incidents reported to ASD and incident response plans enacted.Log analysis extended to workstations and internal servers.

Maturity Level One Establishes the Baseline

Maturity Level One focuses on common attack paths. Internet-facing vulnerabilities get short patching windows, relevant online services require MFA and workstations use application control.

Administrative accounts are separated from ordinary user activity. Backups follow business criticality, and restoration is tested through disaster recovery exercises.

Meeting Level One means satisfying the requirements across all eight strategies. Selected controls on a subset of systems do not meet it.

Maturity Level Two Strengthens Access and Visibility

Maturity Level Two adds phishing-resistant MFA for system users, more extensive application control, tighter privileged access management and requirements for applications outside the main software categories.

Centralised logging and incident response become explicit requirements. Protected logs, analysis of internet-facing server activity, incident reporting and enacted response plans give an organisation the means to investigate activity that preventive controls do not stop.

Privileged access also requires periodic revalidation, inactivity checks and controls around administrative environments.

Maturity Level Three Extends Protection

Maturity Level Three extends controls to more systems and attack techniques. Application control reaches non-internet-facing servers and drivers, and critical or exploited vulnerabilities face shorter remediation windows across more software categories.

Stronger administrative protection includes just-in-time access and Secure Admin Workstations. Backup permissions become more restrictive, and event analysis extends to workstations and internal servers.

An organisation targeting Level Three must also keep meeting every applicable Level One and Level Two requirement.

The comparison above is a summary. For a complete implementation checklist, the authoritative requirements remain in ASD’s Essential Eight Maturity Model, including its appendices comparing maturity levels.

Choose a Target Maturity Level

The right Essential Eight maturity target depends on the organisation’s threat environment, the consequences of compromise and any government, regulatory or contractual obligation that applies.

ASD’s general guidance suggests:

Maturity Level One

May be suitable for small and medium enterprises.

Maturity Level Two

May be suitable for large enterprises.

Maturity Level Three

May be suitable for critical infrastructure providers and organisations operating in high-threat environments.

These are general recommendations and carry no mandate of their own. Where an obligation specifies a maturity level, that requirement sets the minimum target regardless of the organisation’s preferred level.

ASD Essentials explained covers policies and regulations referencing the Essential Eight. ASD Essentials for government examines the PSPF and compares published Commonwealth maturity figures.

Defence Industry Requirements

The Defence Industry Security Program (DISP) requires its members to meet the full Essential Eight at Maturity Level Two.

Assessments against the “top 4” concluded on November 15, 2025. Part B of the DISP questionnaire now contains 107 Essential Eight controls aligned with Maturity Level Two.

For DISP members, Level Two is an applicable requirement, whatever ASD’s general recommendations suggest for an organisation of their size.

Critical Infrastructure Requirements

Enhanced risk management rules under the Security of Critical Infrastructure (SOCI) framework, introduced in June 2026, accept Maturity Level Two for listed asset classes, subject to a 24-month grace period. Maturity Level One remains the baseline option.

The relevant asset class and applicable risk management obligations determine what an operator needs to implement. A general recommendation to target Level Three does not replace those requirements.

Account for Other Security Obligations

ASD’s maturity model FAQ adds limits that apply when a target is set.

Cyber insurance

Insurance cannot substitute for an Essential Eight mitigation strategy. An organisation relying on insurance instead of implementing a strategy is assessed at Maturity Level Zero.

ISM requirements

Essential Eight maturity and ISM obligations are considered independently. An organisation required to meet Maturity Level Two may still need ISM controls mapped to Level Three because of its data classification.

Implement and assess each maturity level in turn until the target is reached. Higher-level controls can be introduced earlier where practical, but having them in place does not show that the complete lower level has been met.

Mapping Strategies to ASD Essentials

ASD Essentials carries the Essential Eight strategies into a broader set of principles, actions and domains. Every Essential Eight strategy contributes to one or more principles in ASD Essentials for enterprise IT.

The Essential Eight remains relevant wherever existing obligations require it. ASD Essentials, published on October 15, 2026, extends ASD’s guidance beyond the original fixed set of strategies, but its publication does not automatically replace those obligations.

The mapping below follows Table 2 of ASD’s transition guidance.

Essential Eight strategyASD Essentials principlesRead more
Patch applicationsVulnerability management; Asset identification; Legacy system managementBoundary services
Patch operating systemsVulnerability management; Asset identification; Legacy system managementBoundary services
Multi-factor authenticationIdentity, credential and access managementIdentity services
Restrict administrative privilegesIdentity, credential and access management; Least privilege access; Secure administration; Network segmentation and segregationPrivileged environments
Application controlTrustworthy software; Secure configuration managementBusiness systems
Restrict Microsoft Office macrosTrustworthy software; Secure configuration managementUser devices
User application hardeningSecure configuration managementUser devices
Regular backupsRegular and proven backups; Least privilege accessBusiness systems

The mapping identifies the relevant principles. It does not make the assessment outcomes equivalent.

For example, existing application control may support the Trustworthy software principle, but its evidence still has to show coverage within the applicable ASD Essentials domain. A control that satisfied an Essential Eight requirement is not necessarily effective everywhere the new principle applies.

Logging and incident response previously appeared within individual Essential Eight strategies. ASD Essentials gives these capabilities dedicated principles, explained in the ASD Essentials Visibility and response guide.

The complete framework structure and domain scope are covered in ASD Essentials explained.

Evidence to Collect for Essential Eight Maturity

Essential Eight maturity evidence can support ASD Essentials, but maturity ratings do not automatically convert into effectiveness ratings. The configurations, test results and operating records behind a rating are more useful than the overall maturity score.

ASD says organisations at Maturity Level Two can expect many existing controls to contribute to actions in the early priority phases, while organisations at Level Three are likely to reuse a broader range of evidence. Level One provides a foundation, but more actions may need further work.

The table lists evidence typically produced during Essential Eight maturity assessments, how to collect it and the ASD Essentials actions it can support. The collection methods are common practice rather than ASD requirements.

EvidenceHow to get itWhat it should show
E8MVT outputKeep the dated report from each Essential Eight Maturity Verification Tool run, including the hosts tested and how they were selected.Which maturity requirements the tested systems met. ASD Essentials treats sample results with care because they do not automatically demonstrate an outcome across the entire domain, so record the domain each host belongs to.
Application Control Verification Tool resultsKeep results for each sampled workstation and server, including the test date and host name.Application control blocks unapproved execution on workstations from Maturity Level One and on internet-facing servers from Level Two, supporting the trustworthy software action (IT.PRO-07.1).
Patch timeframe reportExport patch age per system from the patch management or vulnerability tool, grouped into the 48-hour, two-week and one-month windows.Each system class met its maturity level timeframe. ASD’s transition guide notes that applicable ISM, regulatory and other mandatory timeframes continue to apply alongside risk-based treatment (IT.PRO-06.2).
Authentication method registration reportExport registered authentication methods for each user from the identity provider, identifying phishing-resistant methods for privileged and unprivileged users.Phishing-resistant MFA is in place as Maturity Level Two requires. The report can also show coverage for each applicable domain (IT.PRO-13.4).
Privileged access revalidation recordExport privileged accounts with their last revalidation date and last sign-in, together with accounts disabled after 45 days of inactivity.Privileged access was revalidated within 12 months and inactive access disabled, as Maturity Level Two requires. The records also support periodic access review (IT.PRO-12.1).
Backup access permissionsExport roles and accounts with access to each backup repository from the backup console, identifying which can modify or delete backups.Only backup administrators can modify or delete backups, as Maturity Level Two requires, and repository access is isolated from the primary identity environment (IT.PRO-10.2).
Restoration test recordKeep records of disaster recovery exercises, including systems restored, the common point in time used and the recovery times achieved.Restoration was tested as Maturity Level One requires. ASD Essentials also asks whether recovery met the defined recovery time and recovery point objectives (IT.PRO-10.3).

Preserve the Assessment Context

A useful maturity evidence record identifies the system tested, the collection date, the applicable requirement and the observed result.

For sampled systems, record how the samples were selected and which environment or domain they represent. A passing result on one workstation does not show that every workstation, or the broader environment, has the same configuration.

Tool output and system exports dated within the assessment period are usually stronger evidence than screenshots alone. Screenshots remain useful when they clearly identify the date, host and tenant.

The maturity result records what was deployed when the assessment occurred. ASD’s assessment process guide marks the limit of that record in one sentence: Deployment is not effectiveness.

Reuse Evidence Where It Applies

An Essential Eight assessment shows that controls were configured and tested against particular maturity requirements. ASD Essentials also considers whether the relevant actions achieve their intended outcomes across the applicable domain.

For example, an MFA registration export may show phishing-resistant methods for the users included in the original assessment. The same evidence can support IT.PRO-13.4, provided its coverage and currency are appropriate to the domain being assessed.

Keep the link between each record, its original maturity requirement and the ASD Essentials action it supports. Gaps in system coverage or evidence should stay visible and never be counted as successful results.

The broader transition process, gap analysis and reuse of assessment reports and registers are covered in Essential Eight vs ASD Essentials.

Maturity Evidence With ThreatDefence

ThreatDefence operates a 24x7 SOC with its team based in Australia, providing a 3 min average response under guaranteed SLAs. Threat hunting and an incident response retainer are included in the standard service.

Response actions remain within the authority each customer approves. Case records can be exported for an assessor or at the end of a contract. Australian customers’ data and AI processing remain in Australia.

ThreatDefence does not certify organisations. The assessor determines ASD Essentials ratings.

Maturity Level Two and Three adversaries actively phish credentials, bypass weak MFA and steal authentication tokens. ThreatDefence ITDR detects session token replay, where a stolen session token may allow an attacker to bypass MFA.

The free ASD Essentials Navigator maps every principle and action by chapter and priority phase, and converts ratings into a board summary. Readers new to the framework can start with the five-minute ASD Essentials explainer, which walks through principles, actions, domains, priority phases and ratings.

A Microsoft 365 forensic scan in the ThreatDefence portal with sign-ins by risk, MFA coverage, app consents, findings and response actions

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    What are the eight strategies in the Essential Eight?

    The eight strategies are patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups.

    Together they reduce opportunities for compromise, restrict unauthorised access and support recovery. ASD designed the strategies as a complementary package, so an organisation implements all eight and does not pick individual controls. Each strategy also maps to relevant principles within ASD Essentials.

    Is the Essential Eight still required?

    Yes, the Essential Eight remains required wherever an existing policy, regulation or contractual obligation specifies it. The PSPF and DISP require Maturity Level Two, while SOCI risk management rules recognise the Essential Eight among accepted frameworks.

    ASD Essentials was published on October 15, 2026, but its publication did not automatically remove existing Essential Eight obligations. Organisations should continue meeting current requirements until the relevant authorities communicate changes.

    Is the ACSC Essential 8 the same as the Essential Eight?

    Yes. ACSC Essential 8, ASD Essential Eight, Essential Eight and Essential 8 refer to the same set of mitigation strategies published by the Australian Signals Directorate on cyber.gov.au.

    The framework contains eight strategies assessed using the Essential Eight Maturity Model. ASD Essentials is ASD’s broader evolution of it, with principles, actions and domains, but the original model remains published and relevant to existing obligations.

    What is Maturity Level Zero?

    Maturity Level Zero means there are weaknesses in an organisation’s overall cyber security posture that adversaries using Maturity Level One tradecraft could exploit.

    An organisation is also rated at Level Zero when it relies on cyber insurance instead of implementing an entire mitigation strategy, according to ASD’s maturity model FAQ. Because overall maturity follows the lowest-rated strategy, a single strategy assessed at Level Zero prevents the organisation from claiming a higher overall level.

    What is Essential Eight Maturity Level Two?

    Maturity Level Two is designed to resist more selective adversaries who actively phish credentials, bypass weak MFA and attempt to evade security controls.

    Requirements include phishing-resistant MFA for system users, additional application control, privileged access protections, centralised logging and incident response. Level Two is required for non-corporate Commonwealth entities under the PSPF and for DISP members. ASD’s general guidance also suggests it may suit large enterprises.

    Is Maturity Level Three required?

    No, Maturity Level Three is not a general requirement for most organisations. ASD identifies critical infrastructure providers and organisations operating in high-threat environments as potential candidates.

    The PSPF and DISP specify Level Two, while relevant SOCI and state requirements generally identify lower targets. An organisation’s contracts or threat assessment may justify Level Three. The appropriate target depends on applicable obligations and the consequences of compromise.

    Can an organisation be partially mature across the Essential Eight?

    Yes. Individual Essential Eight strategies can be assessed at different maturity levels, but the organisation’s overall maturity is determined by the lowest-rated strategy.

    For example, meeting Level Three for most strategies and Level One for another produces an overall rating no higher than Level One. ASD expects organisations to reach the same level across all eight before progressing, because stronger controls in one area do not automatically compensate for a weaker strategy elsewhere.

    Which maturity level introduces logging requirements?

    Maturity Level Two introduces logging and incident response requirements within the Essential Eight Maturity Model. Level One has no logging requirements in the model.

    Level Two includes centralised MFA event logging, protection against log modification and deletion, analysis of internet-facing server logs, incident reporting and enacted response plans. Level Three extends log analysis to workstations and internal servers. ASD Essentials addresses these capabilities through dedicated principles, including DET-01 Centralised event logging.

    When was the Essential Eight Maturity Model last updated?

    The Essential Eight Maturity Model was last updated in November 2023, with ASD recording its last review on November 27, 2023. ASD reported no updates during 2024-25, and no later model release had appeared by late 2026.

    The revision required phishing-resistant MFA, moved Microsoft’s recommended application blocklist to Level Two with annual ruleset reviews and aligned backups with business criticality. ASD Essentials followed on October 15, 2026.

    Can Essential Eight maturity levels convert to ASD Essentials ratings?

    No. ASD states that Essential Eight maturity levels do not automatically convert to ASD Essentials effectiveness ratings because the frameworks assess different things.

    Existing controls and current evidence may support corresponding ASD Essentials actions, but each applicable domain is assessed against its intended security outcomes. Priority phases set the order of implementation and are not maturity levels. An organisation with a previous Level Two or Three result still needs to show effectiveness for the relevant ASD Essentials actions.