Yes. The Australian Signals Directorate, ASD, replaced the Essential Eight on 15 October 2026 with a framework it calls the ASD Essentials, without withdrawing the older one, and its own published answers say the completed work still counts. Efforts already finished under the Essential Eight remain relevant, ASD says, and will directly support alignment with the new series. Every one of the eight mitigation strategies maps to at least one principle in it. For a business of 30 to 300 users, the work you paid for is still the work.
That lands differently when you are halfway through. You have a signed scope, a part-spent budget, a date somebody else chose, and a remediation list with items still open. The forward in your inbox announced a new framework, and did not say which half of your project survived it.
Some of it does not carry across. Be precise about which part. Your maturity level rating does not transfer, because ASD says the two frameworks measure different things. The documents naming the old framework need a rewrite. No transition deadline has been published, and ASD writes the Essentials primarily for Commonwealth entities, critical infrastructure and large organisations.
So this quarter's job is not a decision about frameworks. It is sorting what you already bought into three piles: the controls, the rating and the paperwork. One travels almost intact. One does not travel at all, and one needs an afternoon with a word processor rather than another engagement.
TL;DR: What still counts
- ✅ ASD says efforts already completed under Essential Eight remain relevant, and will directly support alignment with the Essentials series.
- ✅ Every Essential Eight mitigation strategy maps to at least one principle, so the controls travel.
- ✅ Maturity level ratings do not carry across, because ASD says the two measure different things.
- ✅ No transition deadline has been published, and ASD does not recommend slowing current uplift.
- ✅ The Essentials is written primarily for Commonwealth entities, critical infrastructure and large organisations.
Contents
- Sort What You Bought Into Three Piles
- Finish the Work Already on the List
- The Record Is What Survives a Rename
- Questions from businesses halfway through a program
Sort What You Bought Into Three Piles
Start with the controls. That is where the money went. A control you have already turned on usually does the job the new document asks for, or most of it, and ASD says so plainly: it will in most cases directly satisfy a corresponding action under a principle, or substantially contribute to one. The control itself has not changed. A second factor on an administrator account does the same job whichever document asks for it. Microsoft's documentation describes multifactor authentication as requiring two or more of something you know, something you have and something you are. None of that moved on 15 October. ASD draws one limit under that, though. A control you already have in place is evidence, not a result. Having it switched on does not by itself show that it works, and it does not hand you a rating.
The rating is the pile that does not move. The old model counted whether you had put specific controls in place. The new one asks whether what you do actually works, for the assets it covers. ASD says that itself, and says maturity level ratings do not automatically convert into effectiveness outcomes. So do not read a Maturity Level Two result as partially effective. If your board pack leads with a maturity level, the number is not wrong. It is answering a question the current baseline does not ask.
The paperwork is the third pile, and the cheapest. Reports, client attestations and board minutes naming the old framework still describe real findings about a real environment. What they need is the framework version and a date on the face of them. They do not need a fresh assessment underneath them.
- List the controls that are settings in a platform you already licence, and note which are enforced today rather than configured once.
- Separate the maturity rating from the findings underneath it, and keep the findings.
- Mark every framework document with its date and its scope.
- ASD says current, reliable evidence showing coverage and consistency need not be regenerated simply because it was collected for another framework.
Finish the Work Already on the List
Nobody has told you to stop. ASD's advice is the opposite: it does not recommend slowing or stopping the roll-out of pre-approved cyber security initiatives, and says organisations should continue their current uplift programs while assessing alignment with the new framework. That is a direct answer to the pause question, and the answer a part-funded project needs. For the big multi-year programs, ASD says it has published transition, implementation and assessment guidance to help organisations move. The items on your remediation list were gaps because of what they expose. Not because of the name on the cover sheet.
There is no date to work back from either. ASD's published position on timing is one sentence long: it has been communicating with regulatory bodies about the impact and expected timeframes of transitioning, and will advise on expectations in due course. Treat any transition deadline you are quoted as an estimate. What ASD put out on 15 October is a framework and a set of guides. It is not a clock.
The Essential Eight has not been withdrawn either. Both frameworks stand through the transition, so the older one is still the live requirement wherever somebody has named it. Where a contract, a client or a regulator asks for Essential 8 alignment, that ask stands until the party who set it says otherwise.
Then there is whether the new series is addressed to you at all. Mostly it is not. ASD says smaller businesses outside the scale of enterprise IT can still use the guidance where relevant, and it publishes tailored cyber security guidance for small businesses separately. A 40 person firm in Melbourne is not being told to adopt a new framework this quarter. It is being left to finish the controls it already knows are open.
- Keep the funded remediation moving. Date each item as it closes.
- Ask whoever quoted you a deadline to show you where ASD published it.
- If the Essentials lands in scope later, you will already hold ASD's first step.
- Do not re-scope a funded project around a framework nobody has required.
The Record Is What Survives a Rename
What outlasts a framework change is the evidence record. Not the score, and not the slide. It says what was assessed, which systems and user groups were in scope, who looked, on what date, and what was tested rather than merely sighted. ASD's own first step asks for the same thing: write down where you stand before you look at anything new. Start with the controls you run today, what your last risk assessment turned up, the Essential Eight work you have already banked, and the handful of business functions you cannot trade without. ASD calls that a transition baseline, and you write it before you list which of your systems the new framework's first stage would cover.
Read what the obligation on your desk actually says. Take Prudential Standard CPS 234, the information security standard set by the Australian Prudential Regulation Authority, or APRA. It asks an APRA-regulated entity to keep a security capability that matches the size and extent of the threats to its information assets, and to test whether those controls work, under a systematic testing program. Across its eight pages it names no external framework at all. One more line is worth knowing: where somebody else manages your information assets and you rely on their control testing, you must assess whether the kind of testing they do, and how often they do it, is enough for what those assets are worth and how fast the threats change. Deficiencies that cannot be remediated in a timely manner have to be escalated and reported to the Board or senior management.
Read that twice if a provider runs your controls. Whether a control was tested, by whom, and how recently is what a client, an assessor or a board comes back to. None of it changes when the cover page does. If you are not APRA regulated, the same demand usually sits in a client's security schedule or a contract clause, and it is worth reading for the same reason. The review a provider should be able to show you is the same artefact. The ASD wording quoted in this article comes from two pages, both published and last reviewed 15 October 2026, read on 20 October and 16 November 2026. Read them yourself before you rely on a date.
- Put the scope, the date and the assessor on every report you hand over.
- Ask which controls were tested and which were only sighted. Get it in writing.
- Keep the restore test dates and the exception register current.
- If you are APRA regulated, read CPS 234 before your next provider review.
Questions from businesses halfway through a program
Do we have to start our Essential 8 program again?
No. ASD says efforts already completed under Essential Eight remain relevant and will directly support alignment with the Essentials series, and that every mitigation strategy maps to at least one principle. What changes is how the result gets expressed, not whether the work happened. Keep the configurations, and keep the evidence behind them. Expect the rating language in your reporting to be rewritten rather than earned again, because ASD says maturity levels do not convert into effectiveness outcomes. If somebody proposes a restart, ask which control they think stopped counting. Put the same question to inSUPPORT: it prices the remediation an audit finds inside its monthly support fee, so a longer list of gaps does not earn it a second project.
Our contract and our board minutes still say Essential 8. How do we evidence the same work under the current ASD baseline?
Leave the name where a counterparty set it, because that requirement is still theirs to change. What you update is the evidence underneath it. ASD's transition guidance says assessment reports, configuration extracts, control test results, exception registers and remediation plans should be reused where they remain current and relevant. It also separates the useful from the valuable: evidence showing what was deployed is useful, but evidence showing how a control operates over time supports a rating more strongly. Its examples are validation results, monitoring records, configuration drift reports and restoration tests. Name the source document and the date beside each claim, the way you would with any other evidence.
How long does a re-baseline take, and what do we get at the end of it?
It depends on the state of your records, not the size of your network. Where the earlier assessment is documented with its scope and dates, the mapping is a reading exercise. Where it is not, somebody has to re-establish what is actually configured first, because otherwise the mapping is worth nothing. What you should end up holding is three things: a dated gap list, a written scope, and a note of which controls were tested rather than sighted. ASD describes that document as a transition baseline, and it is useful whether or not the Essentials ever lands on you.
What is the first thing to do this week?
Pull the last assessment you paid for. Check three things on it: the date, the scope, and whether each finding was tested or sighted. Then keep the funded remediation moving, since ASD does not recommend slowing uplift already approved. If those three are missing, the gap is in your record rather than your controls, and that is the cheaper of the two gaps to close. Write down what you find, with the date on it. You have started the baseline ASD asks for.
A Cyber Strength Audit assesses the environment you actually run against the compliance frameworks your industry answers to. It documents the gaps in plain English and prices the path to closing them. Where controls are already in place it says so, and says what evidence sits behind each one. Remediation of what it finds is included in the inSUPPORT support fee, not quoted back later as a separate project. You keep a dated record of where you stand. That is the first document any framework asks you for.
Book a Cyber Strength Audit →Sources
- "Frequently asked questions", The 23 answers ASD published alongside the Essentials, page published and last reviewed 15 October 2026. The source for the continuity position on completed Essential Eight work, the mapping of every mitigation strategy to at least one principle, the absence of a transition timeline, the primary audience for the series, the statement that maturity ratings do not convert into effectiveness outcomes, and the transition baseline steps. Answers read verbatim 20 October 2026. cyber.gov.au
- "Transitioning from the Essential Eight", ASD's own transition publication, published and last reviewed 15 October 2026. The source for the limit on what a transferred control buys you (a control that previously satisfied an Essential Eight requirement provides evidence, it does not automatically produce a rating, and deployment alone does not demonstrate effectiveness), and for the evidence reuse test: existing assessment reports, configuration extracts, control test results, exception registers and remediation plans should be reused where they remain current and relevant. ASD places it under ASD Essentials for enterprise IT and names its readers as security architects, program leads, chief information security officers and assessors. Read 16 November 2026. cyber.gov.au
- "Prudential Standard CPS 234 Information Security", APRA's information security standard, July 2019. Confirms that an APRA-regulated entity must maintain an information security capability commensurate with the size and extent of threats to its information assets, must test control effectiveness through a systematic testing program, must assess a third party's control testing where it relies on it, and must escalate deficiencies that cannot be remediated in a timely manner to the Board or senior management. Names no external framework. Read 16 November 2026. apra.gov.au
- "How it works: Microsoft Entra multifactor authentication", Microsoft's own documentation for the control most Essential 8 programs implement first. Confirms that multifactor authentication requires two or more of something you know, something you have and something you are, which is the mechanism a framework change does not alter. Read 16 November 2026. learn.microsoft.com
Related Reading
- Cyber Strength Audit
- ASD Replaced the Essential Eight: What It Means for a 50-Person Business
- What Your Provider Should Show You at an Essential 8 Review
- Essential 8 Maturity Model: Level 1, 2 or 3?
- 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


