Skip to content
Rootways CIM Pro flaw CVE-2026-130583 lets attackers read Magento 2 store keys
Black Shard

Loading

    Essential Eight

    Patch applications, and the clock that starts at release.

    Patch applications is the strategy with a stopwatch. Every level sets how often the estate is scanned for missing updates and how long may pass between a vendor's release and its deployment, with the shortest window for an exploited flaw in an internet-facing service.

    Not published

    What the strategy requires

    The model treats patching as four habits: knowing what is installed, scanning it, applying the fix inside a window, and removing what the vendor no longer supports. At Maturity Level One an automated asset discovery runs at least fortnightly and feeds a scanner with a current vulnerability database.

    That scanner runs daily against online services and weekly against office productivity suites, web browsers and their extensions, email clients, PDF software and security products. The windows are 48 hours for an online service where the vendor rates the flaw critical or a working exploit exists, two weeks otherwise, and two weeks for the office and browser group.

    Maturity Level Two adds every other application to a fortnightly scan with a one month window. Maturity Level Three brings the office and browser group under the same 48 hour rule for critical or exploited flaws and removes any unsupported application of any kind.

    What an assessor looks for

    The assessor wants the dates. For a sample of releases across the scanned groups they compare the vendor's release date with the date the update reached the fleet, so the evidence is the scanner's history and the deployment console's reports side by side. A screenshot of the current state proves only the current state.

    They also ask what the scanner cannot see: the device that has not reported in a month, the laptop that only connects over a VPN at night, the browser extension nobody inventories. Fortnightly asset discovery feeding the scanner is the requirement that catches those, and the assessor tests it by picking a device at random.

    Common gaps

    Most estates patch; few measure the gap between release and deployment, so nobody knows the window was missed until an assessor counts the days. The second gap is scope, where the operating system is patched monthly and the browsers, PDF reader and productivity suite ride along on whatever cadence the vendor's own updater chooses.

    The third gap is the online service that is nobody's job because it runs in a vendor's cloud. Unsupported software is the quiet failure: a reporting tool on a retired runtime keeps working, so it stays, and at every level that one application fails the strategy outright.

    How to meet it in Microsoft 365 and Azure

    On a Microsoft tenant the discovery and the scanning are Microsoft Defender for Endpoint with Microsoft Defender Vulnerability Management, which inventories installed software per device and reports missing updates with the vendor's severity. Deployment for the office and browser group runs through Microsoft Intune, with Microsoft 365 Apps for enterprise on a current channel and Microsoft Edge updated by policy.

    Third-party applications are the harder half. Intune's enterprise application management catalogue, or a packaging pipeline that publishes each vendor's release as a required app, keeps them inside the window. Azure Update Manager carries the same role for virtual machines in Azure, and Azure Arc extends it to servers elsewhere. The evidence is the exposure report per release, exported and kept.

    Where it sits on the ladder

    The three pages beneath this one carry the requirement at each level. The first level sets the scanning cadence and the windows for online services and the office and browser group; the second extends the scan and a one month window to every other application.

    The third level tightens the office and browser group to 48 hours for critical or exploited flaws and removes every unsupported application. Patch operating systems is the sibling strategy with the same shape for operating systems, drivers and firmware.

    Dates

    When it was written, and checked.

    .

    Questions, answered.

    What counts as an online service in the Essential Eight?

    A service the organisation runs that is reachable from the internet: the web application, the remote access gateway, the mail gateway, the externally facing API. Those take the 48 hour window when a flaw is rated critical or has a working exploit, at every maturity level.

    Does the 48 hour window start when the patch is released or when we hear about it?

    At release. The model counts from the vendor's release, which is why daily scanning of online services is required: an organisation that learns of a patch a week late has already missed the window.

    Do browser extensions count as applications to patch?

    Yes. The model names web browsers and their extensions in the group scanned weekly and patched inside two weeks, so an extension inventory is part of the evidence.

    What happens to software the vendor no longer supports?

    It is removed. Unsupported online services and unsupported office, browser, email, PDF and security products fail the strategy at Maturity Level One; at Maturity Level Three any unsupported application does.

    Provenance

    Sources, and when they were read.

    Every source was read 31 Oct 2026.

    Being measured against Essential Eight? Scope the work.