Keep going, and put every open item through two tests before you spend another dollar on it. The Australian Signals Directorate (ASD) replaced the Essential Eight on 15 October 2026, and published a guide for businesses caught part-way through. Its advice is not to start fresh work just to hit the old target. Finish what somebody still requires of you. Finish what still closes a real gap. Re-scope anything that fails both tests.
That matters because of where you probably are. The budget is part spent, the remediation list still has items open, and somebody above you wrote Essential 8 alignment into a requirement you did not choose. Then the news arrived that the framework had been replaced. Nobody has told you which half of it survived.
Two things take the heat out of this. ASD does not want approved work slowed or stopped. And it has set no deadline: asked about timing, its published answer, read on 20 October 2026, is that it will advise in due course. It also writes this guidance mainly for large organisations, critical infrastructure and government, and publishes separate material for smaller businesses.
So this is three decisions about work you have already bought, not a new project: which open items still earn their place, what finishing one now has to produce, and which mistakes quietly add cost.
TL;DR: What to do with the work in flight
- ✅ ASD says existing Essential Eight investment remains valuable.
- ✅ Finish an open item if somebody still requires it, or if it still closes a real gap. Do not start fresh work for the old target alone.
- ✅ Reuse current evidence. Deployment alone does not demonstrate effectiveness.
- ✅ The new framework's priority phases set the order of work. They are not maturity, compliance or assurance ratings.
- ✅ The guide targets large organisations, critical infrastructure and government. Smaller businesses may still use the Essentials guidance where relevant, ASD's questions and answers say.
Contents
- Test Every Open Item Before You Finish It
- What Finishing an Item Has to Produce Now
- The Transition Mistakes That Quietly Add Cost
- Questions about the work still on your remediation list
Test Every Open Item Before You Finish It
Before you decide anything, write down where you actually stand. ASD calls that the transition baseline, and it wants six things in it: your last assessment results, the controls you run today, the exception register, the risk register, the remediation plan, and the work already funded but not started. For a business this size that is mostly a filing exercise. It is also the step that makes every decision after it cheap.
Then comes the sentence worth printing out. ASD writes: "Do not initiate work solely to achieve a superseded Essential Eight target unless it remains required by a regulator or other obligation or continues to address material cyber security risk." Those two exceptions are where nearly all of this work sits. A client's security schedule is an obligation. A control that still reduces real exposure addresses material risk. Either one keeps the item on the list.
What the sentence kills is narrower than it first sounds. It kills work whose only justification was a number on a maturity scale. ASD then asks you to map existing and planned work to the Essentials before deciding whether it continues unchanged. That is the part a rushed provider will skip. None of this is permission to down tools either. ASD does not recommend slowing or stopping approved programs. And the framework ASD published in October arrived with a set of guides, not a notice to wind anything up.
- Write the baseline down before you spend anything else: last assessment results, current controls, both registers, the remediation plan, and the funded work still to come.
- Against each open item, name either the obligation that requires it or the exposure it reduces. One of the two, in writing.
- An item that only ever existed to lift a maturity number is the one to re-scope.
- Go back to whoever set your requirement and ask whether it still names Essential 8 alignment. Keep the reply with the baseline.
What Finishing an Item Has to Produce Now
You are probably sitting on more evidence than you think. Reuse it wherever it is still current and still describes your environment. ASD is explicit that you do not have to generate fresh evidence just because the old evidence was collected for another framework. Its list of what an assessed business usually already holds is a long one: assessment reports, configuration extracts, ruleset exports, control test results, logging architecture documentation, exception registers, risk registers and remediation plans.
Then ASD's line that changes what finished looks like. Evidence showing what has been deployed remains useful, but deployment alone does not demonstrate effectiveness. What ASD ranks higher is evidence of a control operating over time: validation results, monitoring records, configuration drift reports, review records, restoration tests. So the last stretch of a part-finished program is usually better spent proving the controls you already switched on than switching on one more.
In Microsoft 365, where most of these businesses already live, that costs something specific. Microsoft's Conditional Access insights and reporting workbook shows you the impact of your policies over time. It shows you nothing until sign-in logs are streaming to a Log Analytics workspace and the Microsoft Entra ID P1 licences are in place. Microsoft Entra access reviews recur on a set frequency, weekly through to annually. Microsoft's own documentation gives a reason to run them: they give auditors proof that policy exceptions are reviewed regularly. That matters here, because ASD asks for the same thing. Existing exceptions, compensating controls and accepted risks should be reviewed. So do not lean on an exception that has expired, a compensating control that has degraded, or a risk somebody accepted against an older threat picture. Look at each of those again first.
- Reuse what is current. Never re-run an assessment just to relabel its findings.
- For each control you have closed, find the record that shows it still operates: a test result, a monitoring report, a drift report, a dated review.
- Check log retention and licensing before you promise anybody evidence covering a period of time.
- Re-open the exception register. Anything expired, degraded or accepted years ago gets looked at again, with a date on the look.
The Transition Mistakes That Quietly Add Cost
ASD names seven transition pitfalls. Five of them bite a part-finished program hardest. The first is claiming equivalence instead of assessing. A control that previously satisfied an Essential Eight requirement provides evidence. It does not automatically produce a rating. The new framework groups a business's functions and assets into eight areas, which ASD calls domains: six technical and two capability. It also recommends the order to tackle them, which it calls priority phases. The second is treating priority phases as maturity levels. Phases sequence the domains, and ASD states plainly that they are not maturity, compliance or assurance ratings. Under the Essentials, organisations no longer select a target maturity level at all. That is a real change if the checklist you filled in yourself was built around picking one.
The third is deferring the capability domains. Governance and culture, and visibility and response, apply across all phases. They should not be held back until the technical domains are complete. The fourth is overlooking new requirements. Some actions have no direct Essential Eight equivalent, and they need their own planning and budget. The fifth is worth carrying into any board paper. Enterprise-wide implementation does not mean an action earns the same rating in every domain.
One honest note. This guide was not written for you. ASD files it under the Essentials for enterprise IT, tags it for large organisations, critical infrastructure and government, and the readers it names are security architects, program leads, chief information security officers and assessors. Separately, in its questions and answers on the Essentials series, ASD says smaller businesses that do not operate at the scale of enterprise IT can still use the Essentials guidance where relevant. So take the method and leave the obligation. Nobody is telling a Melbourne business of 30 to 300 users to adopt it.
The method is the useful part: baseline, reuse, review, then a gap analysis. That analysis classifies each action as already effectively addressed, partially addressed or not addressed. ASD is careful to call those gap analysis findings, not formal assessment ratings. It is the same distinction a provider should already be making at a review. The ASD wording quoted throughout comes from its transitioning publication and its frequently asked questions, both published and last reviewed 15 October 2026. The transitioning publication was read on 16 November 2026, the frequently asked questions on 20 October 2026.
- Treat an old control as evidence towards a rating, never as the rating itself.
- Do not convert a phase number into a grade in a board pack. ASD says it is not one.
- Put the governance and the visibility work into the plan now. They should not wait for the technical items.
- Budget for the actions with no Essential 8 ancestor, because they will not appear anywhere in your old scope.
Questions about the work still on your remediation list
We are part-way through an Essential 8 program. Do we stop, pause or carry on?
Carry on, with ASD's own rule applied item by item. Its transition guide says not to start fresh work just to reach the old target. Two exceptions keep an item on your list: a regulator or another obligation still requires it, or it still addresses material cyber security risk. Most open remediation items clear one of those two without difficulty. A client requirement is an obligation, and an open gap is exposure. ASD also says it does not recommend slowing or stopping approved uplift. So pausing a funded program while you wait for a date is the one option its guidance does not support. Asked about timing, ASD's answer, read on 20 October 2026, is that it will advise on expectations in due course.
Can the provider we already use work out which items still earn their place?
They should be able to, and the method tells you whether they worked from ASD's transitioning publication or somebody's summary of it. The work runs item by item. Set each open item against the two exceptions ASD names, then write beside it which one it meets, and date the line. Ask to see the ASD wording they relied on, in the publication itself. This goes faster where one team runs the IT, the compliance work and the evidence, because the controls and the records then sit inside the same engagement instead of two contracts pointing at each other. That is the model inSUPPORT runs.
We have budget left on this program. Where should the rest of it go?
Into proving the controls you have already switched on. Do that before switching on more. ASD's evidence test is the reason. Evidence showing what has been deployed remains useful, it says, but deployment alone does not demonstrate effectiveness, and evidence of a control operating over time supports a rating more strongly. So the remaining spend buys validation results, monitoring records, drift reports and a restoration test against the items already closed. Check log retention and licensing before you commit to evidence covering a period of time, because that is where this quietly stops being free. Whatever is left in the Essential 8 alignment budget goes to the open items that cleared ASD's two exceptions.
What does the written baseline actually have to contain?
ASD names the contents. You do not have to invent them. The most recent assessment results, the existing controls, the exception register, the risk register, the remediation plans, and the uplift work already committed or planned. Put those in one place with a date on each. Then take the open items one at a time and write the obligation or the exposure beside each. Where you can write neither, you have found the item to re-scope. Most of this is already sitting in folders, which is why ASD puts it first and why it costs so little to do. If the folders turn out to be thin, that is itself the finding, and a scoped audit of the environment produces the document. That is also where The 6 Step Cyber Strength System opens, for the same reason: nothing after it is worth much until that document exists.
A Cyber Strength Audit works through the environment you actually run, against the compliance frameworks your industry answers to. That includes the relevant Essential 8 controls. It records where each one stands, says what evidence sits behind it, and returns a plain English gap list with the cost of closing each item. inSUPPORT has produced that document more than 1,500 times, so it arrives as a standard piece of work rather than a research project. You finish holding the dated baseline ASD asks for as its first step. If you go on to managed support, the remediation it finds sits inside the support fee instead of arriving as a separate project quote a month later.
Book a Cyber Strength Audit →Sources
- "Transitioning from the Essential Eight", ASD's own transition guidance, published and last reviewed 15 October 2026. The source for the statement that existing investment remains valuable, that the Essentials in many cases applies existing controls more broadly, that Essential Eight maturity level ratings do not automatically convert, the four-tier rating scale, the transition baseline step, the instruction not to initiate work solely to achieve a superseded target, the evidence-reuse test and the statement that deployment alone does not demonstrate effectiveness, the review of existing exceptions and accepted risks, the gap analysis classifications, the seven transition pitfalls, and the audience the page tags itself for, large organisations and critical infrastructure, and government. Quoted from a verbatim capture of the page taken 16 November 2026. cyber.gov.au
- "Frequently asked questions", ASD's questions and answers on the Essentials series, published and last reviewed 15 October 2026. The source for the primary audience of the series and the separate guidance for small businesses, the absence of any published transition timeline, and the statement that ASD does not recommend slowing or stopping the roll-out of pre-approved cyber security initiatives. Quoted from a verbatim capture of the page taken 20 October 2026. cyber.gov.au
- "Conditional Access insights and reporting workbook", Microsoft's documentation for the workbook that shows the impact of Conditional Access policies over time, and the source for its prerequisites: sign-in logs retained in a Log Analytics workspace, Microsoft Entra ID P1 licences, and the reader roles required to open it. Page dated 24 March 2026, read 16 November 2026. learn.microsoft.com
- "What are access reviews?", Microsoft's documentation for Microsoft Entra access reviews, confirming that reviews can recur at set frequencies from weekly to annually, and that one stated use is to avoid oversight of policy exceptions and give auditors proof that those exceptions are reviewed regularly. Page dated 12 March 2026, read 16 November 2026. learn.microsoft.com
Related Reading
- Cyber Strength Audit
- ASD Replaced the Essential Eight. What That Actually Means
- What an Essential 8 Assessment Actually Involves
- What Your Provider Should Show You at an Essential 8 Review
- What Actually Happens in a Cyber Strength Audit
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.
inSUPPORT provides managed IT and cyber security services. It is not an insurer, insurance broker or underwriter and does not hold an Australian Financial Services Licence. Where cyber insurance forms part of a plan, it is arranged through licensed insurance partners and underwritten by the insurer. Cover is subject to the insurer's assessment, the policy terms and the Product Disclosure Statement and Target Market Determination. This article is general information about IT and security practice, not financial product advice, and it does not take account of your objectives, financial situation or needs.
CLICK HERE


