Patch applications, and the clock that starts at release.
Patch applications at Maturity Level One: scans, two windows and removals
Maturity Level One of patch applications asks for automated asset discovery at least fortnightly, a scanner with a current database, daily scans of online services, weekly scans of common applications, patches within 48 hours or two weeks, and removal of unsupported software.
If unknown assets are identified as part of asset discovery scans, they should be immediately investigated and treated as suspicious until confirmed otherwise.
What Maturity Level One requires for applications
Maturity Level One is set against actors using commodity tradecraft, such as a public exploit against an online service that was never patched. The patch applications strategy answers that with a fixed cadence of discovery, scanning and patching, and with removal of software its vendor no longer supports.
Each window applies to patches, updates or other vendor mitigations and runs from the vendor's release. For office productivity suites, web browsers and their extensions, email clients, PDF software and security products, the window at this level is two weeks whatever the severity.
| Requirement | Scope | Timeframe |
|---|---|---|
| Automated asset discovery | Assets for later vulnerability scanning | At least fortnightly |
| Vulnerability scanner | Scanner with an up-to-date vulnerability database | Every scan |
| Scan for missing patches | Online services | At least daily |
| Scan for missing patches | Office suites, browsers and extensions, email clients, PDF software, security products | At least weekly |
| Patch online services | Vendor rates critical, or a working exploit exists | Within 48 hours of release |
| Patch online services | Vendor rates non-critical and no working exploit exists | Within two weeks of release |
| Patch common applications | Office suites, browsers and extensions, email clients, PDF software, security products | Within two weeks of release |
| Remove unsupported software | Online services, the common application group and Adobe Flash Player | Once vendor support ends |
Automated asset discovery
- Scope
- Assets for later vulnerability scanning
- Timeframe
- At least fortnightly
Vulnerability scanner
- Scope
- Scanner with an up-to-date vulnerability database
- Timeframe
- Every scan
Scan for missing patches
- Scope
- Online services
- Timeframe
- At least daily
Scan for missing patches
- Scope
- Office suites, browsers and extensions, email clients, PDF software, security products
- Timeframe
- At least weekly
Patch online services
- Scope
- Vendor rates critical, or a working exploit exists
- Timeframe
- Within 48 hours of release
Patch online services
- Scope
- Vendor rates non-critical and no working exploit exists
- Timeframe
- Within two weeks of release
Patch common applications
- Scope
- Office suites, browsers and extensions, email clients, PDF software, security products
- Timeframe
- Within two weeks of release
Remove unsupported software
- Scope
- Online services, the common application group and Adobe Flash Player
- Timeframe
- Once vendor support ends
What an assessor asks to see
ASD's assessment process guide grades evidence in four levels. Testing a control with a simulated activity is excellent, reviewing live configuration is good, reports or screenshots are fair, and a policy or verbal statement is poor. Scripts and tools rank ahead of interviews because they cover many machines at once.
To judge criticality and whether a working exploit exists, assessors use sources such as the SANS Internet Storm Centre, the Microsoft Security Response Centre and the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities Catalog.
- A demonstration of asset discovery, plus earlier discovery scans with their dates and scope
- When the scanner's database was last updated, ideally within 24 hours of the scan
- Earlier scans of online services, checked against the online services known to be in use
- Weekly scan scope, checked against the applications that should have been scanned
- Installed versions and install dates, compared with each vendor's release date
- Versions in use, checked against the vendor's list of supported versions
What an assessor asks to see
- Hotfix KB4577586 applied, to show Adobe Flash Player has been removed
- Documented exceptions with compensating controls, approved by an appropriate authority
Where organisations fall short
If one control in the strategy is assessed as ineffective, the organisation cannot claim Maturity Level One for patch applications. Each requirement is a separate control, so a gap in any one of them counts against the result.
- Online services left off the scan list, including ones forgotten or installed without the owner's knowledge
- A scanner database not updated close to the time of the scan
- Browser extensions or PDF software missing from the weekly scan scope
- Vendor mitigations such as configuration changes, which a scanner may not detect
- Adobe Flash Player installed manually, which hotfix KB4577586 does not remove
- Unknown assets found by discovery scans and not investigated as suspicious
Where organisations fall short
- Risk accepted for a missed control with no compensating controls
- Exceptions approved with no review date, or for longer than one year
Meeting it in Microsoft 365 and Azure
In a Microsoft 365 tenant and an Azure estate, each requirement maps to a product that holds the setting or the record. The assessor still asks for a demonstration and dated history, so keep the exports from each scan and patch cycle.
ASD notes that Windows Server Update Services can report a patch as deployed without showing whether it applied or the machine rebooted. Evidence of a patch rests on installed versions and install dates compared with the vendor's release date. On Windows endpoints, PowerShell can list applications with registered uninstall functionality, read together with Programs and Features.
| Requirement | Microsoft 365 and Azure | Record to keep |
|---|---|---|
| Asset discovery, fortnightly | Microsoft Defender for Endpoint device discovery, Microsoft Intune device inventory, Azure Arc for servers outside Azure | Dated discovery results and their scope |
| Scanner with a current database | Microsoft Defender Vulnerability Management | Database update time against scan time |
| Online services, daily scan | Microsoft Defender for Cloud for workloads in Azure, with a network scanner for internet-facing services | Daily scan history matched to the online services list |
| Common applications, weekly scan | Defender Vulnerability Management software inventory covering Microsoft 365 Apps for enterprise and Microsoft Edge | Weekly scan history and its application scope |
| Patching within the windows | Microsoft Intune and Office cloud policy service update settings for Microsoft 365 Apps for enterprise and Microsoft Edge | Installed versions and dates against vendor release dates |
| Removal of unsupported software | Microsoft Intune uninstall assignments | Versions in use against supported versions |
| Exceptions | A documented exception register | Scope, compensating controls, approver and review date |
Asset discovery, fortnightly
- Microsoft 365 and Azure
- Microsoft Defender for Endpoint device discovery, Microsoft Intune device inventory, Azure Arc for servers outside Azure
- Record to keep
- Dated discovery results and their scope
Scanner with a current database
- Microsoft 365 and Azure
- Microsoft Defender Vulnerability Management
- Record to keep
- Database update time against scan time
Online services, daily scan
- Microsoft 365 and Azure
- Microsoft Defender for Cloud for workloads in Azure, with a network scanner for internet-facing services
- Record to keep
- Daily scan history matched to the online services list
Common applications, weekly scan
- Microsoft 365 and Azure
- Defender Vulnerability Management software inventory covering Microsoft 365 Apps for enterprise and Microsoft Edge
- Record to keep
- Weekly scan history and its application scope
Patching within the windows
- Microsoft 365 and Azure
- Microsoft Intune and Office cloud policy service update settings for Microsoft 365 Apps for enterprise and Microsoft Edge
- Record to keep
- Installed versions and dates against vendor release dates
Removal of unsupported software
- Microsoft 365 and Azure
- Microsoft Intune uninstall assignments
- Record to keep
- Versions in use against supported versions
Exceptions
- Microsoft 365 and Azure
- A documented exception register
- Record to keep
- Scope, compensating controls, approver and review date
Where it sits on the ladder
Maturity Level Zero records that one or more Maturity Level One requirements are not met. ASD expects an organisation to be assessed at Maturity Level One before an assessment against Maturity Level Two begins, and to reach the same level across all eight strategies before moving up.
Maturity Level Two keeps every Maturity Level One requirement and adds fortnightly scanning and a one-month patch window for all other applications. Maturity Level Three brings critical or exploited cases in the common application group to 48 hours and removes every other unsupported application.
Dates
When it was written, and checked.
.
Questions, answered.
Does patch applications at Maturity Level One cover every application?
It covers online services and a named group: office productivity suites, web browsers and their extensions, email clients, PDF software and security products. Other applications come in at Maturity Level Two, with fortnightly scanning and a one-month patch window.
When does the 48-hour window apply at Maturity Level One?
It applies to online services when the vendor rates the vulnerability critical or a working exploit exists. Other online service patches have two weeks. The common application group has two weeks from release at this level, whatever the severity.
Can we hold an exception to a patching requirement?
Yes, if it is documented and approved by an appropriate authority, with compensating controls, a scope, a justification and a review date. ASD's guidance says exceptions should not be approved beyond one year. Accepting the risk with no compensating controls does not meet the requirement.
How often must automated asset discovery run?
At least fortnightly. ASD allows discovery to run on the same daily or weekly schedule as vulnerability scans so both happen together. Unknown assets found by a discovery scan should be investigated straight away and treated as suspicious until confirmed otherwise.
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

