Patch applications, and the clock that starts at release.
Essential Eight patch applications at Maturity Level Two
At Maturity Level Two, Patch applications extends scanning and patching past the commonly targeted applications. Every remaining application is scanned for missing patches at least fortnightly and patched within one month of release, on top of the Maturity Level One requirements.
Patches, updates or other vendor mitigations for vulnerabilities in applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within one month of release.
What Maturity Level Two requires
Maturity Level Two keeps every Maturity Level One requirement for patching applications and adds two for the remaining applications. A vulnerability scan for missing patches runs on them at least once a fortnight, and vendor patches, updates or other mitigations for them are applied within one month of their release.
The base layer carries over unchanged. An automated asset discovery method runs at least fortnightly so new assets reach the scanner, and the scanner works from a current vulnerability database. Unsupported online services are removed, as are unsupported office suites, browsers and extensions, email clients, PDF software, Adobe Flash Player and security products.
| Application group | Scan at least | Patch within |
|---|---|---|
| Online services | Daily | 48 hours when critical or a working exploit exists, otherwise two weeks |
| Office suites, browsers and extensions, email clients, PDF software, security products | Weekly | Two weeks |
| All other applications (new at this level) | Fortnightly | One month |
Online services
- Scan at least
- Daily
- Patch within
- 48 hours when critical or a working exploit exists, otherwise two weeks
Office suites, browsers and extensions, email clients, PDF software, security products
- Scan at least
- Weekly
- Patch within
- Two weeks
All other applications (new at this level)
- Scan at least
- Fortnightly
- Patch within
- One month
What an assessor asks to see
ASD's assessment process guide tells assessors to apply the Maturity Level One method to the wider set of applications, using the fortnightly and one-month timeframes. An assessment at this level focuses on the change from Maturity Level One.
The guide ranks evidence by quality. Testing a control is excellent, reviewing live configuration through the system's interface is good, reports or screenshots are fair, and a policy or verbal statement is poor. Scripts and tools rate above interviews and screenshots because they cover many machines and find issues people overlook.
- A demonstration of automated asset discovery, with dated earlier scans and their scope
- The date the vulnerability database last updated, ideally within 24 hours of the scan
- Earlier vulnerability scan results, checked for date, time and scope
- Proof that the scanned application list includes every application that should be scanned
- Installed versions and install dates, compared with each vendor's release dates
- Documented and approved exceptions, with their compensating controls
Where organisations fall short
One control assessed as ineffective means the organisation cannot claim Maturity Level Two for the strategy, and the target level for the system cannot be claimed either. Risk acceptance does not justify leaving a control out without adequate compensating controls.
- The scanner covers the commonly targeted applications and leaves the remaining applications unscanned
- The application list comes only from registered uninstall entries, which miss some installed applications
- The vulnerability database is out of date when the scan runs
- Missing vendor mitigations such as configuration changes go undetected, as scanners may not flag them
- Unknown assets found by discovery scans are left uninvestigated
- Exceptions lack documented approval, compensating controls or a review date, or run past one year
Meeting it in Microsoft 365 and Azure
In a Microsoft 365 tenant, Microsoft Defender for Endpoint and Microsoft Defender Vulnerability Management can provide the automated asset discovery and vulnerability scanning the requirement calls for across onboarded Windows 11 devices and Windows Server. Microsoft Intune deploys application updates to managed devices.
In an Azure estate, Microsoft Defender for Cloud extends vulnerability assessment to Azure virtual machines, and Azure Arc brings servers outside Azure under the same management. Log Analytics or Microsoft Sentinel can retain scan and deployment history, so dated evidence is available when an assessor asks for it.
| Requirement | Microsoft 365 and Azure capability | Evidence an assessor can review |
|---|---|---|
| Fortnightly automated asset discovery | Microsoft Defender for Endpoint device discovery | Dated device inventory showing scope |
| Current vulnerability database | Microsoft Defender Vulnerability Management | Date of the last vulnerability database update |
| Fortnightly scan of other applications | Defender Vulnerability Management software inventory | Findings by application and version, with scan dates |
| One-month patch window | Microsoft Intune application deployment | Installed versions and install dates against vendor release dates |
| Azure and on-premises servers | Microsoft Defender for Cloud and Azure Arc | Dated server vulnerability findings |
| Exceptions | Documented exception register | Approval, compensating controls and next review date |
Fortnightly automated asset discovery
- Microsoft 365 and Azure capability
- Microsoft Defender for Endpoint device discovery
- Evidence an assessor can review
- Dated device inventory showing scope
Current vulnerability database
- Microsoft 365 and Azure capability
- Microsoft Defender Vulnerability Management
- Evidence an assessor can review
- Date of the last vulnerability database update
Fortnightly scan of other applications
- Microsoft 365 and Azure capability
- Defender Vulnerability Management software inventory
- Evidence an assessor can review
- Findings by application and version, with scan dates
One-month patch window
- Microsoft 365 and Azure capability
- Microsoft Intune application deployment
- Evidence an assessor can review
- Installed versions and install dates against vendor release dates
Azure and on-premises servers
- Microsoft 365 and Azure capability
- Microsoft Defender for Cloud and Azure Arc
- Evidence an assessor can review
- Dated server vulnerability findings
Exceptions
- Microsoft 365 and Azure capability
- Documented exception register
- Evidence an assessor can review
- Approval, compensating controls and next review date
Where it sits on the maturity ladder
Maturity Level One sets the base: fortnightly asset discovery, a current scanner, daily scans of online services, weekly scans of the commonly targeted applications, the 48-hour and two-week windows, and removal of unsupported software in those groups. Maturity Level Two adds the remaining applications.
Maturity Level Three shortens the window for office suites, browsers and extensions, email clients, PDF software and security products to 48 hours when a flaw is critical or exploited, and two weeks otherwise. It also requires removal of any other application its vendor no longer supports.
ASD advises reaching the same maturity level across all eight strategies before moving higher. ASD launched ASD Essentials on 15 October 2026 as the successor framework, and the Essential Eight remains live through the transition.
Dates
When it was written, and checked.
.
Questions, answered.
What changes between Maturity Level One and Two for patching applications?
Two requirements are added. Applications outside online services, office productivity suites, web browsers and their extensions, email clients, PDF software and security products are scanned for missing patches at least fortnightly, and their patches are applied within one month of release. Every Maturity Level One requirement still applies.
Which applications fall under the one-month patch window?
Every application outside the named groups: online services, office productivity suites, web browsers and their extensions, email clients, PDF software and security products. Those groups keep their own shorter timeframes.
Can we reach Maturity Level Two with an application we cannot patch?
Yes, through a formal exception. ASD expects it to be documented and approved by an appropriate authority, with its scope, justification and compensating controls, and reconsidered within one year. Risk acceptance without compensating controls does not meet the requirement.
Do we need Maturity Level One before a Level Two assessment?
ASD's assessment guide says an organisation without an assessment showing Maturity Level One should not begin a Maturity Level Two assessment. ASD also advises reaching the same level across all eight strategies before targeting the next.
Provenance
Sources, and when they were read.
Every source was read 15 Nov 2026.
- 1ASD, Essential Eight maturity modelcyber.gov.au. CC BY 4.0.
- 2ASD, Essential Eight assessment process guidecyber.gov.au. CC BY 4.0.
- 3Black Shard, Essential Eight assessment

