Framework · Cybersecurity · Australia
Essential Eight compliance: the 8 strategies and maturity levels
Essential Eight compliance means implementing the eight mitigation strategies published by the Australian Signals Directorate to the maturity level your risk calls for. The current maturity model, updated in November 2023, defines levels zero to three, and Australian government entities generally target maturity level two.
What you need to know about Essential Eight
Who needs the Essential Eight?
Australian government entities by policy, and many suppliers and businesses by contract or choice.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does the Essential Eight require?
The Essential Eight requires eight mitigation strategies, implemented to a chosen maturity level, with each level's requirements met across all eight before moving to the next.
Prevent malware delivery
Application control, patching apps, macros, hardening.
In QULDEX: Requirements per levelLimit the extent
Admin privileges, OS patching, MFA.
In QULDEX: Privileged access reviewsRecover data
Regular, tested, protected backups.
In QULDEX: Restore testsMaturity levels
Same level across all strategies.
In QULDEX: Maturity tracked per strategyWhat are the Essential Eight strategies and maturity levels?
The eight strategies and the four maturity levels. Select any one to see what it asks for, typical evidence and the matching ISO 27001 and CIS Controls references.
Showing up to 6 per group. Search, filter, or open a group to see all 12.
Prevent malware delivery 4
E8-1Application controlAllow only approved applications, scripts and libraries to run on workstations and servers.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
- Typical evidence
- Allow-list policy, test results
- Maps to
- ISO 27001 A.8.19CIS 2
E8-2Patch applicationsPatch internet-facing services, browsers, office and security products quickly, and remove unsupported applications.
In QULDEXPatch timelines are tracked against the maturity level's targets.
- Typical evidence
- Patch reports
- Maps to
- ISO 27001 A.8.8CIS 7
E8-3Configure Microsoft Office macro settingsBlock macros from the internet and allow only trusted, signed or vetted macros.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
- Typical evidence
- Group Policy evidence
- Maps to
- CIS 4
E8-4User application hardeningHarden browsers and office apps, for example blocking ads, Java and web scripts where not needed.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
- Typical evidence
- Hardening baselines
- Maps to
- ISO 27001 A.8.9
Limit the extent of incidents 3
E8-5Restrict administrative privilegesLimit, validate and review privileged access; keep privileged accounts away from email and web browsing.
In QULDEXPrivileged access reviews run as recurring tasks.
- Typical evidence
- Privileged user list, reviews
- Maps to
- ISO 27001 A.8.2CIS 5
E8-6Patch operating systemsPatch operating systems quickly, and replace unsupported versions.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
- Typical evidence
- Patch reports
- Maps to
- ISO 27001 A.8.8
E8-7Multi-factor authenticationUse MFA for online services, remote access and privileged users; phishing-resistant MFA is expected at higher levels.
In QULDEXMFA coverage is tracked per system and user type.
- Typical evidence
- MFA settings
- Maps to
- ISO 27001 A.8.5CIS 6
Recover data and availability 1
E8-8Regular backupsBack up important data, software and settings, test restoration, and protect backups from unauthorised change.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
- Typical evidence
- Backup logs, restore tests
- Maps to
- ISO 27001 A.8.13CIS 11
Maturity levels 4
ML0Maturity level zeroMaturity levelWeaknesses in the overall posture that would let an adversary easily compromise systems.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
ML1Maturity level oneMaturity levelDefends against adversaries using commodity tradecraft and widely available tools.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
ML2Maturity level twoMaturity levelDefends against adversaries willing to invest more time and use more effective tools; the common target for government entities.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
ML3Maturity level threeMaturity levelDefends against more adaptive adversaries that are less reliant on public tools.
In QULDEXQULDEX tracks this strategy's maturity level with evidence per requirement, so the next assessment starts from current proof.
Nothing matches that search.
Strategy names follow the ASD Essential Eight Maturity Model (November 2023). Summaries are QULDEX paraphrases; check cyber.gov.au for each level's exact requirements.
How do you reach an Essential Eight maturity level?
Pick a target level, assess each strategy against it, close the gaps across all eight, then assess again. Most organisations need 3 to 9 months per level.
Choose the target level
Based on risk, contracts or government policy.
Assess each strategy
Test against the level's requirements, using ASD's assessment process guide.
Close gaps strategy by strategy
Usually MFA, admin privileges and patching first.
Prove it with evidence
Configuration exports, patch reports and test results.
Independent assessment
Where contracts or policy require it.
Hold the level
WeeklyPatch and MFA reportsYearlyRe-assess maturityNext levelRepeat for the next target
Durations are QULDEX planning ranges.
Which evidence does an Essential Eight assessment need?
Assessors look for configuration and test evidence, not just policies.
| Evidence | Strategy | Where it lives in QULDEX |
|---|---|---|
| Application control rules and test results | E8-1 | Evidence vault |
| Patch reports with timelines | E8-2, E8-6 | Evidence vault |
| Macro settings | E8-3 | Evidence vault |
| Hardening baselines | E8-4 | Evidence vault |
| Privileged user list and reviews | E8-5 | Evidence vault |
| MFA configuration and coverage | E8-7 | Evidence vault |
| Backup logs and restore tests | E8-8 | Evidence vault |
| Maturity assessment report | All | Audit workspace |
Evidence names are QULDEX recommendations based on ASD guidance.
How long does the Essential Eight take and what drives the effort?
Most organisations need 3 to 9 months to reach maturity level two. Application control, patching speed and phishing-resistant MFA drive most of the effort.
Where the time goes
Bars show the upper end of each range on one scale (9 months = full width).
What changes the effort
- Target level: each level adds requirements
- Estate size: more endpoints and servers to cover
- Legacy systems: unsupported software must be removed
- MFA type: phishing-resistant methods take longer
- Existing CIS or ISO 27001: covers parts of the work
How mature is your Essential Eight?
Check these eight things first. Nothing you enter leaves this page.
How the Essential Eight maps to CIS Controls, ISO 27001 and NIST CSF
The Essential Eight is a prioritised technical baseline; CIS Controls and ISO 27001 cover the same ground and more.
Essential Eight crosswalk
| Essential Eight | CIS Controls v8.1 | ISO 27001:2022 | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|---|
| Application control | CIS 2 | A.8.19 | PR.PS | Allow-lists |
| Patching | CIS 7 | A.8.8 | ID.RA, PR.PS | Patch reports |
| Macros and hardening | CIS 4 | A.8.9 | PR.PS | Baselines |
| Admin privileges | CIS 5 | A.8.2 | PR.AA | Admin reviews |
| MFA | CIS 6 | A.8.5 | PR.AA | MFA settings |
| Backups | CIS 11 | A.8.13 | PR.DS, RC.RP | Restore tests |
Indicative mapping for planning.
How QULDEX runs the Essential Eight from assessment to maturity level
QULDEX is Essential Eight assessment and evidence software built from EGV Group's audit delivery, used by organisations, their MSPs and the assessors who check them. Pick your role to see who does what.
For government entities and businesses.
- TargetSet the target levelTarget per strategy
- AssessSelf-assessRequirements per level with evidence
- FixClose gapsGaps into CAPA
- ProveCollect evidenceConfiguration and patch evidence
- ReportReport maturityMaturity by strategy
- HoldKeep the levelRecurring evidence
For MSPs and security consultants.
- TargetAdviseRisk-based recommendation
- AssessRun the assessmentA reusable E8 template
- FixImplementProgress dashboard
- ProveReview evidenceReview states
- ReportBrief leadershipBoard-ready report
- HoldMonitorDashboard across clients
For independent Essential Eight assessors.
- TargetPlanScope in a standard format
- AssessReviewView-only access
- FixRetestRetest evidence
- ProveAssessView-only evidence with download control and an access log
- ReportReportFindings per strategy
- HoldRe-assessFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →Essential Eight questions people ask
What is the Essential Eight?
Eight mitigation strategies published by the Australian Signals Directorate: application control, patching applications, configuring Microsoft Office macros, user application hardening, restricting administrative privileges, patching operating systems, multi-factor authentication and regular backups.
What are the Essential Eight maturity levels?
Levels zero to three. Each level defends against a more capable adversary, and you reach a level only when all eight strategies meet it.
Who must meet the Essential Eight?
Australian Commonwealth entities under the Protective Security Policy Framework, generally to maturity level two. Others adopt it by contract or choice.
Is the Essential Eight being replaced?
ASD consulted in 2026 on expanding it into a broader "Essentials" series. The November 2023 maturity model remains the one assessed against until ASD publishes a replacement.
How is the Essential Eight assessed?
Against ASD's Essential Eight Assessment Process Guide, by testing each strategy's requirements at the target level with technical evidence.
Go deeper on Essential Eight
NIST & CIS topic hub
NIST CSF, 800-53 and CIS Controls articles.
blog.quldex.comAudit evidence naming convention
A file-naming scheme assessors can follow.
blog.quldex.comAudit sampling size for compliance
How many samples assessors look at.
blog.quldex.comNIST CSF 2.0: the Govern function explained
Governance around a technical baseline.
References
- ASD, Essential Eight Maturity Model, November 2023. cyber.gov.au
- ASD, Essential Eight Assessment Process Guide. cyber.gov.au
- Protective Security Policy Framework. protectivesecurity.gov.au
- iTWire, Essential Eight: what applies now and what ASD is changing, 2026. itwire.com
Reviewed by
Page history
- : Page first built: strategy explorer, maturity levels and readiness check
Know your Essential Eight maturity level
Answer a short readiness check and get an indicative maturity level. No sales call needed to see the result.