# Essential Eight patching timeframes by maturity level

URL: https://essentialeightmaturity.com/guides/patching-timeframes-by-maturity-level/
Read date: 18 Nov 2026

> At every Essential Eight level, critical or exploited vulnerabilities in online services must be patched within 48 hours, and others within two weeks. Maturity Level Two adds a one month window for all other applications, scanned at least fortnightly. Level Three brings 48 hours to office suites, browsers, email clients, PDF software, security products and, for operating systems, to workstations and internal servers.

## What are the timeframes for patching applications?

At Level One, assets are discovered automatically at least fortnightly. A vulnerability scanner checks online services daily, and office suites, web browsers and their extensions, email clients, PDF software and security products weekly. Critical or exploited vulnerabilities in online services are patched within 48 hours, and others within two weeks. The desktop applications just listed are patched within two weeks. Unsupported versions of online services and those applications are removed.

Level Two scans all other applications at least fortnightly and patches them within one month of release. Level Three adds 48 hours for critical or exploited vulnerabilities in the desktop applications listed above, with two weeks otherwise, and requires unsupported applications of every kind to be removed, not only the listed categories. The page for [Patch applications](https://essentialeightmaturity.com/strategies/patch-applications/) shows the levels with the platforms that evidence the strategy.

## What are the timeframes for patching operating systems?

At Level One, assets are discovered at least fortnightly. Internet-facing servers and network devices are scanned daily, and workstations and other servers and devices fortnightly. Internet-facing systems are patched within 48 hours when critical or exploited, and within two weeks otherwise. Other systems are patched within one month. Unsupported operating systems are replaced.

Level Two adds nothing for operating systems in the November 2023 model, and the assessment guide says no extra assessment is needed. Level Three requires workstations, non-internet-facing servers and non-internet-facing network devices to be patched within 48 hours when critical or exploited (one month otherwise), scans drivers and firmware fortnightly under the same 48 hour or one month rule, and allows only the latest or previous release of an operating system. See [Patch operating systems](https://essentialeightmaturity.com/strategies/patch-operating-systems/).

## When does the 48 hours start?

ASD's FAQ says the 48 hours run from the announcement of a working exploit or from exploitation already occurring, whichever comes first. A vulnerability counts when a vendor rates it critical or a working exploit exists. To find out whether an exploit exists, ASD points to vendors, ASD itself, news outlets, security researchers and the US Known Exploited Vulnerabilities Catalog. If a vendor does not rate criticality, ASD suggests using the type of vulnerability and its CVSS score as a guide.

An online service is any service directly accessible over the internet, including one behind a perimeter firewall. ASD's examples are a web portal, a cloud service and a network device such as a firewall or VPN concentrator. ASD encourages organisations that cannot patch online services quickly to move them to mature cloud providers.

## What did ASD's recent patch alerts show?

Two ASD alerts in the last three months were about exactly this class of device. On 28 September 2026 ASD issued an alert on critical vulnerabilities in Citrix NetScaler ADC and NetScaler Gateway, under active exploitation, and told organisations to apply a high-priority patch. On 23 October 2026 it alerted that Fortinet had announced critical vulnerabilities and security updates to apply as a priority. A gateway or firewall of that kind is the sort of online service the Level One 48 hour rule is written for.

Both are in the [news log](https://essentialeightmaturity.com/news/). The practical test for an organisation is whether the scan record shows the device, the date the fix was released and the date it was applied, within the window.

## How does an assessor test patching?

The guide's preferred evidence is a demonstration. For scanning the assessor asks to see a vulnerability scan, the date the scanner's database was last updated (ideally within 24 hours of the scan) and past scans with dates and scope, then checks that the scanned list matches the services and applications actually in use. For timeframes the assessor uses a network-based scanner to list versions and install dates, and compares them with vendor release dates. The guide notes that a scanner may not find missing vendor mitigations such as configuration changes.

Free tools named include ASD's Essential Eight Maturity Verification Tool, Nessus Essentials, Nexpose Community Edition, OpenVAS and Qualys Community Edition. Where a scanner cannot be used, the assessor can ask for screenshots of versions or a PowerShell listing of installed applications, checked against Programs and Features.

## What can platforms show for patching?

[Vanta](https://essentialeightmaturity.com/platforms/vanta/) says its Essential Eight page tracks OS and application patching to meet Essential Eight requirements, and lists patching integrations including Automox, NinjaOne, ManageEngine, Microsoft Intune and Addigy. [Drata](https://essentialeightmaturity.com/platforms/drata/) lists Intune and NinjaOne, and its help centre treats proof that critical patches were installed in the required timeframe as manual evidence. [Scrut Automation](https://essentialeightmaturity.com/platforms/scrut/) lists Intune, NinjaOne and ManageEngine, and [Scytale](https://essentialeightmaturity.com/platforms/scytale/) lists Intune, NinjaOne, JumpCloud and Jamf Pro. None found for patching integrations at [6clicks](https://essentialeightmaturity.com/platforms/6clicks/), [Secureframe](https://essentialeightmaturity.com/platforms/secureframe/) and [Avertro](https://essentialeightmaturity.com/platforms/avertro/), and [Huntsman Security](https://essentialeightmaturity.com/platforms/huntsman-security/) publishes no integrations page.

A device list from a management tool shows what is installed, not the 48 hour clock. In the [keep Level Two between assessments](https://essentialeightmaturity.com/situations/keep-ml2-continuously/) ranking, where monitoring carries 35 percent, the top three are Vanta at 6.00, Drata at 5.75 and 6clicks at 5.40.

## Frequently asked questions

### Do I have 48 hours to patch from when working exploits are announced or when exploitation starts occurring?

ASD says the 48 hours run from whichever comes first: the announcement of a working exploit, or exploitation already occurring. The requirement applies to vulnerabilities that a vendor rates critical or for which a working exploit exists.

## Keep reading

- [Exceptions and compensating controls in an Essential Eight assessment](https://essentialeightmaturity.com/guides/exceptions-and-compensating-controls/)
- [Application control at Essential Eight Maturity Level Two](https://essentialeightmaturity.com/guides/application-control-at-maturity-level-two/)
- [What assessors check at Essential Eight Maturity Level Two](https://essentialeightmaturity.com/guides/what-assessors-check-at-maturity-level-two/)
- [Essential Eight checklist for a first assessment](https://essentialeightmaturity.com/guides/essential-eight-checklist-for-a-first-assessment/)
- [Maturity Evidence Matrix](https://essentialeightmaturity.com/maturity-evidence-matrix/)
- [Maturity self-assessment](https://essentialeightmaturity.com/)

## Sources

- [ASD, Essential Eight maturity model (November 2023), Internet Archive snapshot of cyber.gov.au](https://web.archive.org/web/20261006110100/https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/essential-eight/essential-eight-maturity-model), read 18 Nov 2026
- [ASD, Essential Eight maturity model FAQ, Internet Archive snapshot of cyber.gov.au](https://web.archive.org/web/20261117040007/https://www.cyber.gov.au/publication/essential-eight-maturity-model-faq), read 18 Nov 2026
- [ASD, Essential Eight assessment process guide (October 2024), Internet Archive snapshot of cyber.gov.au](https://web.archive.org/web/20261022012817/https://www.cyber.gov.au/publication/essential-eight-assessment-process-guide), read 18 Nov 2026
- [ASD, Critical vulnerabilities in Citrix NetScaler ADC and NetScaler Gateway products (28 Sep 2026), Internet Archive snapshot of cyber.gov.au](https://web.archive.org/web/20261024034700/https://www.cyber.gov.au/alert/critical-vulnerabilities-in-citrix-netscaler-adc-and-citrix-netscaler-gateway-products), read 18 Nov 2026
- [ASD, Critical vulnerabilities in Fortinet products (23 Oct 2026), Internet Archive snapshot of cyber.gov.au](https://web.archive.org/web/20261024034700/https://www.cyber.gov.au/alert/critical-vulnerabilities-in-fortinet-products), read 18 Nov 2026
- [Vanta, Essential Eight product page](https://www.vanta.com/products/essential-eight), read 18 Nov 2026
- [Drata help centre, example evidence for not monitored controls, Essential Eight](https://help.drata.com/en/articles/13112197-example-evidence-for-not-monitored-controls-essential-eight), read 18 Nov 2026

Last reviewed 18 Nov 2026
