From the Essential Eight to ASD Essentials: what changes for your organisation
In October 2026 the Australian Signals Directorate released the Essentials series, the evolution of the Essential Eight. Your Essential Eight work carries forward, but it is scoped and assessed differently. This page explains the new model, how each of the eight strategies maps across, and where most organisations will need more work.
The Essential Eight did not fail. The threat moved on.
ASD published ASD Essentials for enterprise IT on 15 October 2026, alongside chapters for operational technology and cloud. ASD describes it as a broader, principles-based, threat-informed approach, and says the Essential Eight remains effective but was built for enterprise IT networks as they were in 2017. Transitional arrangements continue into 2027, and organisations must keep meeting any regulatory or contractual obligation that still asks for Essential Eight reporting.
Five ideas that change between the two frameworks
| Essential Eight | ASD Essentials | What it means in practice |
|---|---|---|
| Eight mitigation strategies, each with requirements | Principles, each supported by actions | A principle is the security outcome; actions are what you do to reach it. One old strategy can feed several principles. |
| Maturity Levels One to Three | Priority phases | Phases set the order in which to work through the technical domains. They are not a maturity or assurance rating. |
| Applied across the whole IT environment | Applied per domain | The same control can be fully effective in one domain and only partly effective in another. |
| Choose a target maturity level | Threat-informed throughout | There is no target level to pick; the framework already reflects current attacker tradecraft. |
| Assessed against specific requirements | Outcome-based assessment | Each action is rated not assessed, not effective, partially effective or fully effective, judged on coverage, consistency, currency and evidence quality. |
Two capability domains that run throughout, six technical domains in phases
Capability domain, from the start. Executive accountability, resourcing, risk management and supplier assurance, AI accountability and legacy system management.
Capability domain, from the start. Central event logging, detection, incident identification, detection efficacy, coordination, response and post-incident learning.
Boundary services, identity services, privileged environments, critical processes and services, business systems, and user devices. Actions are applied and rated in each domain they are mapped to.
Where each Essential Eight strategy lands
Every Essential Eight strategy maps to at least one Essentials principle, so the controls you built still count. The usual gap is scope, the broader outcome the principle asks for, or evidence that the control keeps working.
| Essential Eight strategy | Maps to these Essentials principles | Typical extra work |
|---|---|---|
| Application control | Trustworthy software · Secure configuration management | Control administrative tooling separately; tighter exception management; detect configuration drift. |
| Patch applications | Vulnerability management · Asset identification · Legacy system management | Treat by exploitation, exposure and criticality, not only by age; inventory identities, credentials and data as assets. |
| Patch operating systems | Vulnerability management · Asset identification · Legacy system management | Manage the risk of legacy systems that cannot be replaced yet, until they are retired. |
| Multi-factor authentication | Identity, credential and access management | Phishing-resistant MFA per domain, plus default accounts, secrets storage, scanning for exposed credentials and retiring legacy authentication. |
| Restrict administrative privileges | Identity, credential and access management · Least privilege access · Secure administration · Network segmentation and segregation | Time-bound privilege grants, recording of every administrative change, least privilege for service accounts, limits on lateral movement. |
| Restrict Microsoft Office macros | Trustworthy software · Secure configuration management | Treat macros as one execution path among many; fold settings into maintained configuration baselines. |
| User application hardening | Secure configuration management · Content filtering | Approved baselines beyond user devices; blocking outbound connections to malicious destinations across applications. |
| Regular backups | Regular and proven backups · Least privilege access | Immutable or isolated backup storage, repositories separated from production, restore tests that prove recovery objectives. |
What an ML2 or ML3 rating is still worth
The baseline for Commonwealth entities and many critical infrastructure operators. Much of it feeds the early priority phases: phishing-resistant MFA, patching internet-facing services, privileged access, application control and central logging. Expect work on domains you did not cover, governance, visibility and response, and evidence of sustained effectiveness.
A broader set of controls and evidence carries over, but it still does not equal "fully effective". Actions on credential exposure, supply chain security, per-domain implementation and the two capability domains have no Essential Eight equivalent.
Do not stop. Map completed work and evidence to Essentials actions, keep planned work that still applies, and use the priority phases to direct what is left.
Deployment evidence still counts, but ASD looks for proof that a control keeps working: validation results, monitoring records, drift reports, restore tests and detection engineering. Existing evidence does not need to be regenerated if it is current, reliable and shows coverage and consistency.
The evidence ASD now asks for is the evidence our tools produce
Proof that controls work, not just that they exist: validated findings, attack paths across identity and cloud, and detection testing measured against your SIEM. That is the operational evidence of effectiveness and detection efficacy the Essentials assessment model looks for.
Continuous outside-in asset discovery, vulnerabilities ranked by whether attackers are exploiting them, public code leaks naming you, and supplier scoring: inputs to asset identification, risk-based vulnerability management and supplier assurance.
The Essential Eight and the ISM are mapped in GRCorb today, so the controls and evidence you already hold sit in one register for the gap analysis ASD recommends.
Governance and culture is now assessed: executive accountability, resourcing, supplier assurance and AI accountability. A vCISO carries that mandate on your hours.
Threat Exposure Validation Validation · Threat Landscape Monitoring · GRCorb · vCISO · SAK in Australia
Questions Australian security teams are asking
Is the Essential Eight still required?
Where a regulator, contract or policy still asks for Essential Eight implementation or reporting, keep meeting it as directed by that authority. ASD's transitional arrangements continue into 2027. For new programmes, ASD says organisations can implement ASD Essentials for enterprise IT directly.
Does our ML2 rating convert into an Essentials rating?
No. ASD is explicit that Essential Eight maturity ratings do not automatically convert, because the two models assess different things. Use your existing implementation and assessment evidence as the starting point for a gap analysis.
Are priority phases the new maturity levels?
No. Priority phases set the order in which to implement the technical domains. They are not maturity, compliance or assurance ratings, and ASD lists treating them that way as a common transition mistake.
What is genuinely new?
Governance and culture is assessed for the first time, including executive accountability, supplier assurance, AI accountability and legacy systems. There are new principles for content filtering, awareness training and supply chain security, broader identity and credential requirements, and a dedicated visibility and response domain.
Do we need to collect all our evidence again?
No. Evidence that is current, reliable and shows appropriate coverage and consistency can be reused. What usually needs adding is evidence that controls keep working over time, such as validation, monitoring and restore testing.
Where should we start?
Establish a baseline from your Essential Eight work, scope the first priority phase, run a gap analysis per domain, and build the two capability domains from day one rather than leaving them until the end.
Sources
- ASD's ACSC, "Transitioning from the Essential Eight", 15 Oct 2026: cyber.gov.au
- ASD's ACSC, ASD Essentials for enterprise IT: cyber.gov.au
- ASD, "ASD Essentials: evolving our approach to cyber security resilience", 15 Oct 2026: asd.gov.au
- ASD's ACSC, Annual Cyber Threat Report 2025–26, "ASD's Essentials series": cyber.gov.au
This page summarises ASD's published guidance and is not legal advice. ASD Essentials for enterprise IT is the authoritative source for the requirements.