Skip to content
System management
ASD ISMISM-1696

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.

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

  1. 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.

  2. 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.

  3. 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 27001

ISO/IEC 27001: 2 mappings

  • A.5.7Threat intelligenceDepends on
Essential Eight

ASD Essential Eight: 7 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.