There is no single Essential Eight maturity level that authorises a PROTECTED system. A PROTECTED system is assessed against the full set of ISM controls applicable at PROTECTED, which includes the Essential Eight controls mapped across maturity levels. Maturity Level Two is the mandatory baseline for non-corporate Commonwealth entities, and Maturity Level Three controls remain applicable and are risk managed.
The question sounds like it should have a clean answer: what Essential Eight maturity does a PROTECTED system need? It does not, because the Essential Eight and the classification of the data measure different things. What follows is how the two relate, what a PROTECTED system is actually held to, and why a maturity level alone never authorises it.
What Essential Eight maturity does a PROTECTED system need?
There is no maturity level that, on its own, clears a PROTECTED system. The maturity model and the Information Security Manual (ISM) classification based applicability answer different questions. The Essential Eight Maturity Model prioritises controls against levels of attacker tradecraft, from Maturity Level One to Three. ISM control applicability is driven by the classification of the data a system stores, processes or communicates.
So a PROTECTED system is assessed against the controls the ISM marks as applicable at PROTECTED, and the Essential Eight controls are inside that set. For non-corporate Commonwealth entities, Maturity Level Two is the mandatory baseline under the Protective Security Policy Framework (PSPF). Controls mapped to Maturity Level Three within the ISM remain applicable to their systems, though their implementation may be risk managed rather than treated as absolute. For the relationship in general, see Essential Eight vs the ISM and the maturity levels explained.
How does the Essential Eight relate to the ISM at PROTECTED?
By containment. The Essential Eight is a prioritised subset of ISM controls, and the controls that map to a maturity level carry an Essential Eight tag in the ISM. That tag lets IRAP assessors see which applicable controls belong to the baseline mitigations while still working through the whole applicable set.
The two axes are worth keeping straight because they are easy to conflate.
| Essential Eight maturity | ISM applicability | |
|---|---|---|
| What drives it | Levels of attacker tradecraft and targeting | The classification of the data the system handles |
| Scope | Eight technical mitigations | The full applicable control set across all domains |
| How it is expressed | Maturity Level One, Two or Three | Applicable at NC, OS, PROTECTED, SECRET or TOP SECRET |
| Where it is measured | An Essential Eight assessment | An IRAP assessment against the ISM |
A control can be both PROTECTED applicable and Maturity Level Three mapped. The classification decides that it applies; the maturity tag marks it as one of the prioritised eight.
Is the Essential Eight enough for a PROTECTED system?
No, and this is the expensive misunderstanding. The Essential Eight covers eight technical mitigations, patching, multi factor authentication, application control, macro settings, application hardening, restricting administrative privileges and backups. A PROTECTED system is measured against the whole applicable ISM control set, which spans governance, personnel security, physical security, cryptography, logging and monitoring, incident response and supply chain assurance, none of which the Essential Eight scores.
A system can reach Maturity Level Two and still fall a long way short of what a PROTECTED assessment against the ISM requires. The Essential Eight is the floor a PROTECTED system must clear as part of a much larger set, not a shortcut around it.
Does Maturity Level Two authorise a PROTECTED system?
No. Reaching Maturity Level Two shows the baseline mitigations are mostly aligned. It is not an authorisation, and it says nothing about the wider ISM controls in scope at PROTECTED. Authorisation follows an IRAP assessment of the applicable controls and a risk based decision by the authorising officer, who accepts the residual risk before the system operates.
This is why the sequencing matters. Getting the Essential Eight stable first is the cheapest risk reduction available, and it makes the larger assessment shorter because the baseline mitigations are already in order when the assessment begins. Chasing the assessment before the baseline is stable means documenting weaknesses that could have been closed beforehand for far less.
How is a PROTECTED system prepared for IRAP assessment?
Confirm the classification of the data with the owning agency first, because it sets which ISM controls apply and therefore the scope of the assessment. Build the System Security Plan annex around the applicable controls, get the Essential Eight mitigations working, then bring the system to assessment. The maturity level is a milestone on the way, not the destination.
For an organisation preparing a PROTECTED system that wants the applicable control set mapped before an assessment, Cybernion provides IRAP assessments and readiness. For the broader Essential Eight baseline, see Essential Eight services and the Essential Eight compliance checklist.
Frequently asked questions
What Essential Eight maturity level does a PROTECTED system need?
There is no single maturity level that authorises a PROTECTED system. A PROTECTED system is assessed against the full set of ISM controls applicable at PROTECTED, which includes the Essential Eight controls mapped across maturity levels. Maturity Level Two is the mandatory baseline for non-corporate Commonwealth entities, and controls mapped to Maturity Level Three remain applicable and are risk managed.
Is the Essential Eight enough for a PROTECTED system?
No. The Essential Eight is a prioritised subset of ISM controls covering eight technical mitigations. A PROTECTED system is measured against the whole applicable ISM control set through an IRAP assessment, which covers governance, personnel, physical and technical controls the Essential Eight never touches.
How does the Essential Eight relate to the ISM for PROTECTED?
The Essential Eight controls are inside the ISM and carry a maturity tag. ISM applicability is based on data classification, while the Essential Eight is based on prioritising controls against levels of attacker tradecraft. The two are mapped, so IRAP assessors see which applicable controls belong to the Essential Eight while assessing all of them.
Do Maturity Level Three controls apply to a PROTECTED system?
Yes. For non-corporate Commonwealth entities, Maturity Level Two is the mandatory baseline, but controls mapped to Maturity Level Three within the ISM are still applicable to their systems. Their implementation may be risk managed rather than treated as an absolute requirement.
Does reaching Maturity Level Two authorise a PROTECTED system?
No. Reaching Maturity Level Two shows eight technical mitigations are mostly aligned. It says nothing about the wider ISM controls a PROTECTED system must meet, and it is not an authorisation. Authorisation follows an IRAP assessment against the applicable ISM controls and a risk decision by the authorising officer.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Essential Eight maturity model and ISM mapping, cyber.gov.au, 2026
- Essential Eight maturity model, cyber.gov.au, 2026
- Information Security Manual, cyber.gov.au, June 2026
- Protective Security Policy Framework, protectivesecurity.gov.au, 2025
Last updated: 3 July, 2026
