Skip to content
Enterprise mobility
ASD ISMISM-1366

ASD ISM 1366 Ensure timely security updates for mobile devices

What it says

Security updates are applied to mobile devices as soon as they become available.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Apply security updates to mobile devices as soon as they become available, rather than waiting for a scheduled cycle or leaving users to install them when they choose.

Security updates must be applied to mobile devices as soon as they become available. Available means the vendor or carrier has released the update for that model. Applied means installed on the device, not only offered. The control sets no grace period, and time limits in other patching controls, such as ISM-1878 for critical vulnerabilities in operating systems, do not soften this wording. Mobile devices here are those on a mobile operating system, such as smartphones and tablets.

Why it matters

Until an available update is installed, a device stays open to a flaw the vendor has already identified, often while on networks outside the office. Applying updates as soon as they appear keeps that window short and the device's security from slipping.

How to implement

  1. List every mobile device with its model and software version.

    Cover every device on a mobile operating system; those on a desktop one fall under patching controls such as ISM-1696. Compare the device management console with the asset register and sign-in logs, to find unmanaged devices. Note each model's vendor support status: ISM-1501 requires replacing unsupported operating systems.

  2. Remove the delays you control.

    In device management, turn off deferral periods and scheduled windows for security updates, and set them to install automatically at the shortest deadline the platform allows, so users cannot keep postponing. Cover the operating system, firmware and applications. Some platforms or versions force installation only in supervised or fully managed mode (ISM-1886).

  3. Track each release against what devices run.

    Subscribe to each vendor's security release notices. Use the console's version report, or the centralised patching approach ISM-0298 requires, to confirm the update installed on each device. Note where a carrier delays a model's update, because that delay sets when it becomes available.

  4. Block devices that fall behind.

    Use a compliance rule at sign-in, so a device missing an available security update cannot reach organisational systems until it installs. Follow up devices that are offline, out of storage or unable to update.

  5. Do not let testing delay the fleet.

    Run any compatibility check on a small group at the same time as the general rollout, because the control allows no waiting period. If an update must be held back, treat that as a known shortfall to resolve, not an approved exception.

Keep it running

Watch vendor security release notices and compare each with device versions in the console. A new release, a device falling behind, or a model nearing the end of vendor support should trigger action. ISM-1501 requires unsupported operating systems to be replaced.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Each vendor's published security release dates for the models and managed applications in use, and the device management report of installed versions and install dates, for all devices on an independent list of those on a mobile operating system, from sources such as the asset register or sign-in logs.

    Look at

    The gap between each release and its installation on each device, any device still behind, with its last check-in, its sign-in logs and its access to organisational systems, and any device missing from the report.

    Good evidence

    Every device on the independent list appears in the report and has the latest security update available for its model and managed applications, and the gaps show no waiting added by the organisation. A device without that update passes only if its last check-in and the sign-in logs both show no connection since the release and it cannot reach organisational systems until it updates. Staying inside an internal target, or the limit in ISM-1878, does not pass on its own.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The update settings in device management for each platform, and the same settings on a device sampled from the independent list.

    Look at

    Any deferral period, scheduled window or user choice that could hold an update back, and whether a user can change it.

    Good evidence

    No deferral period or scheduled window holds back security updates, users cannot change these settings or keep postponing updates, and the sampled device shows the same settings.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The list of models and operating system versions in use, compared with each vendor's current support list.

    Look at

    Whether any device runs a model or version the vendor no longer updates.

    Good evidence

    Every device runs a model and version the vendor still updates. A device past support has no security updates left to apply, so report it under ISM-1501 and ISM-1809, and do not count it as evidence that this control is met.

Mappings

Closest match in ISO/IEC 27001: A.8.8, Management of technical vulnerabilities, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

Essential Eight

ASD Essential Eight: 1 mapping

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