BlogCybersecurity

Essential Eight Maturity Assessments, Explained

Published November 3, 2026 · Updated November 17, 2026

Essential Eight Maturity Assessments, Explained

An Essential Eight maturity assessment answers a specific question: how well does a particular system implement the eight mitigation strategies published by the Australian Signals Directorate? It does not tell you everything about your security, and it is not the same thing as a penetration test. Knowing what it does and does not measure is the first step to buying the right one.

The eight strategies

  • Patch applications
  • Patch operating systems
  • Multi-factor authentication
  • Restrict administrative privileges
  • Application control
  • Restrict Microsoft Office macros
  • User application hardening
  • Regular backups

How the maturity levels work

The Essential Eight Maturity Model sets three target levels, Maturity Level One to Maturity Level Three, each designed to mitigate increasingly capable adversary tradecraft. Maturity Level Zero is not a target. It records where the requirements of Maturity Level One are not met.

Three points from ASD’s guidance tend to surprise people. The strategies are implemented and assessed as a package, so a strong result on one does not offset a weak result on another. The target level should be agreed with the system owner before the assessment starts. And assessments follow the levels in order: a system that has not been assessed at Maturity Level One should not begin at Maturity Level Two.

Choosing the right target level

ASD describes each level by the kind of adversary it is designed to stop. Maturity Level One targets opportunistic attackers using widely available tools. Maturity Level Two targets adversaries willing to invest more time and effort. Maturity Level Three targets adaptive adversaries who rely less on public tools and are more likely to go after a specific organisation.

Target levelOften suitsWhat it asks of you
Maturity Level OneSmaller organisations and systems holding little sensitive dataBaseline controls applied consistently across the whole system
Maturity Level TwoOrganisations handling sensitive or personal information, and many government suppliersWider coverage, faster patching, stronger authentication and logging of important events
Maturity Level ThreeSystems likely to be targeted by capable adversariesNear complete coverage, the strongest authentication options and centralised logs that are actively monitored

These are general patterns, not rules. Your target should come from a risk assessment and from any obligations you already have. Commonwealth non-corporate entities, for example, have Essential Eight requirements under the Protective Security Policy Framework, and some contracts set a minimum level for suppliers. The details of each level are revised from time to time, so always work from the current version of the maturity model on cyber.gov.au.

What an assessor looks at

A proper assessment works through the controls one by one and looks for evidence that each is working, not just documented. ASD’s assessment guidance favours stronger forms of evidence, such as seeing a control demonstrated or reviewing logs and scan results, and checking their dates and scope. A written policy on its own shows intent, not effectiveness.

Scope

An assessment applies to a defined system. Be clear about what is in and out, because a result for one environment says nothing about another.

Evidence

Expect to show configuration, logs and demonstrations. Ask how old evidence can be before it stops counting.

Tooling

ASD publishes tools that can support an assessment, including the Essential Eight Maturity Verification Tool and the Application Control Verification Tool.

Output

A useful report states the assessed level for each strategy, the gaps to your target, and what to fix first.

How evidence is weighed

ASD’s assessment process guide grades evidence by quality. Testing a control with a simulated activity is the strongest form, followed by reviewing a control’s configuration directly in the system, then reviewing an exported copy of that configuration. A policy or a verbal assurance is the weakest. In practice, an assessor will want to try running an unapproved application, attempt to open a macro enabled file from the internet, or check patch dates on a sample of machines, rather than read a procedure that says these things happen.

Each control is then given an outcome, such as effective, ineffective, met through an alternate control, or unable to be assessed because there was no visibility. Those outcomes roll up into a maturity level for each strategy.

Where organisations commonly fall short

The same gaps appear again and again, and most are about coverage and proof rather than missing technology. Checking these before an assessment saves a lot of surprises.

Application control on workstations only

Servers are often left out, even though an attacker who reaches a server can do far more damage.

MFA with gaps

Multi-factor authentication is switched on for most staff, but not for administrators, service accounts or older remote access methods.

Backups that have never been restored

A backup is only proven when a restore has been tested. Keep a record of when it was done and how long it took.

Privileged accounts used for everyday work

Administrators reading email or browsing the web with an admin account give attackers an easy route to the most powerful access.

Patching without verification

Patches are deployed, but nobody checks which machines actually installed them or which applications fall outside the patching tool.

How to prepare for an assessment

  • Agree the system boundary and the target maturity level with the system owner
  • List the workstations, servers, applications and online services in scope
  • Do your own dry run of each control on a sample of machines, so the assessment confirms what you already know
  • Gather evidence that shows controls working, such as patch reports, application control logs and backup restore tests, with the dates they were produced
  • Record each exception, why it exists and what compensating control is in place
  • Line up the people who can demonstrate each control on the day

What happens after the assessment

The report is where the useful work starts. Because the strategies are designed to work as a package, one weak strategy undermines the others, so close the gaps that hold the whole system back before polishing the strongest areas. Fix in the order that reduces the most risk, then reassess.

Plan for drift as well. A new application, a missed patch cycle or a temporary exception that quietly becomes permanent can drop a system below the level it once reached. Regular internal checks between formal assessments are the simplest way to keep a result true.

How it differs from other security services

ServiceThe question it answers
External vulnerability scanWhat known weaknesses are visible on our internet facing systems?
Penetration testWhat could a skilled attacker actually do within this scope?
Cyber posture assessmentWhere do we stand overall across controls, governance and exposure?
Essential Eight maturity assessmentWhat maturity level does this system reach against the eight strategies?
Independent assuranceDoes a party with no stake in the result agree with the claims being made?

Reading vendor claims carefully

The Essential Eight is a maturity model, so a claim about it should come with detail. If a vendor says it is aligned or assessed, it is reasonable to ask which system the claim covers, what maturity level was reached, who performed the assessment, and when. We apply the same standard to ourselves: our MedTalk AI product uses Essential Eight aligned controls, and we say so about that product rather than about everything we do.

Frequently asked questions

Is the Essential Eight mandatory?

It is mandatory for Commonwealth non-corporate entities under the Protective Security Policy Framework, and many state agencies and contracts now reference it. For most private organisations it is strongly recommended rather than legally required, but customers and partners increasingly ask about it.

Can we assess ourselves?

Yes. A self assessment is a good way to find gaps and plan work. If the result will support a claim to a customer, a regulator or a board, an independent assessor adds credibility because they have no stake in the outcome.

Should every organisation aim for Maturity Level Three?

No. The target should match the threats you face. Maturity Level Three takes significant effort to reach and maintain, and for many systems Maturity Level Two is the sensible goal. What matters most is reaching your chosen level consistently across all eight strategies.

How often should we reassess?

Whenever the system changes significantly, and on a regular cycle in between. Many organisations reassess formally once a year and run lighter internal checks more often, because controls tend to drift as systems and staff change.

Does the Essential Eight cover cloud and SaaS services?

The Essential Eight was designed mainly for Microsoft Windows based networks connected to the internet. ASD notes it can be applied to other environments, such as cloud services, but that other mitigations may suit them better. Treat it as one part of your security picture, not all of it.

Before you commission an assessment, write down why you need it. Meeting a contract requirement, reporting to a board and building an improvement plan can each call for a different scope and a different level of independence.