ASD ISM 1696 Fix workstation, internal server/network OS in 48h if critical or exploit exists
What it says
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 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Apply vendor fixes within 48 hours of release for operating system flaws the vendor rates critical, or that have a working exploit, on workstations and non-internet-facing servers and network devices.
Vendor patches, updates or other mitigations for vulnerabilities in the operating systems of workstations, non-internet-facing servers and non-internet-facing network devices must be applied within 48 hours of release when the vendor rates the vulnerability critical or a working exploit exists. Either trigger is enough: a working exploit, meaning code or a technique known to succeed against the flaw, counts whatever the vendor's rating. Non-internet-facing means not reachable from the internet. Every workstation is covered, and the 48 hours include weekends.
Free. Save your status, tasks and notes.
Why it matters
Flaws rated critical or with a working exploit are the ones malicious actors can use soonest. One compromised workstation can open a path to internal servers and network devices, so applying these fixes on every device within 48 hours narrows that window.
How to implement
Watch for critical ratings and working exploits.
Take each operating system vendor's security notices and severity ratings, including network device makers', plus ASD alerts and reports of working exploit code or attacks. Assign someone to see each new release on the day it appears, weekends included, with authority to start an urgent change.
Pre-approve an urgent change path.
Use the change and configuration management plan, which ISM-0912 says must define urgent changes and who approves them, to pre-approve fixes for flaws rated critical or with a working exploit, so approval does not use up the 48 hours. Agree the same turnaround with any provider that manages your servers or network devices.
Push the fix to every in-scope device, not only key servers.
Send it through the central patch tool to a small pilot group, then to all workstations, non-internet-facing servers and non-internet-facing network devices, with a forced install and restart deadline inside 48 hours of release. Book server and network device restarts straight away.
Use the vendor's mitigation where the patch cannot go on in time.
Apply the workaround the vendor publishes, such as a setting change, within the 48 hours, then install the patch as soon as it can be. Isolate any device that can take neither, and record it as an open shortfall.
Confirm every device took the fix.
Compare the patch tool's success reports with a vulnerability scan or live version check, and chase offline laptops and failed installs before the 48 hours end.
Keep it running
If a working exploit appears for a fix still pending, the 48 hours from release may already have passed, so apply it at once. Add new workstations, servers and network devices to the urgent deployment group as they are built.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
Operating system vulnerabilities that vendors rated critical or that had a working exploit, over a period long enough to include several, with each fix's release time, checked against a list the auditor builds from vendor notices and ASD alerts.
Look at
When each fix was applied on workstations, non-internet-facing servers and non-internet-facing network devices sampled from a discovery scan.
Good evidence
Every listed fix, including any the vendor rated below critical that had a working exploit, was applied on every sampled device within 48 hours of release, weekends included.
- Check 2 of 3What an auditor asks for
Ask for
The devices the urgent patch process covers, compared with a discovery scan or directory records.
Look at
Whether all workstations are included, not only servers or devices the organisation calls critical.
Good evidence
Every workstation, non-internet-facing server and non-internet-facing network device on the independent list gets fixes for flaws rated critical or with a working exploit through the 48-hour process, with none left to the one-month cycle.
- Check 3 of 3What an auditor asks for
Ask for
A vulnerability scan of sampled devices run during the audit.
Look at
Any missing fix for a vulnerability the vendor rated critical, or with a working exploit, released more than 48 hours earlier.
Good evidence
No sampled device lacks such a fix or the vendor's mitigation. A device covered only by an exception, an accepted risk or isolation counts as a failure until it is fixed.
Mappings
Closest match in ASD Essential Eight: E8-PO-ML3.3, Apply critical patches to non-internet-facing OS within 48 hours, which asks for the same thing.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.8.
ISM-1696 requires a specific technical vulnerability treatment outcome: applying critical OS patches within 48 hours for defined non-internet-facing systems and workstations when rated critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which includes patching as one possible treatment. ISM-1696 is a prescriptive, time-bound implementation that fits within the broader vulnerability management expectation of Annex A 8.8.
This control depends on A.5.7.
ISM-1696 requires applying critical OS patches within 48 hours when vendors assess vulnerabilities as critical or when working exploits exist. ISO/IEC 27001:2022 Annex A 5.7 requires collecting and analysing threat information to produce threat intelligence, which can inform whether working exploits exist and drive prioritisation decisions for patching. Annex A 5.7 does not require patch application, but it strengthens the decision inputs and triggers that help organisations meet ISM-1696 timeframes.
ASD Essential Eight: 7 mappings
This control is equivalent to E8-PO-ML3.3.
ISM-1696 requires critical patches, updates or vendor mitigations for operating systems on workstations, non-internet-facing servers and non-internet-facing network devices to be applied within 48 hours when rated critical or when working exploits exist. E8-PO-ML3.3 states the same 48-hour requirement for the same system scope and the same triggering conditions (vendor-critical or working exploit). Implementing E8-PO-ML3.3 would largely satisfy ISM-1696 and vice versa.
This control partially overlaps E8-PO-ML1.5.
ISM-1696 requires applying critical OS patches within 48 hours for workstations, non-internet-facing servers and non-internet-facing network devices when vendors rate vulnerabilities critical or working exploits exist. E8-PO-ML1.5 also mandates a 48-hour patch window under the same critical/exploit conditions, but it applies to internet-facing servers and internet-facing network devices. They align on urgency and decision triggers, but differ materially on asset exposure scope (internet-facing versus non-internet-facing/workstations).
- E8-PO-ML1.7One-month operating system patching for workstations, non-internet-facing servers and network devicesPartially overlaps
This control partially overlaps E8-PO-ML1.7.
E8-PO-ML1.7 requires operating system patches for workstations, non-internet-facing servers and non-internet-facing network devices to be applied within one month of release, while ISM-1696 requires patches for the same systems within 48 hours where vendors assess vulnerabilities as critical or working exploits exist. They share the same assets and activity, but ISM-1696 imposes a much shorter deadline for that subset and E8-PO-ML1.7 also covers non-critical vulnerabilities.
- E8-PO-ML3.4Non-critical non-internet-facing OS patches within one month if no exploitsPartially overlaps
This control partially overlaps E8-PO-ML3.4.
E8-PO-ML3.4 sets a one-month patching requirement for non-critical OS vulnerabilities on non-internet-facing workstations/servers/network devices when no working exploits exist. ISM-1696 covers the same OS and internal asset scope, but applies to the different condition of critical vendor ratings or the existence of working exploits, with a much shorter 48-hour timeframe. They intersect on the same patch management activity and assets, but address different severity/exploit scenarios and therefore are complementary rather than equivalent.
This control depends on E8-PO-ML1.1.
ISM-1696 requires critical OS patches to be applied within 48 hours for workstations and non-internet-facing servers and network devices when rated critical or exploited. E8-PO-ML1.1 requires automated asset discovery at least fortnightly to ensure assets are known for subsequent vulnerability scanning, which underpins the ability to identify where critical patches must be applied. Without asset discovery, organisations can miss unmanaged endpoints and fail to meet ISM-1696 timeframes for all in-scope systems.
This control depends on E8-PO-ML1.2.
ISM-1696 requires rapid application of critical OS patches within 48 hours for specified non-internet-facing systems and workstations based on vendor criticality or working exploits. E8-PO-ML1.2 requires using a vulnerability scanner with an up-to-date database, which is a prerequisite capability to accurately identify and prioritise missing critical patches and known exploited vulnerabilities. While ISM-1696 is about patch deployment, it is dependent on reliable, current vulnerability intelligence/tooling like E8-PO-ML1.2 to drive timely action and provide assurance coverage.
This control depends on E8-PO-ML1.4.
ISM-1696 requires organisations to apply critical operating system patches within 48 hours for workstations and non-internet-facing servers and network devices when vendors rate issues critical or working exploits exist. E8-PO-ML1.4 requires fortnightly vulnerability scanning to identify missing OS patches on the same asset classes, which provides an operational mechanism to detect patch gaps and validate patch compliance. While scanning does not itself meet the 48-hour patching requirement, ISM-1696 is practically dependent on discovery/verification activities like E8-PO-ML1.4 to reliably identify missing critical patches across the environment.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




