Essential Eight maturity levels describe how fully a business has put the Australian Signals Directorate’s eight baseline security strategies in place, from Maturity Level Zero (not meeting the intent of Level One) to Maturity Level Three (fully implemented against capable, adaptive attackers). For most small businesses, the practical goal is to reach Maturity Level One across all eight strategies first, then decide whether Level Two is worth the extra effort.

The maturity model can look daunting to an owner or office manager who also looks after IT. This guide explains each level in plain terms, shows what it looks like in a small business and sets out a realistic plan for getting there.

A quick refresher: the eight strategies

The Essential Eight is a set of mitigation strategies published by the Australian Signals Directorate (ASD) through the Australian Cyber Security Centre. In short, they are:

For a fuller walkthrough of each strategy and how the model applies to larger organisations and government, see our Essential Eight guide. This article focuses on the maturity levels from a small-business point of view.

The four maturity levels in plain English

Each maturity level is defined by the kind of attacker it is designed to resist. Higher levels widen the scope (more systems and more users), tighten the timeframes for actions such as patching, and add requirements such as centrally storing and reviewing certain event logs.

Maturity Level Zero

A strategy sits at Level Zero when it does not yet meet the intent of Level One. In a small business this often looks like: staff sign in to email with a password only, several people use an administrator account day to day, updates are installed “when someone gets to it” and backups exist but nobody has tried restoring them.

Maturity Level One

Level One is aimed at opportunistic attackers who use widely available tools and look for any easy target, such as a stolen password or an unpatched internet-facing service. For a small business, reaching it usually means MFA is on for email and other internet-facing services, updates are applied within the timeframes the model sets, admin rights are limited, macros are restricted and backups are taken and protected.

Maturity Level Two

Level Two is aimed at attackers who are prepared to spend more time and effort and who target a business more deliberately, for example with convincing phishing aimed at the finance team. The controls extend further across systems and users, timeframes are tighter, and some logging and review requirements appear. Australian Government agencies use Level Two as their baseline, and some suppliers to government are asked about it.

Maturity Level Three

Level Three is aimed at capable attackers who adapt quickly and exploit weaknesses fast. It requires the controls to be fully in place and working consistently, which usually means dedicated IT capability and strong management tooling. Few small businesses need to target Level Three unless their risk or their customers demand it.

Why “across all eight” matters

ASD recommends choosing a target maturity level and reaching it across all eight strategies before moving higher. Attackers look for the weakest point: a business with excellent backups but no MFA on email is still easy to break into.

How to choose a target maturity level

There is no single right answer, but three questions help.

  1. What do your customers and contracts ask for? Tenders, supplier questionnaires and cyber insurance forms often ask about the same controls. If a key customer asks for a stated maturity level, that becomes your target.
  2. What would an incident cost you? A business that holds sensitive client records, makes payments on behalf of others or cannot trade without its systems has more reason to aim higher.
  3. What can you sustain? A level only counts if the controls keep working. Pick a target you can maintain with the people and tools you have, then raise it.

For most small businesses, a sensible pattern is to aim for Level One across all eight strategies, keep evidence that the controls work, and then review whether Level Two is justified.

A practical plan for small businesses

1. Know what you have

List the computers, servers, cloud services and admin accounts. You cannot protect what you have not counted.

2. Start with the quick, high-value controls

Turn on MFA for email and other internet-facing services, remove day-to-day admin rights from staff accounts and set automatic updates for operating systems and common applications.

3. Protect and test your backups

Make sure backups of important data and settings run regularly, cannot be easily changed or deleted by an attacker, and can actually be restored. Schedule a test restore and record the result.

4. Tackle the harder strategies

Application control, macro restrictions and application hardening take more planning, because they can affect how people work. Start with a pilot group, adjust, then extend.

5. Keep evidence as you go

Record what was changed, who did it, when, and how it was checked. Settings screenshots, update reports and restore test records all help if a customer, insurer or assessor asks.

6. Watch for drift

Controls drift over time: a laptop misses updates, a new admin account appears, a backup job starts failing. Regular checks, or monitoring that flags these changes, stop a level quietly slipping.

Illustrative examples

The following examples are illustrative scenarios, not real customers.

Illustrative example: a 12-person accounting practice. The practice holds client tax records and uses cloud email and accounting software. It sets Level One as its target, turns on MFA for all staff, removes admin rights from everyday accounts, enables automatic updates and starts monthly test restores of its file backups. Macro restrictions are piloted with two staff before being applied to everyone. The practice keeps a simple log of each change so it can answer insurer questions with evidence.

Illustrative example: a 40-person manufacturer supplying a government agency. A new contract asks the business to describe its Essential Eight maturity. It first reaches Level One across all eight strategies, then plans a move towards Level Two for the systems that handle contract data. Because Level Two adds logging and review expectations, it brings security events from its computers into one place so that unusual sign-ins and failed backup jobs are noticed promptly.

Limitations to keep in mind

How CiBRAI approaches Essential Eight for smaller businesses

CiBRAI is an Australian-owned, agentic-AI cybersecurity operating platform that brings SIEM, SOAR, threat intelligence, GRC, case management and automated response together, with an always-on AI analyst layer and human approval for high-impact actions. For a small business working towards a maturity level, it helps with the monitoring and evidence side of the job.

CiBRAI SME monitors up to 20 supported Windows, macOS and Linux machines with live SIEM alerts, AI assistance and threat intelligence context in an isolated, Australian-hosted workspace, so changes such as suspicious sign-ins can be investigated and recorded. Essential Eight reporting, with control evidence and trend reporting, is included in the Growth, Business and Enterprise plans; see plans and pricing for what each tier covers.

CiBRAI does not make a business Essential Eight compliant and is not certified or endorsed by ASD. You still need to implement the controls, and maturity is confirmed by assessing your own environment.

Frequently asked questions

Is the Essential Eight mandatory for small businesses?

For most private businesses it is not a legal requirement. It is recommended by ASD and is increasingly requested by customers, government buyers and insurers, so many small businesses adopt it voluntarily.

What maturity level should a small business aim for?

Most small businesses start with Maturity Level One across all eight strategies. Move towards Level Two if your customers, contracts or risk call for it, and only once Level One is stable.

How long does it take to reach Maturity Level One?

It depends on the number of systems, how they are managed and who does the work. MFA, admin rights and automatic updates can often be addressed quickly; application control and macro restrictions usually take longer to plan and test.

Who can assess our maturity level?

You can self-assess using ASD’s published guidance, but an independent assessment by a qualified provider gives customers and insurers more confidence. Either way, the result should be based on evidence that the controls work in practice.

Want to see how monitoring, evidence and reporting fit into your Essential Eight plan? Book a CiBRAI demo.

Leave a Reply

Your email address will not be published. Required fields are marked *