Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Essential Eight Maturity Level Two

Reviewed 13 November 2026Concept 3 min read

Quick answer

Essential Eight Maturity Level Two (ML2) is the middle level of ASD's Essential Eight Maturity Model. It is designed to resist attackers who invest more time in a target and use well-known tradecraft, such as credential phishing, to get around basic controls. ML2 builds on ML1 with broader patching, stronger MFA, tighter privilege management and centralised logging.

On this page
01

What ML2 Adds

ML2 includes every ML1 requirement and raises the bar against an attacker who will spend some effort on you. In summary, the main additions are below. Confirm the exact requirements against ASD's current published model.

  • Application control: extends beyond the most common user folders to restrict executables, libraries, scripts, installers and similar file types more completely, applies to internet-facing servers as well as workstations, and logs allowed and blocked execution.
  • Patch applications and operating systems: vulnerability scanning covers a wider range of software, more applications fall within defined patching timeframes, and patching of workstations and servers is held to tighter expectations.
  • Microsoft Office macros: macro execution is further restricted, Win32 API calls from macros are blocked, and macro antivirus scanning cannot be bypassed.
  • User application hardening: office productivity suites and PDF software are hardened against common abuse such as creating child processes, and legacy or scripting components that attackers rely on, such as older PowerShell versions, are restricted, removed or logged.
  • Restrict administrative privileges: privileged access is revalidated and removed after periods of inactivity or when no longer needed, administration uses dedicated secure workstations or jump servers, local administrator passwords are unique, and privileged account activity is logged.
  • Multi-factor authentication: MFA extends to privileged users and important data repositories, phishing-resistant MFA becomes required for at least some users and services, and MFA events are logged.
  • Regular backups: privileged accounts other than backup administrators cannot read other accounts' backups, and backup deletion and modification are more tightly restricted.
  • Logging: event logs from key controls are collected centrally and protected from tampering.
02

Who Should Target It

ML2 suits organisations that are likely to be deliberately targeted: government entities, healthcare providers, financial services firms, universities, critical infrastructure suppliers and any business holding large volumes of personal information. For many Australian organisations it is the practical target level.

03

How to Test for It

  1. Run a phishing simulation that uses an adversary-in-the-middle proxy to see whether MFA can be bypassed by stealing a session.
  2. Attempt application control bypasses using scripts, libraries and trusted system binaries, not just executables. See living off the land.
  3. From a standard user foothold, attempt privilege escalation and check whether shared or stale local administrator credentials allow lateral movement.
  4. Check that privileged accounts are removed after inactivity and that administration only happens from approved hosts.
  5. Confirm blocked activity in steps 1 to 4 appears in central logs and is visible to the team responsible for responding.

These tests show whether controls withstand the tradecraft ML2 is designed for. Our guide to Essential Eight penetration testing covers how this evidence maps to each strategy.

04

How to Reach and Keep ML2

Close every ML1 gap first, because levels are cumulative. Then prioritise identity: phishing-resistant MFA, privileged access workstations and regular access reviews. Build central logging early, since several strategies depend on it. A maturity level assessment identifies the specific requirements still blocking ML2.

05

Regulatory and Framework Context

ML2 is the second level of the Essential Eight Maturity Model. It is frequently referenced in Australian government policy and procurement. For the wider context on the strategies and who must comply, see ASD Essential Eight explained. ASD revises the model periodically, so always check the current version on cyber.gov.au.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

Who needs ML2?

ML2 is a common target for government entities, organisations holding sensitive personal or financial data, and suppliers to those organisations. Many Australian government policies and contracts reference ML2 as the expected baseline.

What is the biggest jump from ML1 to ML2?

For most organisations it is privileged access management and logging. ML2 expects privileged accounts to be actively reviewed and removed when not needed, and security events to be collected centrally, which needs process as well as technology.

Does ML2 require phishing-resistant MFA?

Recent versions of the model introduce phishing-resistant MFA requirements from ML2, with the broadest scope at ML3. Check the current model on cyber.gov.au for exactly which users and services are covered at each level.

Change log

  1. 13 November 2026First published.
1300 654 898