Firmware-Based Sanitization with Overwrite Fallback

Applies to: Pro, Enterprise, and Audit

Purpose

Firmware + Fallback attempts the configured device-firmware sanitization method first. If the firmware method fails or cannot complete, DriveErase re-prepares the target and runs the selected overwrite profile.

This approach can improve operational completion where firmware support is inconsistent, but it does not make the two outcomes equivalent.

Execution sequence

  1. Validate the target and requested firmware method.
  2. Attempt the firmware operation.
  3. Record the firmware response and failure reason when unsuccessful.
  4. Re-establish host access to the target where possible.
  5. Run the selected overwrite profile across the exposed logical range.
  6. Apply the overwrite method’s verification policy.
  7. Record the actual route, outcome, coverage, and compliance result.

Result interpretation

Possible outcomes include:

  • Firmware method completed successfully;
  • Firmware method failed and overwrite fallback completed successfully;
  • Firmware method failed and fallback completed but did not satisfy certification criteria;
  • Firmware method failed and fallback also failed or remained incomplete.

A successful fallback can still produce a warning because the preferred firmware operation failed. The compliance statement is based on the method that actually completed.

Flash-media implication

When fallback is used on an SSD, NVMe device, or other flash storage, the overwrite covers the exposed logical range. It does not inherit the device-level coverage that the failed firmware method might have provided.

Selecting the fallback profile

Choose the fallback before starting the job. Use a profile approved for the device and disposition. A modern one-pass Clear profile can be more appropriate than a large historical pass count, but a positive Clear result remains subject to device classification and method-specific evidence.

When not to use fallback

Do not use fallback where policy requires a successful device-managed Purge result and logical overwrite is not an acceptable substitute. In that case, treat the firmware failure as a failed sanitization and move the device to an approved alternative method or physical destruction.