Skip to content
Rootways CIM Pro flaw CVE-2026-130583 lets attackers read Magento 2 store keys
Black Shard

Loading

    Essential Eight

    The Essential Eight, strategy by strategy

    The Essential Eight is ASD's set of eight mitigation strategies, the most effective of its Strategies to mitigate cyber security incidents. Its maturity model sets requirements for each strategy at three levels, and organisations should reach one level across all eight before moving higher.

    What the Essential Eight requires

    The eight strategies are patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups. ASD designed them to protect internet-connected information technology networks. Enterprise mobility and operational technology networks may need other mitigation strategies.

    The maturity model defines four levels, from Maturity Level Zero to Maturity Level Three. Level Zero signals weaknesses in the overall cyber security posture. Each level above it counters a step up in adversary tradecraft and targeting, from commodity tools used against any victim to adaptive actors who steal authentication tokens and evade detection.

    Organisations choose a target level suited to their environment and implement each level in turn until they reach it. The model asks for a risk-based approach. Exceptions are kept few and narrow, backed by compensating controls, documented, approved through an appropriate process and reviewed on a regular basis.

    • Maturity Level One: configuration across all eight strategies, such as dedicated admin accounts and application control on workstations
    • Maturity Level Two: wider coverage, plus protected event logs, timely analysis, incident reporting and an enacted response plan
    • Maturity Level Three: phishing-resistant MFA everywhere, just-in-time administration, driver and firmware patching, and stricter macro rules

    What an assessor asks to see

    ASD directs assessments to its Essential Eight assessment process guide. An assessor rates each strategy separately against the target level, so one strategy at Maturity Level Zero holds the overall result at Level Zero in practice.

    The assessor asks for dated artefacts behind each mitigation.

    • Application control rulesets and what they block, with allowed and blocked event logs from Maturity Level Two
    • Patch reports showing the age of the oldest unpatched exploitable flaw
    • Multi-factor authentication coverage by account, and whether each method is phishing-resistant
    • A privileged-account register showing who holds administrative privilege and when it was last revalidated
    • Configuration exports for macro, browser and Office hardening settings
    • Restore-test records from disaster recovery exercises
    What an assessor asks to see
    • Documented exceptions with their approval, compensating controls and review history

    Where organisations fall short

    Application control is the strategy most often found at Maturity Level Zero, because it is the one most often deferred. Switched on in enforce mode without an audit period, it blocks the macros and utilities that teams rely on.

    The logging and incident layer is what separates a Maturity Level One estate from a Maturity Level Two estate. Level One controls are configuration. The Level Two layer is an operating discipline that has to be running, with records, before it can be evidenced.

    • Strategies rated at different levels, which holds the overall result at the lowest one
    • Admin rights that accumulate as roles change and are never revalidated
    • Patch cadences that slip past the model's timeframes
    • Temporary exceptions that become permanent without documented approval or review
    • Backups never tested by a restore, or held where a compromised account can delete them
    • Multi-factor authentication missing from remote access or administrative portals

    How to meet it in Microsoft 365 and Azure

    Most of the evidence sits in the Microsoft 365 tenant, Microsoft Entra ID and the endpoint management tooling. Each strategy maps to products in the tenant and the Azure estate.

    From Maturity Level Two, event logs go to a central store protected from modification and deletion. Microsoft Sentinel, Log Analytics and Microsoft Defender XDR collect authentication, privileged access, application control and PowerShell events for timely analysis, and the incident response plan is enacted when an incident is identified.

    • Application control

      Microsoft 365 and Azure controls
      App Control for Business, Windows Defender Application Control or AppLocker, deployed through Microsoft Intune
      Record to keep
      Ruleset export, annual validation, allowed and blocked events in Microsoft Sentinel
    • Patch applications

      Microsoft 365 and Azure controls
      Microsoft Defender Vulnerability Management, Microsoft Intune, Microsoft 365 Apps for enterprise
      Record to keep
      Vulnerability scanner results and patch reports against the model's timeframes
    • Patch operating systems

      Microsoft 365 and Azure controls
      Windows Autopatch, Windows Update for Business, Azure Update Manager, Azure Arc
      Record to keep
      Patch compliance reports for workstations and servers
    • Configure Microsoft Office macro settings

      Microsoft 365 and Azure controls
      Office cloud policy service, Group Policy, Microsoft Intune
      Record to keep
      Macro policy export and the trusted publisher list
    • User application hardening

      Microsoft 365 and Azure controls
      Microsoft Edge policies, Attack Surface Reduction rules, PowerShell in Constrained Language Mode
      Record to keep
      Hardening settings export and central PowerShell logs
    • Restrict administrative privileges

      Microsoft 365 and Azure controls
      Entra ID Privileged Identity Management, Entra ID Access Reviews, Windows LAPS, Azure Bastion, Credential Guard
      Record to keep
      Privileged-account register and revalidation history
    • Multi-factor authentication

      Microsoft 365 and Azure controls
      Entra ID Conditional Access, Windows Hello for Business, FIDO2 security keys, Microsoft Authenticator
      Record to keep
      Conditional Access policy export and sign-in logs
    • Regular backups

      Microsoft 365 and Azure controls
      Microsoft 365 Backup, Azure Backup, Azure Backup immutable vaults
      Record to keep
      Restore-test records and backup access permissions

    Where each strategy sits

    ASD designed the eight strategies to complement each other, so its guidance is to bring all eight to the same maturity level before moving any of them higher. Four strategies stop attacks landing, three limit how far an attacker gets, and one recovers the business afterwards.

    The Essential Eight is a minimum set of preventative measures and will not mitigate every cyber threat. ASD points organisations to the remainder of its Strategies to mitigate cyber security incidents and to the Information security manual for further controls.

    • Application control

      Role
      Prevent
      Page
      /standards/essential-eight/application-control
    • Patch applications

      Role
      Prevent
      Page
      /standards/essential-eight/patch-applications
    • Configure Microsoft Office macro settings

      Role
      Prevent
      Page
      /standards/essential-eight/configure-microsoft-office-macro-settings
    • User application hardening

      Role
      Prevent
      Page
      /standards/essential-eight/user-application-hardening
    • Restrict administrative privileges

      Role
      Limit
      Page
      /standards/essential-eight/restrict-administrative-privileges
    • Patch operating systems

      Role
      Limit
      Page
      /standards/essential-eight/patch-operating-systems
    • Multi-factor authentication

      Role
      Limit
      Page
      /standards/essential-eight/multi-factor-authentication
    • Regular backups

      Role
      Recover
      Page
      /standards/essential-eight/regular-backups

    Questions, answered.

    What are the Essential Eight strategies?

    Patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups. ASD rates them the most effective of its Strategies to mitigate cyber security incidents.

    Does an independent party need to assess our maturity level?

    ASD sets no requirement for an independent party to sign off an Essential Eight implementation. An independent assessment may be needed when a government directive or policy, a regulatory authority or a contract calls for one. A maturity level stands on the evidence behind it.

    Which maturity level should we target?

    The level you are being asked for. Maturity Level One is the common baseline for small and mid-sized businesses, and contracts in government supply chains increasingly specify Maturity Level Two. ASD also asks organisations to weigh their desirability to malicious actors and the consequences of an incident.

    Is the Essential Eight still current now ASD Essentials exists?

    ASD launched ASD Essentials as the successor to the Essential Eight, and both frameworks are live through the transition. Tenders, insurers and supplier questionnaires still ask for an Essential Eight maturity level, and ASD maps every strategy to at least one Essentials principle.

    Provenance

    Sources, and when they were read.

    Every source was read 15 Nov 2026.

    Being measured against Essential Eight? Scope the work.