Skip to content
Enterprise mobility
ASD ISMISM-2100

ASD ISM 2100 No sensitive or classified data on mobile screens in or near connected vehicles

What it says

Sensitive or classified data is not viewed on mobile devices within or near connected vehicles.

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

In plain English

Do not view sensitive or classified data on a mobile device inside or close to a connected (internet-linked) vehicle, even with care taken to shield the screen.

Sensitive or classified data must not be viewed on mobile devices (smartphones, tablets or laptops, organisation-owned or privately owned) within or near connected vehicles. A connected vehicle is any vehicle linked to the internet, by a built-in modem or a tethered phone, so data can pass to or from it. Sensitive data would damage an organisation or person if compromised, and classified data includes OFFICIAL: Sensitive and above. The ISM sets no distance for near, so the organisation sets one. Unlike ISM-0866, this control has no exception for taking care.

Why it matters

Cameras can record a mobile device's screen in or near a connected vehicle, and the vehicle can send data over the internet, beyond the organisation's control. Not viewing this data there leaves those cameras nothing sensitive to capture.

How to implement

  1. Write the rule into the mobile device usage policy.

    Use the policy ISM-1082 requires, with no exception for parked vehicles or for taking care. Say what near means, because the ISM gives no distance: base it on how far a vehicle's cameras could read a screen, and cover car parks and kerbsides.

  2. Work out which vehicles count.

    Check fleet, hire and leased vehicles for internet connectivity, built in or fitted later, and for whether a driver's phone can be tethered to them. Treat staff cars, taxis, rideshare vehicles and any vehicle you cannot check as connected, because a driver's tethered phone is enough. Public transport with onboard internet also fits that meaning.

  3. Change work that puts this data on screens in vehicles.

    Review field, dispatch and travel tasks that open sensitive or classified data on a phone, tablet or vehicle-mounted laptop. For the trip, send a job reference that reveals nothing sensitive, with the details opened once the person has moved away from the vehicle.

  4. Tell mobile device users what to do instead.

    Keep the data closed until out of the vehicle and away from other vehicles. Cover passengers as well as drivers, and anyone reaching this data on a privately owned device.

  5. Record tasks that cannot change yet as shortfalls.

    The control allows no exception, so give each one an owner and a date to close it, and do not describe it as approved.

Keep it running

Recheck when fleet or hire arrangements change, a role starts working from vehicles, or an app begins showing sensitive or classified data on phones. A report of such data being viewed in or near a connected vehicle should prompt a look at why.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The mobile device usage policy (ISM-1082) and the fleet and hire vehicle records.

    Look at

    Whether the policy bars viewing with no exception and says what near means, whether each vehicle type in the records has been assessed as connected or not, and whether each type marked not connected agrees with its manufacturer's specifications and with records of any devices, such as telematics units or dashcams, fitted later to each vehicle of that type.

    Good evidence

    The policy bars viewing sensitive or classified data within and near connected vehicles with no exception and says what near means, and every vehicle type in the records has been assessed. For each type marked not connected, its manufacturer's specifications and records of any devices fitted later to each vehicle of that type show no internet connectivity and no way to tether a driver's phone.

  2. Check 2 of 3What an auditor asks for

    Ask for

    Interviews with mobile device users picked from fleet bookings, travel records and field rosters, including anyone on a privately owned device.

    Look at

    What each person does with sensitive or classified data in a car, taxi or car park, including as a passenger and when parked.

    Good evidence

    Each person keeps such data closed until away from any connected vehicle, including as a passenger and when parked, and describes near the way the policy does.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Access logs for systems holding sensitive or classified data, matched to trip times in fleet or travel records for a sample of those users.

    Look at

    Whether such data was opened on that person's mobile device during a trip in a vehicle that is connected or treated as connected.

    Good evidence

    No sampled trip shows such data being opened on that person's mobile device while they were in or near the vehicle. One that does is a shortfall until the work has changed, even if a risk or exception was recorded.

Mappings

Closest match in ISO/IEC 27001: A.5.15, Access control, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.5.15Access controlPartially meets

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