Skip to content
Patch applications
Essential EightE8-PA-ML1.5

Essential Eight PA-ML1.5 Apply critical online service patches within 48 hours

What it says

Patches, updates or other vendor mitigations for vulnerabilities in online services 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 patches, updates or vendor mitigations for online service vulnerabilities within 48 hours of release if the vendor rates them critical or a working exploit exists.

Patches, updates or other vendor mitigations for vulnerabilities in online services must be applied within 48 hours of release when either:

  • the vendor assesses the vulnerability as critical, or
  • a working exploit (attack code that works against it) exists, noticed or not, whatever the vendor's rating.

Online services are services reached over the internet. Vendor mitigations are vendor fixes other than patches, such as configuration changes. The 48 hours count from release, not from when a scan finds the gap. Other vulnerabilities get two weeks (E8-PA-ML1.6).

Why it matters

Opportunistic attackers use publicly available exploits against unpatched online services. A vulnerability the vendor rates critical, or one with a working exploit, is an obvious target on a service anyone can reach, so applying the fix within 48 hours keeps the exposure short.

How to implement

  1. Follow vendor advisories for every online service you run.

    Subscribe to each vendor's security notices for the services in your scan scope (E8-PA-ML1.3), so a fix is seen the day it is released rather than whenever the next scan finds it.

  2. Decide straight away whether the 48 hours apply.

    Take the severity from the vendor's own advisory, because a scanner may show a score from another source. Check the advisory, public lists of exploited vulnerabilities and threat intelligence for a working exploit. Either condition puts the fix on the 48-hour path.

  3. Apply the fix within 48 hours of release.

    Agree an emergency change route in advance so approval does not use up the time. Where the vendor offers a mitigation instead of a patch, such as a configuration change, apply it and check it by hand, because a scanner may not detect it.

  4. Confirm the fix and keep the times.

    Rescan or check the service after the change, and record the release time and the time the fix was applied, so you can show 48 hours was met.

  5. Check providers that run online services for you.

    You cannot apply their fixes, so ask how quickly the provider applies fixes for vulnerabilities the vendor rates critical or that have a working exploit, and get evidence that it is within 48 hours of release.

Keep it running

Recheck open fixes when a vendor raises a rating to critical or a working exploit appears: the 48 hours count from release, so an older fix is then already overdue. Review the emergency change route after any fix that missed 48 hours.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Vendor advisories for the organisation's online services over recent months, with patch and change records.

    Look at

    For each vulnerability the vendor rated critical, when the fix was released and applied and, if the vendor raised its rating to critical later, when it did so.

    Good evidence

    Every patch, update or vendor mitigation for a vulnerability the vendor rated critical was applied within 48 hours of its release or, where the vendor raised its rating to critical more than 48 hours after release, already applied when the rating was raised. A fix released less than 48 hours before the audit is not yet due, and an exception or accepted risk counts as not applied.

  2. Check 2 of 3What an auditor asks for

    Ask for

    Vulnerabilities in those services that had a working exploit, taken from public lists of exploited vulnerabilities and threat intelligence, including ones the vendor rated below critical.

    Look at

    When each fix was released and applied, when the working exploit first appeared, and the vendor's rating, including when any rating of critical was given.

    Good evidence

    Each one with a released fix had that fix applied within 48 hours of release or, where the vendor had not rated it critical within 48 hours of release and the working exploit first appeared more than 48 hours after release, already applied when the exploit appeared. A fix released less than 48 hours before the audit is not yet due.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A network-based scan or version check of each online service, with a manual check of vendor mitigations.

    Look at

    Installed versions and install dates against vendor release dates, and configuration changes a scanner cannot see.

    Good evidence

    No online service lacks a fix, released more than 48 hours earlier, for a vulnerability the vendor rated critical or that has a working exploit, and each vendor mitigation used instead of a patch is present in the live configuration.

Mappings

Closest match in ASD Information Security Manual: ISM-1876, Patch online services within 48 hours if critical or a working exploit exists, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 1 mapping

ASD ISM

ASD Information Security Manual: 8 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

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