Blog | Insicon Cyber

ASD Essentials Is Here: Why Boards in Australia and New Zealand Should Now Expect Evidence, Not Assurances

Written by Matt Miller | 18/11/26, 3:53 am

A tick in a box is not evidence.

On 15 October 2026, the Australian Signals Directorate (ASD) launched ASD Essentials. It builds on the Essential Eight and arrives as three chapters: enterprise IT, operational technology and cloud. The Essential Eight stays live while organisations transition, and ASD has been clear that existing regulatory obligations still apply until regulators say otherwise.

Most of the commentary will list what is new. I want to talk about what has changed in kind.

The question has moved from “have you deployed the control?” to “can you show it works?”

That is the position Greg Bunt and I take into every board conversation. Evidence, not assumption. It is good to see the national baseline say it so plainly.

Five weeks on: what has settled and what has not

The dust has settled a little since 15 October. Four things are clearer.

  1. The retirement date is still unofficial. Commentary says the Essential Eight will be deprecated in about 12 months and retired in about 24, and one vendor puts that at mid-2027 and mid-2028. I have not found a formal date from ASD, and the vendor piece I checked gives no primary source. Treat the dates as a planning assumption, not a deadline.

  2. The assessor question is now public. On 16 October the Australian Computer Society warned that ASD's assessment guidance leaves "expert judgement" undefined. It called for a baseline for assessor competency, several forms of skills evidence, and reports that name the assessor and say what was and was not tested. That is fair. If assessors are to be trusted, the standard applied to them should be as clear as the standard applied to the controls. ACS also points to a shortfall of around 54,000 cyber professionals in Australia, so many organisations will need help to do this properly.

  3. Supplier guidance is still to come. ASD has said it will publish guidance on assessing suppliers. Until it does, start with your own evidence and ask your critical suppliers the same questions.

  4. New Zealand is quiet. As at 18 November I have not found an NCSC statement on ASD Essentials. The NZISM continues to govern government agencies.

Why ASD changed it

Three reasons stand out from ASD’s own material.

  1. The technology moved. The Essential Eight was designed to protect internet-connected enterprise IT networks. ASD’s Chris Horlyck told iTnews it predates cloud becoming a major part of the sector. Cloud and operational technology now have chapters of their own.

  2. The threat moved. Stephanie Crowe, head of the Australian Cyber Security Centre, says AI is helping malicious actors operate with greater scale, speed and effectiveness. ASD’s planning guidance goes further. Highly capable adversaries now pose a credible threat to a broader range of organisations, not just the obvious targets.

  3. One number hid too much. Maturity levels were useful. They were also easy to misread. A level tells you what was deployed. It does not tell you whether it holds. Information Age notes the ANAO flagged low cyber resilience across non-corporate Commonwealth entities in 2023, and that audits have found few entities even partly compliant.

What “evidence” now means

Under ASD Essentials there is no target maturity level. Each action is rated in each domain as not assessed, not effective, partially effective or fully effective. Assessors look at coverage, consistency, currency and the quality of the evidence. Deployment records alone do not earn a rating.

Three details I like.

  • The weakest link sets the rating. One weak action holds the whole principle back.
  • “Not assessed” is kept separate from “not effective”. It is an honest way to say what you have not looked at yet.
  • The indicators are blunt. MFA that relies on SMS, voice or push-only prompts is rated not effective. Backups that share the production identity platform cannot rate better than partially effective. An incident response plan that has never been exercised cannot rate better than partially effective.

That last one is a test I already put to boards. When did you last run an incident response exercise under realistic conditions? When did you last restore from backup under time pressure? If the honest answer is “we haven’t”, you are not resilient. You are hoping.

ASD Essentials | Australia and New Zealand

Could your leadership team show the evidence today?

Matt Miller and Greg Bunt help boards and executives in Australia and New Zealand see where their security evidence is strong, where it is thin, and what to do first under ASD Essentials. Start with a straight conversation.

Talk to Insicon CyberRead the ASD Essentials explainer

info@insiconcyber.com | insiconcyber.com

Where assumption hides

Confidence and capability are not the same thing. The organisations that worry me most feel well protected because a box was ticked. That box is meaningful. It does not show your defences would hold under real conditions.

Suppliers are the clearest example. I ask every new client the same question.

Can you name your ten most critical technology suppliers, and tell me what security assurance you hold from each?

Most can name the suppliers. Almost none can answer the second half.

ASD Essentials turns that question into something assessable. Suppliers are selected on a risk assessment, current assurance evidence is retained, and the organisation acts when that assurance lapses. In the cloud chapter, even where the provider does the work, the customer remains accountable for confirming it, using current independent assurance. Executive accountability for cyber security, and for AI, is assessable too.

ASD’s new Asset scoping guide for cloud makes this practical. It asks whether you can actually get the audit logs for a service, or whether they are restricted by service tier or kept for less time than you need. It asks whether you can revoke sessions and preserve evidence mid-incident, and whether losing tenant configuration or encryption keys would stop you restoring. Those are questions you can answer with evidence. They are very hard to answer with a supplier’s brochure. It also starts with a register of the SaaS and PaaS services you use, because you cannot evidence what you have not scoped.

Outsourcing the work does not outsource the accountability.

Raising the level of scrutiny

Boards should be asking harder questions. ASD’s own guidance for senior executives suggests several. These are the ones I would start with, adapted.

  1. Which of our critical functions and assets sit in each domain, and which would hurt most if compromised?
  2. What did our Essential Eight investment buy us, and what is genuinely new work?
  3. When do we see the first posture report, and what will it list as not assessed? Are the reasons good ones?
  4. How will effectiveness be validated, by whom and how often? Independent testing? Exercises?
  5. Where does our plan depart from ASD’s recommended sequence, and what is the documented reason?
  6. Who owns each exception, and when does it expire?

Scrutiny runs both ways. Boards should demand evidence. They should also be open to answers that challenge what they think they already know. And the same standard applies to advisers, including us. ACS has raised the same concern about assessors, so ask who did the assessment, what they tested and what they did not. If I tell you a control is effective, I should be able to show you how we know.

What to do now in Australia and New Zealand

  • Keep the Essential Eight going. Contracts, insurers and regulators still reference it, and ASD says existing investment carries forward. iTnews reports that ASD expects to retire the Essential Eight within about two years. As at 18 November I have still not found a formal date, so plan for it without treating it as a deadline.
  • Baseline first. Map your existing Essential Eight evidence to the Essentials actions. ASD is clear that maturity ratings do not convert automatically, and that stale evidence should not be relied on.
  • Start where ASD starts. For enterprise IT, that means Boundary services and Identity services, with governance and visibility and response running alongside from day one.
  • Pick the right chapter. If your environment is entirely SaaS and PaaS, begin with the cloud chapter. If you run on-premises, hybrid or IaaS, begin with enterprise IT. Most organisations will need both in time.
  • New Zealand. The NZISM remains the baseline for government, and as at 18 November I have still not seen the NCSC respond to the Essentials. New Zealand organisations that use the Essential Eight, or serve Australian customers, should watch closely.
None of this needs a bigger budget to begin. It needs someone to ask for the evidence, and keep asking.
Ask for the evidence.
Then ask when it was last tested.

If you would like a straight view of where your evidence is strong and where it is thin, Greg and I are happy to talk it through with your leadership team, in Australia or New Zealand. Contact us at info@insiconcyber.com.

 

Sources