Module 2 of StartCloud's Essential Eight for Australian Business pathway, in six short units with a knowledge check: the four Essential Eight maturity levels (Zero through Three) defined by the attacker tradecraft each is built to stop, the commonly missed rule that you must reach the same level across all eight controls before moving higher, what each level usually means when a contract, insurer or the WA Government policy asks for it, how exceptions can be handled without failing a level, a practical first-pass self-assessment, and how ASD Essentials (published 15 October 2026) replaces target maturity levels with priority phases and per-domain effectiveness ratings, with no automatic conversion but existing work and evidence carrying forward.
Maturity levels without the jargon
Four levels, not three
There are four maturity levels, not three. Level Zero is a real level and a lot of businesses are sitting in it without knowing.
This is the part that makes the whole model click: the levels are not defined by how much effort you have put in. They are defined by the kind of attacker they are designed to stop. ASD builds each level around a level of tradecraft and targeting, so a level really describes which sort of attacker you are resistant to.
One thing to know up front: maturity levels belong to the Essential Eight. ASD Essentials (the Essentials series), the successor ASD published in October 2026, does not use them, and unit 5 of this module explains what it does instead. They are still worth understanding, because insurers, customers and WA Government tenders still ask about them.
Not a badge of shame, just a starting point. It means there are gaps in the overall security posture that, if exploited, could compromise your data or your systems. Most businesses that have never looked start here, including plenty who assume otherwise.
Aimed at attackers using commodity tradecraft that is widely available, for example a publicly available exploit against an unpatched online service, or logging in with credentials that were stolen, reused, brute forced or guessed. ASD describes these attackers as looking for any victim rather than a specific victim.
A modest step up. These attackers invest more time and better tools, actively target credentials with phishing, and use technical and social engineering techniques to get around weak multi-factor authentication. They are more selective about targets, and will hunt for accounts with special privileges.
Attackers who are much less reliant on public tools, who exploit weaknesses like old software or poor logging, and who can circumvent even stronger multi-factor authentication by stealing authentication token values. They pivot across a network, seek password hashes, and cover their tracks.
ASD makes a useful point here. The same attacker might use crude methods against one target and sophisticated ones against another, so trying to guess "who would attack us" is the wrong question. Ask instead what level of skill and persistence you want to be resistant to.
The rule everyone misses
This is the single most commonly missed rule in the whole model, and getting it wrong makes a business sound much better prepared than it is.
ASD is explicit. The eight strategies are designed to complement each other and cover different threats, so you implement to achieve the same maturity level across all eight, then move up. Being brilliant at backups and hopeless at patching does not average out to something respectable. Your maturity is effectively set by your weakest of the eight.
Pouring effort into the two controls you find easiest, reaching Level Two on those, and describing the business as "working towards Level Two". Meanwhile application control has never been touched, so the real answer is still Level Zero.
Get all eight to Level One first, even where that feels unambitious. A flat Level One across the board is stronger, and far easier to defend to an assessor, than a jagged profile with a couple of showpieces.
Real businesses have awkward corners: the legacy application that breaks when patched, the machine that cannot be locked down. ASD expects a risk-based approach. Keep exceptions few and narrow, use compensating controls, limit how many systems and users are affected, and document and approve each one through a proper process, then review them regularly. Handled that way, an exception does not automatically stop you meeting a maturity level.
Which level, if any, you need
Under the Essential Eight, ASD asked organisations to pick a target level suitable for their environment and work up to it, based on how desirable a target they are and how badly a breach would hurt.
ASD Essentials has dropped that step. Organisations no longer choose a target maturity level, and ASD now advises against starting work purely to reach a superseded Essential Eight target, unless a regulator or other obligation still requires it or the work addresses a material risk. So for most businesses the useful question is not which level to aim for, it is which level, if any, somebody is asking you for. Here is what each one usually means when it turns up.
This is the level the WA Government's Cyber Security Policy still refers to. It is built to stop attackers hunting for any victim rather than a specific one, which is precisely the traffic a typical Perth business faces: automated scanning, reused passwords, unpatched services. If a contract, insurer or tender asks for it, all eight need to be at Level One, not most of them.
Usually written into a contract, or into a larger customer's supplier requirements. Level Two assumes attackers who will phish your people properly and try to work around weak multi-factor authentication, so it changes what counts as good enough MFA. If you hold sensitive client data or move significant money, stronger sign-in is worth having whoever is asking, and ASD Essentials calls for phishing-resistant MFA anyway.
Level Three is demanding and expensive, and it is normally driven by a government directive, a regulator, or a contract rather than a business choosing it. ASD is also blunt that Level Three will not stop an attacker willing and able to invest enough time, money and effort. There is no level that makes you safe.
A business with a real, evidenced Level One is in far better shape than one that has spent two years reaching for Level Three and finished neither. If somebody has asked you for a level, complete it across all eight. If nobody has, put the effort into the work itself, in the order module 7 sets out, rather than into reaching a score ASD has moved away from.
Working out where you are
You cannot claim a level without checking, and checking is more straightforward than most people expect. The detailed requirements live in the maturity model itself: Appendices A through C set out what each of Levels One, Two and Three demand, control by control. Appendix D compares the levels side by side with the changes shown in bold, which is the fastest way to see what stepping up would cost you.
For a formal assessment, ASD publishes a separate Essential Eight assessment process guide. Module 8 of this pathway covers assessments and evidence properly, including the question everyone asks about whether you need to be certified.
- Take the eight controls one at a time and write down what you do today, not what you intend to do
- For each, decide whether it is nothing, partial, or fully in place everywhere, without rounding up
- Anything partial is not that level yet. Partial is the most common self-assessment error
- Your overall position is your weakest control, not your average
- Write the gaps down with a rough cost and an owner. That list is now your plan
Our Essential Eight self-assessment checklist turns all of this into 24 simple questions you can work through in a sitting. No email required, and it prints cleanly if you would rather do it on paper with the team.
Open the free self-assessment checklistDo not be discouraged if that afternoon ends with Level Zero written at the bottom of the page. That is where most businesses start, and knowing it is the difference between a plan and a guess. The next four modules walk through the eight controls themselves, so you will know exactly what "in place" looks like for each one.
How ASD Essentials changes this
Everything so far is how the Essential Eight works, and it is still the language insurers, customers and WA Government tenders use. On 15 October 2026, though, ASD published ASD Essentials as its successor, and it measures progress in a different way. Three changes matter for this module.
You no longer pick a level to aim for. ASD Essentials sets out priority phases, which are a recommended order of work, not a score. Sign-in and identity, along with anything facing the internet, come first. Admin access and critical systems come second. Business systems and staff devices come third. Governance and monitoring run alongside all three.
Instead of one level for the whole business, each action is assessed in each area it applies to, and rated as not assessed, not effective, partially effective or fully effective. The question shifts from "is it in place?" to "is it working, and can you show it?"
There is no automatic translation from a maturity level to the new ratings. ASD is clear that even Maturity Level Three does not automatically mean fully effective. What does carry over is the work: controls you have in place, and evidence that is current and relevant, become the starting point for a gap analysis.
No switch-over date has been set. ASD is working with regulators and will advise on expectations, and it says anyone with a contractual, regulatory or other obligation tied to the Essential Eight should keep meeting it. So if someone asks you for a maturity level, answer in maturity levels. If nobody is asking, work in the order of the priority phases rather than towards a superseded target. ASD Essentials is written mainly for Commonwealth entities, critical infrastructure and large organisations, though ASD says smaller businesses can use it where relevant.
- cyber.gov.au: Essential Eight maturity model (Australian Signals Directorate)
- cyber.gov.au: Essential Eight explained
- cyber.gov.au: Transitioning from the Essential Eight (ASD Essentials)
- cyber.gov.au: ASD Essentials frequently asked questions
Maturity level descriptions checked against ASD guidance in August 2026, and the ASD Essentials changes in November 2026. The Essential Eight maturity model is still published on cyber.gov.au, so read the current version, and the exact wording of the contract or tender, before answering in maturity levels.
Knowledge check
5 quick questions. Get 4 right and the module is yours.
1. How many maturity levels are there, and what does the lowest mean?
2. You are strong on backups and MFA but have never looked at application control. What is your maturity?
3. What kind of attacker is Maturity Level One designed to stop?
4. Your business reached Essential Eight Maturity Level Two last year. What does that mean under ASD Essentials?
5. Your business has one legacy application that cannot be patched. Does that stop you meeting a maturity level?