Essential Eight
Patch Applications in the Essential Eight Explained
30 Aug 2026 · Updated 30 Aug 2026
Patch applications is the Essential Eight strategy with the tightest clock. It requires frequent scanning for missing patches and fast patching, measured in days for exposed services, with the shortest windows for internet facing applications and those that handle untrusted content. Unsupported applications must be removed. When a working exploit appears, the most exposed applications must be patched within 48 hours.
Attackers do not wait. When a vulnerability in a widely used application becomes public, mass scanning for it starts almost immediately. This strategy is a race against that, and the timeframes reflect it.
What does patch applications mean in the Essential Eight?
Patch applications is the Essential Eight strategy that requires organisations to find and fix application vulnerabilities quickly. Vendors release updates to close security holes, and unpatched applications, especially those exposed to the internet or handling untrusted content, are among the most common ways in.
The strategy has two moving parts: how often an organisation looks for missing patches, and how fast it applies them. It sets scanning frequencies and patching deadlines that get tighter the more exposed an application is. Internet facing online services are treated most urgently, followed by the applications that process material an attacker can control, web browsers, email clients, office productivity suites and PDF software. It also requires that applications no longer supported by their vendor be removed, because an unsupported application never gets patched and becomes a permanent hole. This is a continuous operational discipline, not a one off, which is what makes it demanding to sustain.
What does patch applications require at each maturity level?
The requirements tighten the scanning cadence and the patch deadlines as the maturity level rises, and extend them to more categories of application. Each level includes the ones below.
| Level | What is required |
|---|---|
| Maturity Level One | Asset discovery at least fortnightly; scan internet facing services at least daily and browsers, office suites, email, PDF and security products at least weekly; patch internet facing services within 48 hours when critical, otherwise within two weeks; patch the high risk application group within two weeks; remove unsupported applications |
| Maturity Level Two | Scan other applications at least fortnightly and patch them within one month |
| Maturity Level Three | Patch the high risk application group within 48 hours when critical or a working exploit exists; remove unsupported other applications |
The structure shows where the urgency lies. Level One protects the exposed surface and the untrusted content applications. Level Two brings the rest of the estate into a managed cycle. Level Three tightens the high risk group to the same 48 hour standard as internet facing services, because a capable attacker moves fast on browser and document vulnerabilities. How the levels map to attacker capability is covered in the Essential Eight maturity levels.
What is the 48 hour patch rule in the Essential Eight?
The 48 hour rule requires the most exposed applications to be patched within 48 hours when a vulnerability is assessed as critical by the vendor, or when a working exploit exists. At Maturity Level One it applies to internet facing online services. At Maturity Level Three it extends to the high risk application group, browsers, office suites, email, PDF and security products.
The detail that matters is when the clock starts. The 48 hours runs from the announcement of a working exploit, or evidence that exploitation is already occurring, whichever comes first. So the trigger is not simply the release of a patch, it is the point at which the vulnerability becomes actively dangerous. That is a demanding standard operationally, because it can require emergency patching outside normal change windows. It is also the right standard, because the gap between an exploit appearing and mass exploitation is often measured in hours, not weeks. Organisations that meet this rule have a fast track patching process ready, not just a monthly cycle.
Why does the Essential Eight prioritise patching internet facing applications?
Internet facing applications are the ones an attacker can reach directly and scan for at scale, so a known vulnerability in an exposed service is frequently exploited within hours of becoming public. The Essential Eight puts the tightest timeframes there because the risk is highest and the window shortest.
Applications that handle untrusted content come next in priority for a related reason: they process material an attacker controls. A web browser renders pages an attacker can craft, an email client opens messages an attacker sends, a PDF reader opens documents an attacker supplies. A vulnerability in any of these can be triggered by getting a user to open the wrong thing. That is why browsers, email clients, office suites and PDF software fall into the high risk group with weekly scanning and short patch windows. The strategy is not asking for everything to be patched instantly, it is asking for the things most likely to be attacked to be patched first, fastest. For an organisation building a patching program to meet an Essential Eight target, Cybernion helps through Essential Eight advisory and assessment.
Frequently asked questions
What does patch applications mean in the Essential Eight?
Patch applications is the Essential Eight strategy that requires organisations to find and fix vulnerabilities in their applications quickly, before attackers exploit them. It sets how often to scan for missing patches and how fast to apply them, with the tightest timeframes for internet facing services and the applications that handle untrusted content, such as web browsers, email clients, office suites and PDF software. Unsupported applications must be removed.
What is the 48 hour patch rule in the Essential Eight?
The 48 hour rule requires the most exposed applications to be patched within 48 hours when a vulnerability is assessed as critical by the vendor or when a working exploit exists. At Maturity Level One this applies to internet facing online services. At Maturity Level Three it also applies to office productivity suites, web browsers, email clients, PDF software and security products. The 48 hour clock runs from the announcement of a working exploit or evidence that exploitation is occurring, whichever is first.
What does patch applications require at each maturity level?
At Maturity Level One, organisations run automated asset discovery at least fortnightly, scan internet facing services at least daily and high risk applications at least weekly, patch internet facing services within 48 hours when critical, and patch the high risk application group within two weeks. Maturity Level Two adds fortnightly scanning and one month patching of other applications. Maturity Level Three tightens the high risk group to 48 hours when critical and requires removal of unsupported applications.
Why does the Essential Eight prioritise patching internet facing applications?
Internet facing applications are the ones attackers can reach directly and scan for at scale, so a known vulnerability in an exposed service is often exploited within hours of becoming public. The Essential Eight sets the tightest timeframes there because that is where the risk is highest and the window shortest. Applications that handle untrusted content, such as browsers and email clients, come next because they process material an attacker controls.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Essential Eight maturity model, Australian Signals Directorate, 27 November 2023
- Essential Eight maturity model FAQ, Australian Signals Directorate, 28 October 2024
- Essential Eight assessment process guide, Australian Signals Directorate, 2 October 2024
Last updated: 30 August, 2026
