Choose a Sanitization Approach and Method

Applies to: All editions; firmware approaches require Pro or higher

Approach selection

Choose the approach according to media type, interface, supported command path, data classification, assurance requirement, and device disposition.

Overwrite Based

Use overwrite-based sanitization when:

  • The target is an HDD;
  • The device is attached through USB or another path that does not support the required firmware command;
  • The active edition is Standard;
  • Policy accepts sanitization of the exposed logical range;
  • A repeatable host-driven pass sequence is required.

Overwrite is generally appropriate for functioning magnetic HDDs. On flash media, it does not establish coverage of controller-managed hidden or retired areas.

Firmware Based

Use firmware-based sanitization when:

  • The target is a directly attached compatible SATA SSD, NVMe device, or SAS SSD;
  • The device supports the selected command;
  • The controller path permits protocol passthrough;
  • The required assurance is better served by a device-managed operation;
  • The active license is Pro, Enterprise, or Audit.

A preflight-compatible selection can still fail at runtime because the device’s security state or controller access changes.

Firmware + Fallback

Use firmware with overwrite fallback when a compatible firmware method is preferred but an alternate host overwrite should be attempted if the command fails. Select the fallback profile with the same care as a primary overwrite method.

A successful fallback does not mean that the firmware method succeeded. The report identifies the actual route and its compliance consequences.

Device-type guidance

Device and connectionNormal approach
Direct SATA HDDOverwrite Based
Direct SAS HDDOverwrite Based
Direct SATA SSDFirmware + Fallback in Pro or higher
Direct NVMe deviceFirmware + Fallback in Pro or higher
Direct SAS SSDFirmware + Fallback in Pro or higher
USB HDDOverwrite Based
USB SSD or flash mediaOverwrite Based, with flash-coverage limitation
Virtual diskOverwrite Based, subject to virtual-storage limitations

Standards-related selection

A method’s name or Potential Compliance label describes an intended technique, not the final result. Actual compliance depends on device classification, completed coverage, command outcome, verification, error handling, and the evidence recorded after execution.