Skip to content
arrow_back
boltASD Essential Eight

Essential Eight PO-ML1.7One-month operating system patching for workstations, non-internet-facing servers and network devices

Official control statement

Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within one month of release.
boltASD Essential EightE8-PO-ML1.7

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Once a fix is public, attackers can work out the flaw it closes, so apply operating system fixes to workstations and non-internet-facing servers and network devices within a month of release.

Control Stack classificationPreventativePatch management
record_voice_over

What this means in practice

Operating system vendors regularly publish fixes for security flaws found in their software. A fix can be a patch, an update that contains the fix, or another mitigation the vendor publishes, such as a configuration change or workaround. This control covers the operating systems of three kinds of asset: workstations (the desktops and laptops people use every day), servers that are not internet-facing (such as internal file, database and directory servers) and network devices that are not internet-facing (such as internal switches and routers). Fixes for vulnerabilities in those operating systems must be applied within one month of the vendor releasing them. It is about the operating system itself, such as Windows, macOS, Linux or a network device's operating system, not the applications installed on it. The month is counted from the vendor's release date, not from when the team first notices the fix, and it applies to every fix for a vulnerability in these operating systems, whatever severity the vendor gives it. It matters because once a fix is published the flaw becomes public knowledge, and attackers can study the fix to work out how to exploit it. Workstations are where many attacks start, through malicious email or websites, and servers and network devices that cannot be reached directly from the internet are still exposed once an attacker has that foothold inside. Unpatched operating systems then make it much easier for the attacker to gain administrator access, spread to other machines and reach sensitive data.

Framework

ASD Essential Eight

Control effect (Control Stack)

Preventative

E8 mitigation strategy

Patch operating systems

Classifications

N/A

Official last update

N/A

Control Stack last updated

15 Oct 2026

E8 maturity levels

N/A

priority_high

Why it matters

Known, publicly documented flaws stay open in the operating systems of workstations and non-internet-facing servers and network devices for more than a month after the vendor has released a fix. An attacker can exploit them to compromise a workstation in the first place, for example through a malicious email attachment or website, and then again to gain administrator access, move from machine to machine, take over servers that hold sensitive data or run core services such as directory and file services, and tamper with internal network devices, turning one foothold into an organisation-wide ransomware outage or data breach. The organisation also falls short of this Essential Eight requirement.

settings

Operational notes

Treat one month from the vendor's release date as the deadline for applying each patch, update or other vendor mitigation for a vulnerability in the operating system of a workstation, non-internet-facing server or non-internet-facing network device. Plan testing, staged deployment, maintenance windows and restarts so they finish well inside that month, leaving time to deal with devices that fail to install an update, are switched off or are away from the office network. Track missing operating system fixes against their deadlines using patch management and vulnerability scan results, and follow up devices before they become overdue rather than after. Network device upgrades often need a planned outage, so book those changes early in the window, and where a patch cannot be installed, apply the vendor's other published mitigation within the same month instead. Keep build images and templates up to date so newly deployed workstations and servers do not start out missing fixes released more than a month earlier, and keep each server's and network device's internet-facing status current in the asset inventory, because this one-month window applies to those that are not internet-facing.

build

Implementation tips

  • The IT operations manager should keep a complete list of workstations, non-internet-facing servers and non-internet-facing network devices, recording each one's operating system and version. Build it by combining the asset inventory with endpoint management and network management records, and mark every server and network device as internet-facing or not, so that no in-scope operating system sits outside the patching process.
  • The patch management lead should subscribe to the security advisories and update notifications of every operating system vendor in use, covering desktop, server and network device operating systems. Log each new patch, update or vendor mitigation with the date the vendor released it, and set its deadline at one month from that date rather than from when the team first sees it.
  • System administrators should configure the patch management tool (for example Microsoft Configuration Manager or Intune, Jamf for Mac computers, or a Linux patch management service) to deploy operating system updates to workstations and non-internet-facing servers in staged groups, starting with a small test group. Set installation deadlines and enforced restarts so that every device, including laptops working away from the office, has each update installed and active within one month of its release.
  • Network engineers should plan operating system upgrades for non-internet-facing switches, routers and other network devices through the change process: download the vendor's fixed release, trial it on a test or lower-risk device, and schedule the change for every affected device inside the one-month window. Where the vendor publishes a workaround or configuration change instead of, or ahead of, a fixed release, apply that mitigation within the same window.
  • The IT operations lead should run a report from the patch management tool and vulnerability scanner listing operating system fixes still missing from workstations, non-internet-facing servers and non-internet-facing network devices, sorted by vendor release date, and chase each device owner before the one-month deadline. Where a patch cannot be installed because it breaks a business system, the team should apply the vendor's other published mitigation within the same month and record what was applied and when.
fact_check

Audit / evidence tips

  • AskAsk for the asset inventory of workstations, servers and network devices, showing each one's operating system and version and whether it is internet-facing.Look atWorkstations, non-internet-facing servers and non-internet-facing network devices that are missing from the inventory or from the patch management and network management tools, and servers or network devices with no internet-facing classification.GoodEvery workstation, non-internet-facing server and non-internet-facing network device is recorded and covered by a patching process, so none of their operating systems are left out.
  • AskAsk how the team learns about new operating system patches, updates and vendor mitigations, and for the record of recent releases with their vendor release dates.Look atOperating systems in use that have no advisory source, and deadlines counted from when the team found or scanned for a fix rather than from the vendor's release date.GoodEvery operating system vendor in use is tracked, and each fix's one-month deadline is counted from the date the vendor released it.
  • AskAsk for patch compliance reports for workstations and non-internet-facing servers covering several recent operating system releases, and choose a sample of devices that includes laptops working away from the office.Look atThe gap between each update's vendor release date and the date it was installed and made active on each sampled device, and any devices that are offline, failing to install or still waiting for a restart.GoodEvery sampled workstation and non-internet-facing server had each operating system patch or update installed and active within one month of its release.
  • AskAsk for the current operating system versions of a sample of non-internet-facing switches, routers and other network devices, with the vendor advisories that apply to them and the change records for recent upgrades.Look atDevices still running a version the vendor fixed more than a month ago, and upgrades or vendor workarounds applied later than one month after their release.GoodEach sampled non-internet-facing network device had the vendor's fix or published mitigation applied within one month of its release.
  • AskAsk for recent vulnerability scan results for workstations, non-internet-facing servers and non-internet-facing network devices, and for records of any vulnerabilities handled with a vendor mitigation instead of a patch.Look atMissing operating system fixes whose vendor release date is more than one month old, and whether each mitigation used matches what the vendor published and was in place within one month of release.GoodScans show no operating system fixes outstanding beyond one month of release, and every vendor mitigation used in place of a patch was applied within the same window.
link

Cross-framework mappings

How E8-PO-ML1.7 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.

ISO 27001

ControlNotesDetails
layersPartially meets(1)expand_less
Annex A 8.8ISO/IEC 27001 Annex A 8.8 requires an organisation to obtain information about technical vulnerabilities, evaluate its exposure and take ...

ASD ISM

ControlNotesDetails
equalEquivalent(1)expand_less
ISM-1695E8-PO-ML1.7 and ISM-1695 use identical wording: patches, updates or other vendor mitigations for operating system vulnerabilities on work...
open_in_fullBroader than(1)expand_less
ISM-1902E8-PO-ML1.7 requires all operating system patches for workstations, non-internet-facing servers and non-internet-facing network devices t...
layersPartially meets(1)expand_less
ISM-1754ISM-1754 requires vulnerabilities identified in software to be resolved in a timely manner, without fixing a timeframe or limiting the so...
sync_altPartially overlaps(2)expand_less
ISM-0298E8-PO-ML1.7 requires operating system patches for workstations, non-internet-facing servers and non-internet-facing network devices to be...
ISM-1696E8-PO-ML1.7 requires operating system patches for workstations, non-internet-facing servers and non-internet-facing network devices to be...
extensionDepends on(2)expand_less
ISM-1143ISM-1143 requires patch management processes and supporting procedures to be developed, implemented and maintained, while E8-PO-ML1.7 req...
ISM-1702ISM-1702 requires a vulnerability scanner to be used at least fortnightly to find missing operating system patches on workstations, non-i...

These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.

See all Patch operating systems controls, or browse the full ASD Essential Eight library.

Mapping detail

Mapping

Direction

Controls