Skip to content
Enterprise mobility
ASD ISMISM-2101

ASD ISM 2101 No sensitive or classified calls or conversations in or near connected vehicles

What it says

Sensitive or classified phone calls and conversations are not conducted within or near connected vehicles.

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

In plain English

Do not hold sensitive or classified phone calls or conversations inside or close to a connected (internet-linked) vehicle, even with care taken not to be heard.

Sensitive or classified phone calls and conversations must not be held within or near connected vehicles. Conversations include talking in person. 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 means compromise would damage an organisation or person, and classified includes OFFICIAL: Sensitive and above. The ISM sets no distance for near, so the organisation sets one. Unlike ISM-1644, this control has no exception for taking care, and hands-free calling changes nothing.

Why it matters

A connected vehicle's infotainment system or connected services can record a conversation, keep it and pass it on, beyond the organisation's control. Holding sensitive or classified calls and conversations away from these vehicles keeps them out of those systems.

How to implement

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

    Use the policy ISM-1082 requires, covering in-person conversations and calls on organisation-owned and privately owned mobile devices, with no exception for hands-free use or parked vehicles. Say what near means, because the ISM gives no distance: base it on how far a vehicle's systems could pick up speech.

  2. Find where these conversations happen around vehicles.

    Look at on-call duties, shared trips to meetings, site visits and calls taken in car parks. 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. Agree a way to defer calls that reach someone in a vehicle.

    Use a holding line with no details, such as 'call you back shortly', then resume once the person has left the vehicle and moved away. Move debriefs from the car to the destination. Not pairing the phone (ISM-2099) does not make the call acceptable.

  4. Record duties that cannot change yet as shortfalls.

    An on-call role that must take sensitive calls on the road is one example. 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 on-call arrangements, fleet or hire arrangements or meeting locations change. A report of a sensitive or classified call taken in or near a connected vehicle should prompt a look at why the person saw no alternative.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The mobile device usage policy (ISM-1082), with the on-call and field duty rosters.

    Look at

    Whether the policy covers both calls and conversations, within and near, with no exception, and whether each rostered duty has a way to take such calls away from vehicles.

    Good evidence

    The policy bars both calls and conversations within and near connected vehicles with no exception and says what near means, and every rostered duty has a stated way to take such calls away from vehicles.

  2. Check 2 of 3What an auditor asks for

    Ask for

    Interviews with people picked from on-call rosters, fleet bookings and travel records, including anyone on a privately owned device.

    Look at

    What each person does when a sensitive or classified call comes in on the road, or such a conversation starts in a car, including hands-free and when parked.

    Good evidence

    Each person defers the call or conversation until out of the vehicle and away from connected vehicles, and nobody treats hands-free use or a parked vehicle as acceptable.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Logs from an encrypted calling service, or incident and duty call logs, matched to trip times in fleet or travel records for a sample of those people.

    Look at

    Whether any sensitive or classified call overlaps that person's trip in a vehicle that is connected or treated as connected.

    Good evidence

    No sampled call was held while the person was in or near the vehicle on such a trip. One that was is a shortfall until the duty has changed, even if a risk or exception was recorded.

Mappings

Closest match in ISO/IEC 27001: A.6.7, Remote working, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.6.7Remote workingPartially meets

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