Applies to: Pro, Enterprise, and Audit
Overview
Firmware-based sanitization sends a supported protocol command to the storage device and allows the device to process its media using its internal capabilities. This can provide broader device-level coverage than ordinary host overwrite on compatible flash storage.
DriveErase supports firmware workflows for eligible directly attached SATA/ATA SSDs, NVMe devices, and SAS SSDs.
Why direct attachment matters
The command must pass from the Privileged Execution Environment through the controller and driver to the target. USB bridges, RAID controllers, HBAs, docking stations, enclosures, virtualization layers, and vendor drivers can block, translate, or hide the required protocol.
A device can be detected normally and still reject firmware sanitization.
Device state
Firmware execution can depend on device security and readiness states, including:
- Supported sanitize or format capabilities;
- Frozen or locked ATA security state;
- Command-in-progress state;
- Controller passthrough support;
- Device namespace or subsystem configuration;
- Power and reset behavior.
DriveErase records the mode used and the returned result where available.
Verification and assurance
Firmware commands usually do not produce the same host readback evidence as a fixed-pattern overwrite. Assurance is based on the supported command, device response, completion status, protocol semantics, target identity, and any post-operation checks recorded by DriveErase.
A firmware method can have potential Clear or Purge applicability, but the final report determines the actual compliance statement. Some prerequisites cannot be established automatically, and the report can withhold a positive claim.
Failure handling
With Firmware Based, a failed firmware operation produces a failed erasure result for that device. With Firmware + Fallback, DriveErase prepares the device for the selected host overwrite after a failed firmware attempt and records which route completed.