Home  /  Insights  /  Essential Eight vs ISO 27001: which should you do first?
Insights

Essential Eight vs ISO 27001: which should you do first?

One is a prescriptive set of technical controls from the ASD. The other is an international, certifiable management system. They're complementary, and the right order depends on who's asking.

Cyber Veda

Quick answer: The Essential Eight is the ASD's set of eight technical mitigation strategies, assessed against maturity levels; there is no certificate. ISO 27001 is a certifiable management system covering risk, governance and 93 controls. If a customer or tender needs a certificate, start with ISO 27001 and set an Essential Eight maturity target inside it. If you need quick technical risk reduction, start with the Essential Eight.

How they differ

Essential EightISO 27001
OriginAustralian Signals Directorate (ASD)ISO/IEC international standard
FocusEight technical controls to stop common attacksA management system for all information security risk
How controls are chosenPrescribed: the same requirements for everyone at a given levelRisk-based: you select controls from your own risk assessment
OutcomeA maturity level (0 to 3) from an assessmentA certificate from an accredited body
Who checks itYou, or an independent assessor of your choiceAn accredited certification body
How long the result lastsA point-in-time rating; buyers usually expect it to be recentThree years, with surveillance audits in years one and two
Covers people and process?BarelyYes: governance, suppliers, HR, incidents, continuity
Recognised overseas?RarelyGlobally

The simplest way to hold the difference: the Essential Eight tells you what to configure on your systems, while ISO 27001 tells you how to run security as a managed, reviewed process across the whole business. Neither replaces the other.

The eight strategies

Application control, patch applications, configure Microsoft Office macro settings, user application hardening, restrict administrative privileges, patch operating systems, multi-factor authentication and regular backups. Our Essential Eight page explains each one and what the maturity levels require.

In October 2026 the ASD published ASD Essentials, the evolution of the Essential Eight, which swaps strategies and maturity levels for principles, actions and domains, and gives governance far more weight. The Essential Eight is still what PSPF, DISP and most tenders assess today. See Essential Eight to ASD Essentials for what changes.

Maturity levels in brief

Each maturity level is built to resist a more capable attacker. Level One targets opportunistic attackers using commodity tools; Level Two, attackers willing to invest more time and better tools; Level Three, adaptive attackers who are less reliant on public tools. Level Zero means Level One isn’t met. The levels are cumulative, and the Essential Eight is implemented and assessed as a package: if one strategy falls short, you can’t claim the level.

The requirements are specific. Take patching. At every level, patches for vulnerabilities in internet-facing online services must be applied within 48 hours when the vendor rates them critical or a working exploit exists, and within two weeks otherwise. Level Two adds patching of all other applications within one month and vulnerability scanning of them at least fortnightly. ISO 27001 would never state a number like that. It asks you to decide one, justify it through risk and prove you meet it.

How each one is assessed

Essential Eight

There is no accredited Essential Eight assessor and no certificate. You either self-assess or engage an independent assessor, usually following ASD’s Essential Eight Assessment Process Guide. The guide ranks evidence by quality. Testing a control with a simulated activity, such as trying to run an unapproved program, is the strongest. Reviewing live configuration comes next, then screenshots or reports of configuration. A policy or a verbal assurance is the weakest. Assessors sample workstations, servers and network devices, usually with scripts rather than interviews, and report a level per strategy.

ISO 27001

An accredited certification body audits your ISMS in two stages: a Stage 1 review of design and readiness, then a Stage 2 audit of whether the system actually operates, sampling records over a period of time. See Stage 1 and Stage 2 audits. The auditor checks your clauses 4 to 10 processes and the controls in your Statement of Applicability, but judges them against your own risk decisions, not a fixed configuration. Surveillance audits follow in years one and two, and recertification in year three.

The practical consequence: an ISO 27001 certified business can still be at Maturity Level Zero on some strategies, and a business at Level Two can have no ISMS at all. Buyers that ask for both expect to see both.

Where they overlap

Every Essential Eight strategy maps to one or more ISO 27001 Annex A controls, such as 8.8 technical vulnerability management, 8.2 privileged access rights, 8.5 secure authentication, 8.13 information backup and 8.19 installation of software. If you build ISO 27001 well, you've already done much of the groundwork.

The difference is depth. ISO 27001 lets you decide how to patch based on risk. The Essential Eight tells you exactly how fast, for which applications, at each maturity level.

Essential Eight strategyMain Annex A controlsWhat the Essential Eight adds
Application control8.19, 8.7Only approved programs can run, enforced on workstations first, then servers at higher levels
Patch applications8.8Fixed patching windows and scanning frequencies by application type
Office macro settings8.9, 8.7Macros from the internet blocked; only approved macros allowed at higher levels
User application hardening8.9Specific browser and Office settings, such as blocking web advertisements and Java from the internet
Restrict admin privileges8.2, 5.15, 5.18Privileged accounts kept away from email and web browsing, with regular revalidation
Patch operating systems8.8Fixed patching windows, and removal of unsupported operating systems
Multi-factor authentication8.5, 5.17Where MFA is required, and phishing-resistant methods at higher levels
Regular backups8.13Restores tested, and access to backups restricted so ordinary accounts, and at higher levels most privileged accounts, can’t change or delete them

What each one leaves out

The Essential Eight is deliberately narrow. It says little about governance, risk assessment, supplier security, staff screening, awareness training, incident response, physical security or business continuity, and the model is written for Windows-based, internet-connected networks. A SaaS business running mostly on cloud platforms will find parts of it a poor fit.

ISO 27001 covers all of those areas but never tells you a minimum setting. A badly run ISMS can accept weak patching as a risk and still be certified, as long as the decision is documented and owned. That is why government buyers add the Essential Eight on top: it sets a floor the risk assessment can’t talk you below.

Who asks for which

Who is askingWhat they usually want
Federal agencies under the PSPFMaturity Level Two for their own systems, and often a stated level from suppliers whose systems hold their information
Defence, through DISPThe full Essential Eight at Maturity Level Two for every member; see DISP and ISO 27001
State and local government tendersOften ISO 27001, sometimes with an Essential Eight level alongside
Critical infrastructure entitiesA recognised framework under their risk management program; ISO 27001 and the Essential Eight are both options
Enterprise customers and banksMostly ISO 27001 or SOC 2, plus their own questionnaire
Overseas customersISO 27001 almost always; the Essential Eight is rarely understood outside Australia
Cyber insurersAnswers about MFA, backups, patching and admin rights, often framed in Essential Eight terms

For the legal picture behind these requests, see is ISO 27001 mandatory in Australia?

Which first?

  • A tender or customer wants a certificate: ISO 27001 first, with an Essential Eight target written into your risk treatment plan.
  • A government customer asks for a maturity level: Essential Eight assessment first, then build ISO 27001 around it.
  • You've just had a scare: Essential Eight first. It's the fastest way to cut ransomware and phishing risk.
  • You sell overseas or to enterprise: ISO 27001 first. It is the credential those buyers recognise.
  • You are joining DISP: both, because Defence requires Level Two and expects the governance an ISMS provides.

Doing ISO 27001 first doesn’t mean ignoring the Essential Eight for eight weeks. Quick technical wins such as MFA everywhere, blocked internet macros and tested backups belong in the first weeks of any ISO 27001 project, and they count as evidence for both.

Running both together

The efficient approach is one ISMS with Essential Eight maturity as a measurable objective. The same evidence (patch reports, admin access reviews, backup tests) serves both. We run Essential Eight assessments and ISO 27001 implementations side by side so nothing is done twice.

In practice that means four links between the two:

  • Objectives. State the target maturity level and date as an information security objective under clause 6.2, with an owner and a measure.
  • Risk treatment. Where the Essential Eight requires something your risk assessment wouldn’t, record the requirement as a customer or contractual obligation so it drives the control.
  • Statement of Applicability. Reference the Essential Eight in the justification for the related Annex A controls, so an auditor can see why your patching windows are what they are.
  • Internal audit and management review. Review maturity progress alongside the rest of the ISMS, with exceptions recorded, owned and given expiry dates.

Common mistakes

  • Claiming a maturity level from a policy document. Assessors weigh tested configuration far above written intent.
  • Assuming the ISO 27001 certificate answers an Essential Eight question in a tender. It doesn’t, and evaluators notice.
  • Reporting the best strategy’s level instead of the weakest. Most buyers read your overall maturity as your lowest strategy.
  • Aiming for Level Three on some strategies while others sit at Zero. ASD recommends reaching one level across all eight first.
  • Running the two as separate projects with separate evidence, so every audit and assessment starts from scratch.

Effort for either depends mainly on scope, your current environment and the target level. See what drives the cost of ISO 27001.

Next step

If you supply government, ISO 27001 for government suppliers sets out which agencies ask for what. To work out the right order for your business, book a free 30-minute consultation.

FAQ

Common questions

Is the Essential Eight mandatory?

For non-corporate Commonwealth entities, the Protective Security Policy Framework requires it at Maturity Level Two. For private businesses it isn’t law, but government contracts, state agencies, insurers and larger customers increasingly ask for a maturity level.

Can you be certified to the Essential Eight?

No. There is no Essential Eight certificate. Organisations are assessed against the ASD maturity model and report a maturity level. Be wary of anyone selling an “Essential Eight certification”.

Does ISO 27001 cover the Essential Eight?

ISO 27001 covers the same areas (patching, admin privileges, MFA, backups, application control), but it doesn’t prescribe the specific technical settings each maturity level requires. An ISO 27001 ISMS gives you the place to manage Essential Eight targets, not an automatic maturity level.

Which maturity level should we aim for?

ASD advises choosing a target maturity level that suits your environment and reaching it step by step, at the same level across all eight strategies. Non-corporate Commonwealth entities must reach Maturity Level Two under the PSPF, and many government suppliers aim for the same. Your risk assessment and customer requirements should set the target.

Will our ISO 27001 auditor check our Essential Eight maturity?

Not as such. A certification body audits your ISMS against ISO 27001. If your objectives or risk treatment plan commit you to an Essential Eight target, the auditor will check that you are tracking and working towards it, but they won’t issue a maturity rating. That comes from an Essential Eight assessment.

Is the Essential Eight easier than ISO 27001?

It is narrower, not necessarily easier. The Essential Eight is eight technical strategies with fixed requirements, so a cloud-first business can often reach Level One quickly, but Levels Two and Three usually need real engineering work. ISO 27001 is broader, covering governance, people, suppliers and incidents, and it ends in a certificate.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.