ASD ISM 2098 Prevent data transfer over USB on mobile devices
What it says
Mobile devices are configured to prevent data transfers over Universal Serial Bus connections.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Configure mobile devices to block data transfers in either direction over Universal Serial Bus (USB) connections; charging alone is not covered.
Mobile devices must be configured to prevent data transfers over Universal Serial Bus (USB) connections. The device itself must block them, in either direction, whether the other end is a computer, storage drive or other USB equipment. Unlike ISM-0343 and ISM-1418, it does not depend on a business requirement. Charging is not a data transfer, so this control does not stop it, though ISM-1299 advises against designated charging stations and wall outlet charging ports. Mobile devices here are those on a mobile operating system, such as smartphones and tablets.
Free. Save your status, tasks and notes.
Why it matters
A USB cable bypasses the network controls watching a device. Without this block, someone with brief access to an unlocked device, or a compromised computer or charging point the user accepts, can copy organisational data off the device or load files onto it.
How to implement
List every mobile device and the USB block it supports.
Cover every device on a mobile operating system; on a desktop one, ISM-1418 and ISM-0343 cover removable media instead. For each platform and model, find the setting blocking all USB data. Some offer only a file transfer block, need a recent version, or need supervised or fully managed mode (ISM-1886).
Move cable-based routines to managed services first.
Shift backups, file sharing and application loading to the network, so nobody needs a cable once the block goes live. Do any setup that needs USB before the block applies, and confirm it is back on after any repair that needed USB.
Apply the block through device management.
Use the all-data setting where available. Otherwise block file transfer, USB drive access, pairing with computers, debugging and USB tethering one by one. Stop users turning it off (ISM-0864).
Test with a real cable and computer.
On a test device of each model, try to copy files both ways, pair with an unknown computer, make a backup, tether and use a USB drive. Fix any route that works.
Handle models that cannot block USB data.
Replace them, or block them from organisational systems with a compliance rule at sign-in. A recorded exception stays a known shortfall until then. Treat any privately owned device allowed to connect the same way, because the control makes no exception for it.
Keep it running
Recheck the block after operating system upgrades, repairs and resets, and when a new model arrives, because settings differ by model and version. A request to sync, back up or load files by cable should prompt a different route, not an exception.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
The device management console's list of devices with the USB setting 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 setting, and whether it blocks all USB data or only file transfer.
Good evidence
Every device on the independent list prevents USB data transfers, including any privately owned devices allowed to connect. A file transfer block passes only if USB drive access, pairing, debugging and USB tethering are also blocked, and a recorded exception does not pass.
- Check 2 of 2What an auditor asks for
Ask for
A live test on devices sampled from the independent list to cover each platform and model, including a recently repaired or reset one, with a cable, a computer they have not met and a USB drive.
Look at
Whether files can be copied in either direction, whether pairing, backup, debugging or USB tethering works, and whether an ordinary user can turn the block off.
Good evidence
No data moves in either direction by any of those routes, and an ordinary user cannot turn the block off.
Mappings
Closest match in ISO/IEC 27001: A.5.14, Information transfer, which this control partially meets.
ISO/IEC 27001: 3 mappings
This control partially meets A.5.14.
ISM-2098 requires mobile devices to be configured to prevent data transfers over USB connections. ISO/IEC 27001:2022 Annex A 5.14 requires information transfer rules and procedures for all transfer facilities, which can include controls over physical interfaces such as USB when they are used as a transfer channel. ISM-2098 is one concrete, device-level control that implements a restriction within the wider policy or procedure framework of Annex A 5.14.
This control partially meets A.5.15.
ISM-2098 requires mobile devices to be configured so data cannot be transferred over USB connections. This is an access/usage restriction on an interface that fits within Annex A 5.15, which requires establishing and implementing rules to control physical and logical access to information and associated assets. Annex A 5.15 is broader because it covers policy-driven access control across systems, networks, and physical environments, whereas ISM-2098 is a single technical enforcement point for one channel on one asset class (mobile devices).
This control partially meets A.7.10.
ISM-2098 requires mobile devices to be configured to prevent data transfers over USB connections. ISO/IEC 27001:2022 Annex A 7.10 requires secure management of storage media across its lifecycle, which includes controlling the use of removable media and interfaces that enable copying to/from such media. ISM-2098 is a specific technical enforcement mechanism (USB data blocking on mobiles) that fits within the broader storage media governance required by Annex A 7.10.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




