Essential Eight
Patch Operating Systems in the Essential Eight Explained
30 Aug 2026 · Updated 30 Aug 2026
Patch operating systems keeps the operating system layer current across servers, workstations and network devices, and requires unsupported operating systems to be replaced. Timeframes are tiered by internet exposure, tightest for internet facing servers and network devices. For this strategy Maturity Level Two matches Level One, and the real step up, drivers, firmware and faster workstation patching, comes at Level Three.
Applications are one attack surface, the operating system underneath is another. This strategy covers the layer that everything else runs on, and an unpatched or unsupported operating system undermines every control above it.
What does patch operating systems mean in the Essential Eight?
Patch operating systems is the Essential Eight strategy that keeps the operating systems on servers, workstations and network devices up to date, and requires operating systems no longer supported by their vendor to be replaced. It is the companion to patch applications, covering the operating system layer rather than the applications on top.
Like application patching, it sets scanning frequencies and patch timeframes, tiered by how exposed a system is. Internet facing servers and network devices get the shortest windows, because they are directly reachable and constantly scanned by attackers. Workstations and non internet facing systems get a slightly longer window. The requirement to replace unsupported operating systems is as important as the patching itself: an operating system past its support date will never receive fixes again, so it is a permanent, growing vulnerability that no amount of other controls fully compensates for. Old, unsupported systems running well past their life are one of the most common findings in government audits.
What does patch operating systems require at each maturity level?
The scanning cadence and patch windows are set at Level One, hold steady at Level Two, and tighten at Level Three with drivers and firmware added. Each level includes the ones below.
| Level | What is required |
|---|---|
| Maturity Level One | Asset discovery at least fortnightly; scan internet facing server and network device operating systems at least daily and other operating systems at least fortnightly; patch internet facing operating systems within 48 hours when critical, otherwise within two weeks; patch workstations and non internet facing systems within one month; replace unsupported operating systems |
| Maturity Level Two | Same requirements as Maturity Level One |
| Maturity Level Three | Scan drivers and firmware at least fortnightly; patch workstations and non internet facing systems within 48 hours when critical; patch drivers and firmware within 48 hours when critical and one month otherwise; use the latest or previous release of operating systems |
The pattern is unusual among the eight because Level Two adds nothing here. How the levels map to attacker capability is set out in the Essential Eight maturity levels.
Why is Maturity Level Two the same as Level One for patch operating systems?
For this strategy, the controls at Maturity Level Two are identical to Maturity Level One, and the ASD assessment guide states that no separate assessment is required at Level Two because the controls are the same. It is the only strategy where a level adds nothing.
This is a result of the November 2023 update to the maturity model. That update rebalanced the workstation and non internet facing operating system patch timeframe to one month at Maturity Level One, which happened to bring Level One and Level Two into alignment for this strategy. It is worth knowing when assessing or planning, because it means the effort for operating system patching is concentrated at Level One and again at Level Three, with no additional work at Level Two. The absence of a Level Two step is not a gap in the model. It is a deliberate consequence of setting a sensible Level One standard. The changes made in November 2023 are worth understanding when comparing older guidance.
What changes for patch operating systems at Maturity Level Three?
Maturity Level Three closes the lower layers and speeds up workstation patching. It adds scanning for drivers and firmware at least fortnightly, requires drivers and firmware to be patched within 48 hours when critical and within one month otherwise, tightens workstation and non internet facing operating system patching to 48 hours when critical, and requires the latest or previous release of operating systems to be used.
The logic is that a capable attacker, the kind Level Three is calibrated against, does not stop at the operating system. Once the operating system is patched and current, drivers and firmware become the next target, because they run with high privilege and are often neglected. Firmware in particular is hard to patch and easy to forget, which is exactly why an advanced attacker looks there. Requiring the latest or previous release of operating systems also stops an organisation from staying on an old but still supported version indefinitely. Level Three is where operating system patching stops being about the obvious layer and starts covering the whole stack. For an organisation working towards a Level Three target, we help through Essential Eight advisory and assessment.
Frequently asked questions
What does patch operating systems mean in the Essential Eight?
Patch operating systems is the Essential Eight strategy that requires organisations to keep the operating systems on their servers, workstations and network devices up to date, and to replace operating systems no longer supported by the vendor. It sets scanning frequencies and patch timeframes tiered by internet exposure, with the tightest windows for internet facing servers and network devices. It is a companion to patch applications, covering the operating system layer rather than the applications on top.
What does patch operating systems require at each maturity level?
At Maturity Level One, organisations run asset discovery at least fortnightly, scan internet facing server and network device operating systems at least daily and other operating systems at least fortnightly, patch internet facing operating systems within 48 hours when critical, patch workstations and non internet facing systems within one month, and replace unsupported operating systems. Maturity Level Two has the same requirements. Maturity Level Three adds driver and firmware patching and tightens workstation patching to 48 hours when critical.
Why is Maturity Level Two the same as Level One for patch operating systems?
For patch operating systems, the controls at Maturity Level Two are identical to Maturity Level One, so the ASD assessment guide states no separate assessment is required at Level Two. This happened because the November 2023 update rebalanced the workstation and non internet facing patch timeframe to one month at Level One, which brought the two levels into line for this strategy. The real step up for this strategy comes at Maturity Level Three.
What changes for patch operating systems at Maturity Level Three?
Maturity Level Three adds scanning for drivers and firmware at least fortnightly, requires drivers and firmware to be patched within 48 hours when critical and within one month otherwise, tightens workstation and non internet facing operating system patching to 48 hours when critical, and requires the latest or previous release of operating systems to be used. It closes the lower layers, drivers and firmware, that a capable attacker targets once the operating system itself is current.
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 assessment process guide, Australian Signals Directorate, 2 October 2024
- Essential Eight maturity model changes, Australian Signals Directorate, 27 November 2023
Last updated: 30 August, 2026
