Why the Essential Eight still matters in 2026
The ACSC Essential Eight (Australian Cyber Security Centre — Essential Eight Maturity Model, accessed 3 November 2026) provides a practical baseline for reducing common cyber risks. It can support an organisation's security program and evidence, while Privacy Act compliance still depends on the reasonable steps appropriate to the organisation's circumstances.
1) What is the ACSC Essential Eight and why it matters
- Threat reduction: Focused on preventing or limiting ransomware, BEC, and privilege escalation.
- Regulatory alignment: Supports Privacy Act obligations for reasonable security controls and data breach minimisation. The OAIC's guidance on the Australian Privacy Principles (Office of the Australian Information Commissioner — Australian Privacy Principles (APP 11), accessed 16 June 2026) speaks to outcomes rather than naming a specific framework; in our reading, implementing the Essential Eight is a practical and defensible way to evidence the reasonable security steps APP 11 expects.
- Supplier expectation: Commonwealth buyers and primes often request maturity evidence in tenders.
- Audit-ready: Evidence gathered here reuses well for ISO 27001 Annex A and customer due diligence.
2) The eight controls explained
- Application control: Allow-list trusted binaries and scripts using WDAC/AppLocker.
- Patch applications: Apply the timeframe for the product category and target maturity; the 48-hour trigger applies to defined categories when the vendor rates a vulnerability critical or a working exploit exists.
- Configure Office macros: Disable macros where there is no business need, block internet-origin macros, enable macro antivirus scanning and add the controls required at higher maturity levels.
- User application hardening: Disable Flash/ads/Java where not needed; enforce SmartScreen and restrict plug-ins.
- Restrict admin privileges: Use separate privileged accounts, restrict their use and centrally log privileged events; JIT/JEA can support the design where appropriate.
- Patch operating systems: Apply the operating-system timeframes for the system category, maturity level, vendor rating and exploit status, using tested deployment rings.
- Multi-factor authentication (MFA): Enforce MFA for admins, remote access, and later all users; block legacy auth.
- Regular backups: Immutable/offline copies, separated credentials, and monthly restore tests.
3) Maturity assessment model (Level 0-3)
- Level 0: Controls largely absent or ad-hoc; high exposure to common ransomware techniques.
- Level 1: Partial coverage; some endpoints or apps excluded; exceptions unmanaged.
- Level 2: Systematic enforcement with monitoring; exceptions tracked; resistant to commodity attacks.
- Level 3: Broad enforcement, strong monitoring, and tamper resistance; robust against targeted tradecraft.
Planning target: EDUC4TE commonly uses Level 2 within 12 months as a starting planning assumption. Confirm the target against the organisation's risk assessment, PSPF obligations, regulator expectations and contracts.
4) Implementation roadmap (12-month timeline)
Quarter 1: Baseline and quick wins
- Inventory endpoints/servers and privileged accounts; classify crown-jewel apps and data.
- Enable MFA for admins and remote access; block legacy protocols (POP/IMAP/SMTP Basic).
- Start AppLocker/WDAC in Audit on a pilot OU; capture blocks; refine allow rules.
- Set browser and Office macro baselines: block internet macros; enable SmartScreen.
- Identify backup scope; create an immutable/offline copy; run a test restore.
Quarter 2: Enforce and expand
- Move application control pilots to Enforce for kiosks/labs, then finance and IT devices.
- Implement category-specific patch SLAs, including an emergency 48-hour path where the current model applies, with ringed deployments (pre-prod → pilot → broad).
- Remove standing admin rights; adopt JIT (Privileged Access Management) and JEA for servers.
- Harden user apps: disable Flash, restrict untrusted fonts/plug-ins, enforce signed macros only.
- Backups: enforce MFA on the backup console; separate credentials and network path.
Quarter 3: Monitor and verify
- Centralise logs (EDR + SIEM) for control bypass attempts: unsigned execution, MFA disabled, backup failures.
- Drift detection: weekly reports on patch age, MFA coverage, privileged group changes, allow-list coverage.
- Purple-team each control; tune rules and detections for bypass techniques.
- Restore testing: monthly VM/database restores with measured RTO/RPO.
Quarter 4: Optimise and evidence
- Policy-as-code for Intune/GPO baselines; peer-review changes before rollout.
- Evidence packs: policy exports, screenshots, SIEM dashboards, restore logs, exception register.
- Run ransomware tabletop; validate runbooks; close gaps in access recovery and comms.
- Map Essential Eight evidence to ISO 27001 controls to minimise duplicate effort.
5) Australian government contractor requirements
- Tenders: Expect clauses requiring Essential Eight alignment and stated maturity levels. Non-corporate Commonwealth entities are directed to implement the Essential Eight under the Protective Security Policy Framework (PSPF), and primes increasingly ask suppliers to state their maturity level in tender responses.
- Evidence: Provide policy exports, Conditional Access summaries, allow-list coverage, backup restore proofs.
- Data residency: Ensure backups/logs respect contractual and Privacy Act requirements; confirm regions with providers.
- Supply chain: Flow requirements to subcontractors handling Commonwealth data; assess their MFA, patching, and backup practices.
6) ROI and business case
- Cost avoidance: Reduced ransomware likelihood and faster containment; Mid-size data breaches commonly run to substantial total costs once investigation, remediation, and reputational impact are included.
- Downtime reduction: Ringed patching and allow-listing shrink outbreak clean-up time.
- Audit efficiency: Shared evidence supports ISO 27001 and customer due diligence.
- Sales advantage: Demonstrable maturity helps win government and enterprise contracts.
Practical examples (config and code)
Example 1: AppLocker publisher rule (start in audit)
# Build publisher rules from a reference device and save them to an XML policy file
Get-AppLockerFileInformation -Directory "C:\\Program Files" -Recurse -FileType Exe |
New-AppLockerPolicy -RuleType Publisher -User Everyone -Xml |
Out-File ".\\AppLockerPolicy.xml"
# Merge the policy into the effective local policy, then set the rule collections to
# "Audit only" (in the policy XML or via GPO) so blocks are logged without being enforced
Set-AppLockerPolicy -XmlPolicy ".\\AppLockerPolicy.xml" -Merge
Start the rule collections in Audit only enforcement mode to capture legitimate binaries, then switch to Enforce rules by ring.
Example 2: Conditional Access MFA rollout (phased)
- Phase 1: All admins + remote access; block legacy auth.
- Phase 2: High-risk apps (finance, HR); include device compliance checks.
- Phase 3: All users, with monitored break-glass accounts excluded from MFA but heavily audited.
Example 3: Backup resilience
- Primary: Daily incrementals, weekly fulls, 30-90 day retention.
- Secondary: Immutable object storage; separate admin credentials and network path.
- Test: Monthly restore of a representative VM/database; document RTO/RPO.
Common pitfalls and how to avoid them
- Application control rollouts break apps: Pilot in audit, refine, then enforce with rings; keep an exception queue.
- Patch latency due to change windows: Pre-prod rings and emergency change paths for critical CVEs.
- MFA gaps: Legacy protocols bypass Conditional Access; block legacy auth and monitor sign-ins.
- Privilege sprawl: Stale admin groups; implement JIT/JEA and quarterly access reviews. Privilege abuse is a consistent, widely reported contributor to confirmed breaches, which reinforces the importance of Control 5 in the Essential Eight.
- Unrestorable backups: Immutable/offline copies plus monthly restore tests; monitor job success, not just start events.
Before / after
Before: Standing admin rights, monthly patching, macros unrestricted, backups only online.
After (Level 2/3): JIT admin with PAWs, risk-based patch SLA, signed-only macros, enforced allow-listing, immutable backups with tested restores.
Evidence to collect
- Policy exports: AppLocker/WDAC XML, Intune and GPO baselines, Conditional Access JSON.
- Coverage metrics: patch age, MFA %, allow-list blocks, privileged group changes, backup success.
- Restore proofs: timestamped logs with RTO/RPO results.
- Exception register: time-bound exceptions and compensating controls.
Call to action
Assess where you are today, prioritise quick wins, and drive to Level 2+ within a year using disciplined rollout and evidence.
Sources referenced in this article: ACSC Essential Eight Maturity Model, OAIC (Australian Privacy Principles, APP 11), Australian Signals Directorate (ASD).
CTA: Assess your Essential Eight maturity with our free self-assessment tool.


