What ASD published
ASD Essentials is a series, not a single document. ASD released it on 15 October 2026 after a public consultation that ran from 15 June to 12 July 2026. It has three parts:
- Chapters for specific environments. Essentials for enterprise IT, Essentials for cloud (for organisations whose technology runs entirely on SaaS and PaaS) and Essentials for operational technology. ASD says more chapters can be added.
- Overview publications. What is the Essentials, the case for change, a reading guide, guidance on which chapter to start with, a paper for senior executives, AI considerations and an FAQ.
- Supplementary guidance. An implementation planning guide, an assessment process guide, an assessment evidence guide and asset scoping guidance for enterprise IT, and a guide to transitioning from the Essential Eight.
The enterprise IT chapter is the one that takes over from the Essential Eight. ASD calls it an evolution: every Essential Eight strategy maps to at least one Essentials principle, and in its FAQ ASD also describes the change as replacing the Essential Eight. Both statements are accurate. The Essential Eight is not withdrawn yet, though. ASD says it will maintain both frameworks on cyber.gov.au during the transition period, and that organisations should continue to meet their current regulatory obligations until regulators communicate changes.
How ASD Essentials is structured
Every chapter uses three layers:
- Principles describe the security outcome to achieve, such as trustworthy software or identity, credential and access management. ASD draws them from the cyber security principles in its Information security manual (ISM).
- Actions describe what you must do to achieve each principle. Where it fits, ASD maps actions to MITRE ATT&CK techniques.
- Domains group the business functions and assets that share similar risk, and say where each action applies.
The enterprise IT chapter has six technical domains, set in three priority phases, and two capability domains that run through all three.
| Priority phase | Domains | Why this order |
|---|---|---|
| Phase 1 | Boundary services, Identity services | Internet-facing services, edge devices and identity systems are the common routes to initial access |
| Phase 2 | Critical processes and services, Privileged environments | Limits privilege escalation and the impact of a successful intrusion |
| Phase 3 | Business systems, User devices | The largest, most widely distributed part of the environment, easier to secure once earlier phases are in place |
| All phases | Governance and culture, Visibility and response | Accountability, risk management, detection and response, started early and expanded as you go |
Assessment changes too. Each action is rated not assessed, not effective, partially effective or fully effective for each domain it applies to. A principle takes the lowest rating of its actions in that domain, and a domain counts as addressed only when every applicable action is fully effective. Assessors judge coverage, consistency, currency and evidence quality, guided by indicators of good practice in ASD’s assessment evidence guide.
What changes from the Essential Eight
| Essential Eight | ASD Essentials (enterprise IT) |
|---|---|
| Eight mitigation strategies with set requirements | Principles, each supported by actions |
| Maturity Levels Zero to Three | Priority phases, which set the order of work and are not a rating |
| You pick a target maturity level | No target level; all applicable principles and domains are the goal, sequenced by phase |
| Applied across the whole IT environment | Applied and assessed domain by domain |
| Rated against specific requirements | Four-tier rating of whether each action achieves its outcome |
| Little on governance | Governance and culture domain: executive accountability, resourcing, risk management, supplier assurance, AI accountability, legacy systems |
The new ground is substantial. ASD’s transition guide lists principles with no direct Essential Eight equivalent, including content filtering, cyber security awareness training and cyber supply chain security. Asset identification now covers infrastructure, operating systems, applications, identities, credentials and data as distinct assets. Logging, detection and incident response, previously scattered across strategies, become a domain of their own. MFA becomes one part of a broader identity principle that also covers default and unused accounts, secrets stored in code and file shares, and legacy authentication protocols.
Your maturity level doesn’t convert
ASD is clear that Essential Eight maturity ratings do not translate into Essentials ratings, because the two models measure different things. Your existing controls and evidence carry forward, and ASD wants you to use them as the starting point for a gap analysis. An organisation at Maturity Level Two can expect many controls to contribute to actions in the early phases, such as phishing-resistant MFA, patching internet-facing services, privileged access, application control and central logging. Expect more work on governance, on visibility and response, on assets and domains the Essential Eight never reached, and on evidence that shows a control keeps working over time, not just that it was deployed.
What hasn’t changed yet
Today’s obligations still name the Essential Eight, and ASD tells you to keep meeting them:
- PSPF. PSPF Release 2026, published by Home Affairs on 1 July 2026, still requires every Commonwealth entity it covers to implement all eight strategies to Maturity Level Two under the Essential Eight Maturity Model. Home Affairs has not announced a change.
- DISP. Defence requires all DISP members to achieve and maintain the full Essential Eight at Maturity Level 2, assessed through the Cyber Security Questionnaire. Defence has not announced a move to Essentials. Our guide to DISP and ISO 27001 covers the detail.
- Tenders, state policy and questionnaires. Contract clauses, state cyber policies, customer security questionnaires and cyber insurance forms ask for an Essential Eight maturity level, and they will keep doing so until their owners rewrite them.
On timing, ASD says it is talking to regulators about the impact and expected timeframes and will advise on transition expectations in due course. No date has been announced. An ACSC official told iTnews in June 2026 that the Essential Eight would probably start to be phased out in about a year and retired in about two, but that is an estimate, not a deadline. Until a regulator sets one, your current obligations stand.
What to do now
ASD’s advice is not to stop. It does not recommend slowing or halting approved uplift programs; carry on while you assess alignment with the new framework. Its transition guide sets out a sequence that works for most organisations:
- Record your baseline. Your latest Essential Eight assessment, current controls, exception and risk registers, and the uplift work already planned.
- Scope the phase 1 domains. Identify the assets and functions in Boundary services, Identity services, Governance and culture, and Visibility and response. Reuse your asset inventory and architecture documents.
- Run a gap analysis. For each action, record whether existing controls already address it, partly address it or don’t. These are planning findings, not formal ratings.
- Plan, deliver and progress. Close the gaps, then move through phases 2 and 3 while growing the two capability domains.
ASD also says not to start work purely to reach a superseded Essential Eight target unless a regulator or other obligation still requires it, or it still addresses material risk. If a contract needs Maturity Level Two, that work is still required. Mapping each planned item to Essentials before you start lets the same work serve both.
Mapping Essential Eight evidence to Essentials actions, domain by domain, is detailed work, and it is the part we take on for clients. What it looks like depends on who you are.
Small and medium businesses
ASD wrote Essentials primarily for Commonwealth entities, critical infrastructure and large organisations, and says smaller businesses can still use it where relevant. If a customer, tender or insurer asks for an Essential Eight maturity level, that is still the answer they want. Use the Essentials phase 1 domains to guide your next round of improvement: identity and internet-facing systems first, with clear executive ownership. If you run entirely on SaaS and PaaS, read the cloud chapter, which deals directly with what sits with you and what sits with the provider.
Government suppliers
Agencies are still measured against Essential Eight Maturity Level Two, so their contracts and questionnaires will keep asking for it. Keep your maturity assessment current, and expect agencies to start asking about Essentials once Home Affairs updates the PSPF. Our guide to ISO 27001 for government suppliers explains how security terms reach you through contracts.
DISP members
Nothing changes until Defence says so. Keep meeting the full Essential Eight at Maturity Level 2 and keep your Annual Security Report and CSQ answers accurate. Doing an Essentials gap analysis alongside that costs little and puts you ahead when Defence moves.
Managed service providers
Your clients will ask both questions: are you at an Essential Eight maturity level, and how will you support their move to Essentials? ASD is explicit that outsourcing does not transfer accountability. Clients must get current evidence that you are delivering the security outcomes you are responsible for, and a domain is not effective just because a provider owns it. Expect responsibility matrices to be rewritten by domain. ASD also notes its assessment process guide is meant for assessing your own environment, not for assessing suppliers. See ISO 27001 for MSPs.
Where ISO 27001 fits
The move to Essentials narrows the gap between ASD’s guidance and ISO 27001. The Essential Eight barely touched governance, and the Governance and culture domain is now assessed in every phase: executive accountability, risk appetite, resourcing, security risk management, supplier assurance and the management of exceptions and accepted risks. That is what an ISMS does. Scoping by business function, a risk assessment, an asset inventory, an exception register with owners and expiry dates, a review cadence and independent internal audit all carry straight across.
Be precise about what that means. ASD’s assessment evidence guide maps actions to controls in the ISM, the Essential Eight, NIST CSF 2.0, NIST SP 800-171r3 and the AESCSF. ISO 27001 is not on that list. ASD says evidence from other frameworks can be reused where it shows an action is effective, so your ISMS records count as evidence, but an ISO 27001 certificate is not an Essentials rating, just as it was never an Essential Eight maturity level. Our comparison of Essential Eight vs ISO 27001 explains why, and the ISO 27001 gap analysis guide shows how a structured gap analysis is run.
Next step
Keep building to the Essential Eight where PSPF, DISP, a tender or a customer requires it, and plan your move to Essentials alongside it. We assess your current maturity, map it to the Essentials principles and domains, and build one plan that meets today’s obligations and gets you ready for Essentials. See our Essential Eight assessments and ISO 27001 service, or book a free 30-minute consultation and tell us who is asking you for what.
