Processing Standards
Different organizations carry different risks. Our process selects, executes, and verifies the appropriate sanitization method for each data-bearing device.
01 / Purge-level approach
Security requirements vary by organization, regulation, and internal policy. We assess each digital storage medium by its technology, interface, capabilities, condition, and intended disposition before selecting the strongest supported sanitization method.
Where supported, our in-house processing system invokes device-native sanitize, secure erase, cryptographic erase, or block erase operations. These methods address storage areas that ordinary file deletion or formatting does not.
When no supported device-native Purge method is available, we perform a verified NIST Clear overwrite as the final logical fallback. If the Clear operation cannot be completed and verified, the storage medium is physically destroyed.
02 / NIST SP 800-88 Rev. 2
Our process follows the Clear, Purge, and Destroy framework in NIST SP 800-88 Rev. 2. We prioritize supported device-native methods, use NIST Clear only as the final logical fallback, and physically destroy media when sanitization cannot be verified.
NIST SP 800-88 Rev. 2 — Guidelines for Media Sanitization (opens in a new tab)Device-native · ATA
A device-native ATA secure erase command used when it is supported and appropriate for the media.
Device-native · ATA
An enhanced ATA erase operation that uses the drive manufacturer’s supported implementation.
Device-native · ATA
A standards-based device sanitize operation using block erase or cryptographic erase when supported.
Device-native · SCSI / SAS
A device-native sanitize operation available on supported modern SCSI and SAS media.
Device-native · NVMe
A native NVMe sanitize operation using the supported block, cryptographic, or overwrite action.
Device-native · NVMe
A supported NVMe format operation using secure erase settings or cryptographic erase.
Final fallback · Cross-interface
A verified overwrite through the normal read/write interface, used only when a supported device-native purge method is unavailable.
03 / Verification protocol
Our in-house software manages and verifies each sanitization operation and records the result against the storage medium’s unique serial number. A trained technician then independently reviews and verifies that result before it is carried into the final certificate. Any medium that cannot complete and pass verification is physically destroyed by shredding or crushing.
Reviewed by the SecureErase compliance team · Updated August 19, 2026
Start a conversation