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).
Free. Save your status, tasks and notes.
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
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.
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.
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.
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.
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
- 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.
- 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.
- 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/IEC 27001: 1 mapping
This control partially meets A.8.8.
E8-PA-ML1.5 requires organisations to remediate critical online-service vulnerabilities by applying patches or mitigations within 48 hours. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which includes but is not limited to patching. E8-PA-ML1.5 is a concrete, time-bound implementation for a high-risk subset of vulnerability treatment covered more broadly by Annex A 8.8.
ASD Information Security Manual: 8 mappings
This control is equivalent to ISM-1876.
E8-PA-ML1.5 requires patches, updates or vendor mitigations for critical vulnerabilities in online services to be applied within 48 hours of release (including where working exploits exist). ISM-1876 states the same 48-hour requirement for critical vendor-assessed vulnerabilities or where working exploits exist in online services. The scope, trigger conditions and timeframe align closely such that implementing one would largely satisfy the other.
This control partially meets ISM-1754.
ISM-1754 requires vulnerabilities identified in software to be resolved in a timely manner. E8-PA-ML1.5 specifies a concrete timeliness requirement for one subset of software vulnerability remediation: applying critical patches for online services within 48 hours. E8-PA-ML1.5 is therefore one prescriptive implementation path that fits within the broader outcome stated by ISM-1754.
This control partially overlaps ISM-1483.
ISM-1483 requires internet-facing server applications to use the latest release, reducing risk from vulnerabilities addressed in newer versions. E8-PA-ML1.5 relates by mandating critical patches or vendor mitigations for online services within 48 hours, which is one mechanism to keep exposed services secure. E8-PA-ML1.5 is time-bound patching for critical issues, whereas ISM-1483 is a standing version/release requirement that can include but is not limited to patching.
- ISM-1877Patch internet-facing server/network OS in 48h if critical or exploit existsPartially overlaps
This control partially overlaps ISM-1877.
ISM-1877 focuses on patching operating systems for internet-facing servers and internet-facing network devices within 48 hours when vulnerabilities are critical or exploited. E8-PA-ML1.5 applies an equivalent 48-hour patching expectation, but for vulnerabilities in online services (applications), not OS on servers/network devices. They reinforce a consistent rapid remediation approach for exposed attack surfaces, but cover different technology layers.
This control partially overlaps ISM-1879.
E8-PA-ML1.5 requires applying critical patches for online services within 48 hours when rated critical or exploited. ISM-1879 requires the same 48-hour treatment but for critical vulnerabilities in drivers. They overlap when driver vulnerabilities affect systems delivering online services, but ISM-1879 is broader across endpoint/server drivers while E8-PA-ML1.5 is limited to online services.
This control is supported by ISM-1921.
ISM-1921 requires organisations to frequently reassess the likelihood of system compromise when working exploits exist for unmitigated vulnerabilities. E8-PA-ML1.5 supports ISM-1921 by providing a high-priority treatment trigger (critical or exploited online service vulnerabilities) that should drive urgent re-evaluation of compromise likelihood and residual risk while remediation is pending. E8-PA-ML1.5 is primarily a remediation timeframe for one asset class, whereas ISM-1921 is an assessment-cadence requirement that also applies when mitigations are not immediately possible.
This control depends on ISM-0298.
E8-PA-ML1.5 requires critical patches or vendor mitigations for online services to be applied within 48 hours. ISM-0298 supports E8-PA-ML1.5 by mandating a centralised, managed patching approach that maintains patch integrity and confirms successful application across applications, operating systems, drivers and firmware. ISM-0298 is about the patch management capability and assurance, whereas E8-PA-ML1.5 is a specific time-bound requirement for critical online-service vulnerabilities.
This control depends on ISM-1698.
E8-PA-ML1.5 requires organisations to apply critical patches or mitigations for vulnerabilities in online services within 48 hours of release. ISM-1698 supports E8-PA-ML1.5 by requiring daily vulnerability scanning of online services to identify missing patches or updates, helping detect gaps and drive timely remediation. ISM-1698 focuses on detection cadence, while E8-PA-ML1.5 mandates the remediation timeframe for critical issues.
ASD Essentials for enterprise IT: 2 mappings
- IT.PRO-06.2Apply security patches within risk-based timeframes, or automatically where impact is lowPartially meets
This control partially meets IT.PRO-06.2.
IT.PRO-06.2 requires security patches or updates to be applied within defined risk-based timeframes; E8-PA-ML1.5 sets a 48-hour deadline for patching online services when vendors assess vulnerabilities as critical or working exploits exist, one risk-based timeframe.
- IT.PRO-06.3Remediate or mitigate above-threshold vulnerabilities within defined timeframes and verify effectivenessPartially meets
This control partially meets IT.PRO-06.3.
IT.PRO-06.3 requires vulnerabilities above risk thresholds to be remediated or mitigated in set timeframes; E8-PA-ML1.5 sets 48 hours to apply patches or vendor mitigations for online services when vendors rate vulnerabilities critical or working exploits exist, one such timeframe.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




