Skip to content
Enterprise mobility
ASD ISMISM-2097

ASD ISM 2097 Configure mobile devices with always on VPN

What it says

Mobile devices are configured with always on VPN functionality.

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

In plain English

Configure mobile devices with always on VPN functionality, so the VPN starts and stays up by itself on every network instead of relying on users to turn it on.

Mobile devices must be configured with always on VPN functionality. A VPN (virtual private network) is an encrypted tunnel between the device and the organisation's network or VPN service. Always on means the device starts the VPN itself and keeps it running on any network, rather than users turning it on. A VPN covering only selected applications is not always on. Mobile devices here are those on a mobile operating system, such as smartphones and tablets. ISM-0705 separately requires split tunnelling, where some traffic bypasses the VPN, to be disabled.

Why it matters

Without it, a device's traffic travels outside the VPN whenever a user forgets or chooses not to connect, more visible to whoever runs that network and missing the organisation's gateway protections. Starting the VPN automatically closes that gap.

How to implement

  1. List every mobile device and its always on VPN option.

    Cover every device on a mobile operating system; for those on a desktop one, no control requires always on VPN, though ISM-0874 and ISM-0705 apply. Check each platform and VPN client, including any bought service, for a whole-device always on mode. Some offer it only in supervised mode (ISM-1886).

  2. Size the VPN gateway for every device connected at once.

    Devices will now hold a tunnel whenever they have a network, so check gateway capacity and client licences before rollout, or the provider's limits on a bought service. A gateway that cannot keep up will cut people off and prompt requests for exceptions.

  3. Build the always on profile in device management.

    Set the VPN to start without user action and reconnect after restarts and network changes. Authenticate without a user prompt, such as with a device certificate. User multi-factor authentication to the systems behind it still applies (ISM-0974). Stop users changing the profile or adding their own (ISM-0864).

  4. Block traffic when the tunnel is down, where the platform offers it.

    The control does not name this setting, but without it traffic can leave between a restart and the VPN connecting, a gap against ISM-0874. A block also stops hotel Wi-Fi sign-in pages, so choose: staff use cellular data there, or you exempt sign-in pages, the same gap.

  5. Test on real networks, then roll out.

    Restart the device, switch between cellular and Wi-Fi, check a hotel-style Wi-Fi sign-in page behaves as you chose, and try to turn the VPN off as a user. Where a model cannot keep the VPN on, replace it or block it from organisational systems; a recorded exception stays a known shortfall.

Keep it running

Watch VPN gateway capacity and connection failures, because a dropped tunnel can cut devices off or leave traffic outside it. Test again after operating system, VPN client or gateway changes, when a new model arrives, and when someone asks for an exemption.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The device management console's list of devices with the VPN profile applied to each, and an independent list of devices on a mobile operating system, from sources such as the asset register, carrier bills or sign-in logs.

    Look at

    Whether every device on the independent list has the always on setting, rather than a per-application or manually started VPN.

    Good evidence

    Every device on the independent list has the whole-device always on setting applied, including any privately owned devices allowed to connect. A per-application or manual VPN does not pass, and neither does a recorded exception.

  2. Check 2 of 3What an auditor asks for

    Ask for

    A live test on a device of each platform sampled from the independent list: a restart, a change between Wi-Fi and cellular, an attempt to turn the VPN off as an ordinary user, and a forced tunnel failure.

    Look at

    The VPN's state after each event, the matching records on the VPN gateway, and whether traffic gets out while the tunnel is down.

    Good evidence

    The VPN reconnects by itself after each event, the gateway records agree, and the user cannot turn it off. Apart from what the device needs to join the network and reconnect the VPN, any traffic getting out while the tunnel is down, including through a Wi-Fi sign-in page exemption, is a gap against ISM-0874 until closed.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The exemptions in the VPN profile, and sign-in logs for organisational services showing the source address of mobile device sign-ins.

    Look at

    What each exemption lets outside the tunnel, and whether sign-ins come from the VPN's addresses or from other networks.

    Good evidence

    No exemption goes beyond what a Wi-Fi sign-in page needs, and sampled devices sign in to organisational services through the VPN's addresses. A wider exemption fails here, and one running alongside a live tunnel is also split tunnelling (ISM-0705). A Wi-Fi sign-in page exemption, used before the tunnel is up, is not split tunnelling but is a gap against ISM-0874 until closed, as is a sign-in from a home, hotel or carrier address before the tunnel connects.

Mappings

Closest match in ISO/IEC 27001: A.8.1, User end point devices, which this control partially meets.

ISO 27001

ISO/IEC 27001: 3 mappings

  • A.8.1User end point devicesPartially meets
  • A.8.20Networks securityPartially meets
  • A.5.14Information transferSupports

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