Applies to: All editions
Supported approach
USB-attached storage and removable flash media use overwrite-based sanitization in DriveErase. Firmware methods are blocked because USB bridges and removable media normally do not provide the required native protocol access.
Device identity
USB enclosures can report the bridge’s identity rather than the underlying drive. Confirm:
- Enclosure and physical device labels;
- Reported model and serial;
- Capacity;
- USB port or bay;
- Whether the media is a rotational HDD, SSD, or flash device;
- Whether multiple identical devices are connected.
Where identity is weak, connect one approved device at a time.
USB HDDs
A complete successful overwrite can process the addressable logical range of a functioning USB HDD. The bridge must remain stable throughout the job and must not reset, disconnect, or change the reported capacity.
USB SSDs and flash media
Host overwrite reaches the logical range exposed by the device. It does not prove that wear-levelled, over-provisioned, retired, remapped, or hidden flash storage was processed.
Where policy requires stronger assurance and native firmware sanitization cannot be accessed, remove the underlying compatible device for direct attachment or apply the approved physical-destruction process.
Operational controls
- Disable USB power-saving features that could interrupt long operations where policy permits.
- Use a reliable direct port rather than an unpowered hub.
- Avoid moving the device or cable.
- Do not rely on a low-quality adapter for a long multi-pass job.
- Treat any disconnect as an incomplete result.
Health assessment
SMART and self-test passthrough can be unavailable through USB. Full Media Read Scan and Sampled Write-Verify Test can still provide host-visible evidence, subject to bridge stability and the limitations of those tests.