ASD ISM 2099 Prevent connection of mobile devices to infotainment
What it says
Mobile devices are not connected to the infotainment systems of connected vehicles.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Do not connect mobile devices to the infotainment systems of connected vehicles by any means, including Bluetooth, Wi-Fi, USB or phone projection.
Mobile devices must not be connected to the infotainment systems of connected vehicles. An infotainment system is the dashboard unit for audio, navigation and calls; a connected vehicle is one that sends data over a network, often to its manufacturer. Any connection counts, including Bluetooth, Wi-Fi, USB and phone projection (showing phone apps on the vehicle's screen). The ban covers all mobile devices, even on short trips or in hire vehicles. ISM-2100 and ISM-2101 bar viewing sensitive or classified data, and such calls and conversations, in or near these vehicles.
Free. Save your status, tasks and notes.
Why it matters
Connected vehicles can record and send data about occupants and linked devices, often to the manufacturer, which may pass it on. A connected phone can give up contacts, messages and call history, and staying unconnected keeps the device's data out of that path.
How to implement
State the rule in the mobile device usage policy (ISM-1082).
Cover Bluetooth, Wi-Fi, USB and phone projection, in fleet, hire and private vehicles. People usually cannot tell from the driver's seat whether a vehicle is connected, so unless records show a vehicle has no data link, treat it as connected.
Give people another way to do what the connection did.
Provide a cradle and the device's own speaker, or an authorised hands-free kit separate from the vehicle (ISM-0682 bars Bluetooth on SECRET and TOP SECRET devices). Charge from an authorised power adapter, not the vehicle's USB port. ISM-2101 still bars sensitive or classified calls within or near connected vehicles.
Block what mobile device management can block.
On supervised devices (ISM-1886), turn off phone projection where the platform offers the setting, and keep USB data transfers off (ISM-2098). Management tools usually cannot tell a vehicle from other Bluetooth devices, so use a peripheral allowlist if one is available.
Remove any existing connections at both ends.
Delete the vehicle from the device's Bluetooth, Wi-Fi and projection lists. In the vehicle's settings, delete the device and any copied contacts, call logs or messages, using a factory reset on fleet vehicles if the menu leaves them behind. This clears local copies but does not recall anything already sent.
Keep it running
Recheck when the organisation buys or hires vehicles, or changes device models or settings. Treat any connection found as a fault: remove it at both ends and find out why the alternative did not suit.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
Paired device lists, saved Wi-Fi networks and phone projection settings on a sample of mobile devices drawn from sign-in logs, including those of people who drive for work.
Look at
Whether any entry is a vehicle, such as a manufacturer or model name.
Good evidence
No sampled device holds a pairing, saved network or projection link to a vehicle infotainment system, unless records show that vehicle has no data link.
- Check 2 of 3What an auditor asks for
Ask for
The phone and device lists in the infotainment systems of a sample of connected fleet or pool vehicles, picked from vehicle records, where the organisation has any.
Look at
Whether any mobile device name, contacts or messages appear there.
Good evidence
No mobile device, and nothing copied from one, appears in any sampled vehicle.
- Check 3 of 3What an auditor asks for
Ask for
The live mobile device management settings on a sampled device with a mobile operating system, with a USB data transfer tried against a computer rather than a vehicle.
Look at
Whether phone projection is off where the platform has the setting, whether USB data transfers are off (ISM-2098), and whether the user can change them.
Good evidence
Phone projection is off where the platform offers the setting, USB data transfers are off, the transfer fails and the user cannot change either.
Mappings
Closest match in ISO/IEC 27001: A.8.12, Data leakage prevention, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.12.
ISM-2099 requires that mobile devices are not connected to the infotainment systems of connected vehicles. This prevents contacts, messages and other sensitive data from being synchronised to and retained in vehicle systems outside organisational control, which is a specific data leakage prevention measure for devices under Annex A 8.12. Annex A 8.12 applies leakage prevention across all systems, networks and devices, whereas ISM-2099 addresses one leakage path.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




