Quick answer
Essential Eight Maturity Level One (ML1) is the first level of ASD's Essential Eight Maturity Model. It is designed to stop opportunistic attackers who use commodity tools and publicly available exploits against any vulnerable target. ML1 sets baseline requirements for all eight strategies, including timely patching of internet-facing systems, MFA on internet-facing services and tested backups.
On this page
What ML1 Requires
ML1 targets attackers who are not after you specifically. They scan for known vulnerabilities, send commodity malware and try stolen passwords against whoever responds. In summary, ML1 expects the following. Check the exact wording against ASD's current published model.
- Application control: on workstations, execution is restricted to an approved set of programs in the locations attackers most often use, such as user profile and temporary folders.
- Patch applications: assets are discovered and scanned for vulnerabilities on a regular schedule. Patches for internet-facing services are applied quickly, within days where a working exploit exists, and common applications such as browsers, email clients, office suites and PDF software are patched within a short window. Unsupported applications are removed.
- Microsoft Office macros: macros are disabled for users without a business need, macros from the internet are blocked, and users cannot change macro security settings.
- User application hardening: browsers do not run web advertisements or Java from the internet, Internet Explorer 11 is disabled or removed, and users cannot change browser security settings.
- Restrict administrative privileges: privileged access is validated when first requested, privileged accounts cannot browse the web or read email, and privileged and unprivileged activity happen in separate environments.
- Patch operating systems: internet-facing servers and network devices are patched quickly, workstations and internal servers within a longer window, and unsupported operating systems are replaced.
- Multi-factor authentication: MFA protects users of internet-facing services and online services that hold sensitive or non-public organisational data.
- Regular backups: important data, software and settings are backed up and retained according to business need, restoration is tested, and ordinary users cannot read other users' backups or modify and delete backups.
Who Should Target It
ML1 is the minimum sensible baseline for any internet-connected organisation. It is the level named in the SOCI Act risk management program rules when an entity chooses the Essential Eight as its cyber framework, and a common first milestone for organisations working towards ML2.
How to Test for It
- Run an external discovery exercise and compare it with your asset register. Unknown internet-facing systems are the most common reason ML1 patching fails. See attack surface management.
- Check internet-facing services against the known exploited vulnerabilities list to confirm exploitable flaws are patched within the required time.
- Attempt to run an unapproved executable from a user profile or temporary folder on a sample of workstations.
- Open a macro-enabled document downloaded from the internet and confirm it is blocked.
- Try each internet-facing login without a second factor, including legacy protocols and alternate endpoints.
- From a standard account, attempt to reach, change or delete backups.
Hands-on checks like these are stronger evidence than configuration screenshots. Our guide to Essential Eight penetration testing explains how they fit into a test.
How to Reach and Keep ML1
Start with an accurate asset inventory, because patching and MFA requirements depend on knowing what is exposed. Automate patching where possible, remove unsupported software, enforce MFA at the identity provider rather than per application, and record and review every exception. A maturity level assessment gives an evidence-based starting point.
Regulatory and Framework Context
ML1 is the first level of the Essential Eight Maturity Model. For a broader introduction to the strategies and who must comply, see ASD Essential Eight explained. ASD revises the model periodically, so confirm exact timeframes and scope against the current version on cyber.gov.au.
Latest intel on this topic
- ASD Essentials: evolving our approach to cyber security resilienceASD's ACSC · 7 October 2026
- Consultation on evolution of Essential EightASD's ACSC · 2 September 2026
Updated hourly from the daily briefing.
Common questions
Is ML1 enough for a small business?
For many small organisations ML1 is a sensible first target, because it defeats the untargeted attacks that cause most incidents. If you hold sensitive data, support critical services or face targeted threats, plan to move on to ML2.
Does ML1 apply to servers?
Some ML1 requirements apply to internet-facing servers and network devices, such as patching timeframes. Others, such as application control, apply to workstations at ML1 and extend to servers at higher levels.
What is the most common reason organisations miss ML1?
Incomplete coverage. A control that is applied to most systems but not all, or patching that misses internet-facing devices nobody knew about, is enough to leave a strategy at ML0.
Change log
- 13 November 2026First published.