Told to Get Essential 8 Aligned. What Actually Changes Now

Clay illustration: an operations manager handed an instruction they did not ask for, puzzled, while a colleague calmly shows that the job in front of them is the same job it was yesterday.

Almost nothing changes about the control work, and Essential 8 is still the right name for the job you were handed. The Australian Signals Directorate (ASD) published the ASD Essentials on 15 October 2026 and describes it as replacing the Essential Eight. Its transition guidance says the money already spent on the Essential Eight remains valuable. It also says the new framework in many cases applies the controls you already run more broadly. Both sets of guidance sat on cyber.gov.au when ASD's pages were read on 20 October 2026, and the transition guidance was still there on 16 November 2026. ASD has published no transition deadline.

A board paper or a client's security schedule landed on your desk naming Essential 8. Then somebody forwarded you the news. So you hold two documents that appear to disagree, and nobody internally whose job this is. It is an uncomfortable place to be asked for a plan.

The mismatch is a vocabulary problem before it is a technical one. The controls, the evidence and the environment are the same on both sides of the name change. What does not travel across is the grade. Knowing which is which keeps you from buying a freshly labelled project you do not need.

So what follows is the translation. What the old name still means, what carries over from work already paid for, and how to turn a directive into a scoped piece of work with a name against it.

TL;DR: What to tell whoever sent the email

  • ✅ Essential 8 has not been withdrawn. ASD still publishes it under Existing Essential Eight.
  • ✅ ASD writes the Essentials primarily for Commonwealth entities, critical infrastructure and large organisations, and points smaller businesses elsewhere.
  • ✅ Any date you are working to came from whoever set it. ASD has published none.
  • ✅ Control work carries over where evidence is still current. A maturity rating never becomes an effectiveness rating.
  • ✅ Your environment and your licensing decide the work, not the name on the directive.

Contents

Essential 8 Is Still the Right Name in That Email

Start with the word, because the word is what is making this feel urgent. ASD's own frequently asked questions, published and last reviewed 15 October 2026, ask why it is replacing the Essential Eight, so replacing is ASD's word and not a vendor's. The Essential Eight has not been withdrawn. On the Essentials hub it sits under its own heading, Existing Essential Eight. That is not how a framework gets retired.

Then read who the new guidance is written for, because that is the part the market will skip this quarter. ASD says the series is written primarily for Commonwealth entities, critical infrastructure owners and operators, and large organisations. Smaller businesses that do not operate at the scale of enterprise IT can still use the guidance where relevant. ASD publishes tailored guidance for small businesses separately. So nobody can tell a business of 30 to 300 users that it must now adopt the Essentials. If somebody does, ask to see the sentence.

Which leaves the question that actually decides anything. Whoever wrote your directive owns its words, and a framework page does not amend a client's security schedule or a board resolution. The detail sits in what ASD actually published on 15 October. The point for you is narrower than that. If the requirement says Essential 8, your deliverable says Essential 8, and the record underneath it says what was checked and when. That is not a loophole. It is how an obligation has always worked.

  • What ASD published. A framework of Principles, Actions and Domains, in chapters for enterprise IT, operational technology and cloud.
  • What ASD did not publish. A date. Its answer on timing is that it will advise on expectations for transitioning in due course.
  • What to put in writing. The framework the requirement names, the systems it covers, and who set it. One email, kept.

What Carries Over Is the Control Work, Not the Grade

ASD is unusually blunt about this. Efforts already completed under the Essential Eight remain relevant, it says, and will directly support alignment with the Essentials series. Every Essential Eight mitigation strategy maps to at least one principle. In most cases, ASD says, a control implemented under the Essential Eight will directly satisfy a corresponding action or substantially contribute to one. So the work already done keeps counting.

The grade is the exception, and it is worth getting right before it reaches a board pack. The two frameworks ask different questions. The maturity model asked whether you had put specific controls in. The new one asks whether each control actually works for the systems it is meant to cover, and the answer gets one of four ratings: not assessed, not effective, partially effective, fully effective. ASD says maturity level ratings do not automatically convert into effectiveness outcomes. So a Maturity Level Two result is not a partially effective result, and anybody who turns one into the other has invented a number. Those four words only come out of somebody looking at your environment, which is what an Essential 8 assessment involves.

If nobody has looked at your environment yet, most of your actions start in a tier worth knowing by name. ASD calls it not assessed, calls that a neutral rating, and says it must remain distinct from not effective. If a report grades those actions as failures, that tells you about the method rather than about your environment.

Whichever name is on the directive, the settings on your systems are the same ones, and the instructions for them come from the vendor, not from ASD. Microsoft's own instruction for requiring multifactor authentication from everybody is a Conditional Access policy, which is a rule that decides who has to pass which checks before they are let in. It targets all users and all resources. Emergency access and service accounts are excluded. The rule runs first in report-only mode, where it records what it would have done without blocking anybody, and is switched on after that. Office blocks macros in files from the internet by default. The policy that enforces that block is available for Microsoft 365 Apps for enterprise, and not for Microsoft 365 Apps for business. That licensing line decides what you can enforce. The name on the directive does not.

So the work gets scoped from your environment, not from the email. inSUPPORT's own sequencing puts reducing the attack surface before patching what remains. That is its operating order for its own remediation work. Yours may land differently once somebody has actually looked at what you run.

  • Carries over. The controls themselves, the configuration records, the test results, the asset and access registers, where they still describe the environment as it runs today. ASD's own caution is that deployment alone does not demonstrate effectiveness.
  • Does not carry over. The maturity level rating, and any sentence built on top of it.
  • Decides the work. Your environment, your platforms, and what your licences let you enforce today.

Turning the Directive Into a Piece of Work With a Name On It

With nobody in-house, what you are buying is a document and an owner. The document has to answer the question you were asked, in the words it was asked in, while recording the controls and the evidence underneath so it reads to either vocabulary. That is one job and not two. It is also the same job a properly run assessment has always produced.

ASD's own first step for anybody preparing is to write down where you stand today: what your last Essential Eight assessment found, the controls you actually run, what your risk assessments turned up, and which business functions you cannot trade without. ASD calls that a transition baseline. The step after it is working out which of your systems and functions belong to the four areas ASD puts in its first phase. It names them as boundary services, identity services, governance and culture, and visibility and response. Read that list again and notice what it actually is. An inventory and a set of records. Nothing in it obliges you to adopt anything. What you commission has to carry four things.

  • The framework and the level named exactly as your directive names them, so the pack answers the question you were actually asked.
  • A dated record of each control as it stands, written against the control rather than against a grade.
  • What your platforms and licences let you enforce today, and what they do not.
  • A named owner and a review date against every gap, with the evidence behind each conclusion attached.

What to Ask Whoever Runs It

This is the part people get wrong, and it is simpler than it sounds. Ask for the source page, not a slide about it. Ask for the evidence each conclusion rests on. Ask who owns the next action on every gap and when it is next looked at. A provider already handling your alignment should produce all three without a new engagement. What a provider should show you at a review is the longer version of that list. If you are shortlisting Essential 8 compliance help in Melbourne, those three asks sort the field faster than any capability statement.

This article describes ASD guidance published 15 October 2026, read from verbatim captures of ASD's frequently asked questions taken on 20 October 2026 and of its transitioning guidance taken on 16 November 2026. Check cyber.gov.au yourself before you accept a date from anyone.

Questions When the Framework Moved and the Directive Did Not

Do we have to adopt the ASD Essentials?

Not on ASD's own description of who the series is for. ASD says the Essentials is written primarily for Commonwealth entities, critical infrastructure owners and operators, and large organisations. Smaller businesses which do not operate at the scale of enterprise IT can still use the guidance where relevant. It publishes separate guidance for small businesses. There is also no deadline to adopt it, because ASD's published answer on timing is that it will advise on expectations for transitioning in due course. If a requirement on you names Essential 8 compliance, that is still the requirement until whoever set it says otherwise.

We have nobody in-house. What do we actually need a provider to do?

Three things, in this order. Read the source guidance, not a summary of it, and show you where each answer came from. Assess the environment control by control, writing down what was tested, when, and on what evidence. Then scope the remaining work with a named owner and a date against each gap. That is a defined piece of work rather than an open retainer, and for a business of roughly 30 to 300 users that is what a Cyber Strength Audit produces. If your current provider already handles your Essential 8 compliance work, ask for those three things before you buy anything new.

How long does this take, and what is the deadline?

There is no ASD deadline to work to, so the only date that matters is the one in your directive. The assessment itself is a scoping and evidence exercise, and it moves at the speed of your records. An environment with current documentation goes quickly. One where nobody has written anything down does not. On the remediation, the honest answer is that it depends which controls are short. Settings change quickly. Anything needing new software, a replaced operating system or a licence change is a procurement decision instead. Ask for a timeframe per gap, not one number for the lot.

Somebody has quoted us for an ASD Essentials readiness project. Do we start there?

Start with the two documents this whole problem turns on, because neither of them needs a project. Go back to whoever sent the directive and get the requirement in writing, including the framework it names and the systems it covers. Keep the reply. Then get a dated picture of where your controls actually sit, written against the controls rather than against a grade. With those two in hand you can read any quote for the work it covers instead of the framework it is named after. ASD itself tells organisations not to start work purely to hit a superseded Essential Eight target unless a regulator or another obligation still requires it, or it still addresses material cyber security risk. That is worth reading in both directions. Booking a scoped look at the environment is how you get the second document without guessing at it.

See Where You Stand Against the Words in That Email

A Cyber Strength Audit works through the environment you actually run, against the compliance frameworks that apply to your industry including the relevant Essential 8 controls. The gaps come back in plain English, with what it takes to close each one and what that costs. You finish holding a documented audit trail you can hand to a board or a client who asks, and the baseline either vocabulary starts from. If you go on to managed support, the remediation it finds is inside the support fee rather than a project quote arriving a month later.

Book a Cyber Strength Audit →

Sources

  • "Frequently asked questions", ASD's questions and answers on the Essentials series, published and last reviewed 15 October 2026. The source for ASD's replacing language, who the series is written for, the absence of a transition timeline, the continuity of completed Essential Eight work, the mapping to principles, the four effectiveness ratings, the transition baseline and the statement that maturity levels do not automatically convert. Read from a verbatim capture of the page taken 20 October 2026. cyber.gov.au
  • "Transitioning from the Essential Eight", ASD's own transition guidance, published and last reviewed 15 October 2026. It states that investment already made in the Essential Eight remains valuable, and that the new framework in many cases applies existing controls more broadly. It advises against starting work solely to achieve a superseded Essential Eight target. It is also the source for the four-tier rating scale, and for not assessed being a neutral rating that must remain distinct from not effective. On reusing earlier evidence, it holds that evidence counts where it remains current and relevant, and that deployment alone does not demonstrate effectiveness. Read from a verbatim capture of the page taken 16 November 2026. cyber.gov.au
  • "ASD Essentials", The framework's own hub page, carrying the Principles, Actions and Domains model, the chapters for enterprise IT, operational technology and cloud, and the Essential Eight under the heading Existing Essential Eight. Read 20 October 2026. cyber.gov.au
  • "Require MFA for all users with Conditional Access", Microsoft's own instruction for enforcing multifactor authentication across a tenant, including the recommended baseline targeting all users and all resources, the exclusion of emergency access and service accounts, and running the policy in report-only mode first. Page dated 24 March 2026, read 16 November 2026. learn.microsoft.com
  • "Macros from the internet are blocked by default in Office", Microsoft's documentation of the default macro block and of the policy that enforces it, which states that the policy can be used only with Microsoft 365 Apps for enterprise and is not available for Microsoft 365 Apps for business. Page dated 17 July 2026, read 16 November 2026. learn.microsoft.com
Kane Nawrocki, Founder and CEO of inSUPPORT

About the author: Kane Nawrocki is the founder and CEO of inSUPPORT. He has spent more than 25 years in IT and built inSUPPORT to give Australian businesses managed IT, security and compliance as one model, with the remediation an audit finds included in the support fee rather than billed back as a surprise project.

Content reviewed by Probably Genius for accuracy and relevance.

Want to discuss this topic more?
CLICK HERE