Data sanitization is the process of removing data from storage media so it cannot be recovered, while leaving the device usable for redeployment, resale, or lease return. It is the right choice when equipment still has value and the data on it must not leave the organization. Blue Revive provides data sanitization services matched to each media type, verified per device, and recorded by serial number so an auditor can trace every drive. To plan sanitization for an equipment refresh or lease return, Contact us.
What Is Data Sanitization?
Data sanitization is the deliberate, verified removal of data from storage media so that recovering it is infeasible for a given level of effort. The federal reference point is NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization, published in September 2025. It replaced Rev. 1, which had been in place since 2014 and is still quoted in many older contracts and policies.
NIST describes three sanitization methods. Clear applies logical techniques to user-addressable storage, protecting against simple, non-invasive recovery. Purge applies techniques that protect against recovery even with laboratory methods; for many modern drives this means built-in block erase or cryptographic erase commands. Destroy renders the media physically unusable.
Rev. 2 also separates logical techniques, which work through the device’s own interfaces and commands, from physical techniques, which act on the media itself. That distinction defines this page. Data sanitization uses logical techniques, so the device survives and can be reused or resold. When media must be physically destroyed, see Secure Data Destruction.
Rev. 2 changed emphasis in ways that matter to buyers. It is built around an organization’s sanitization program rather than a list of techniques, it points to current industry standards for media-specific methods, and it puts more weight on confirming that sanitization actually worked. It also treats multi-pass overwriting as unnecessary, which makes older references such as DoD 5220.22-M a sign of an outdated policy rather than a stronger one.
Data sanitization is one of the Destruction & ITAD services, and it is usually the step that makes value recovery from retired IT equipment possible.
Logical Methods Compared
Logical sanitization techniques differ in how they work, which media they suit, and how their results can be verified. The wrong technique for a media type can leave data behind while producing a record that says the device was sanitized. The table compares the main logical methods and their limits.
Two limits matter most. Overwriting an SSD does not reliably reach every block, so flash media needs a purge technique built for it. Cryptographic erase is only as strong as the drive’s encryption and how its keys were handled. A device that fails sanitization or verification is not passed for reuse; it moves to physical destruction.
Sanitize or Destroy?
The core decision is whether a device should be sanitized and reused or physically destroyed. Three factors drive it: the value of the device, the sensitivity of the data, and the condition of the media.
Device value
Sanitization makes sense when the equipment has reuse or resale value. Recent laptops, servers, and mobile devices often do. Older equipment may have little value left, and destruction followed by recycling may cost less than sanitizing and testing each unit.
Data sensitivity
Organizations set sanitization levels by the sensitivity of the data a device held. For most enterprise data, a properly executed and verified purge technique is accepted. Some organizations and contracts require physical destruction for the most sensitive categories regardless of value. That is a policy decision the client makes, and the sanitization plan follows it.
Media condition
Sanitization depends on the device working. A drive that will not respond, will not complete its sanitize command, or fails verification cannot be passed as sanitized. Those units are routed to physical destruction, and the record shows why.
In practice, most programs use both. Devices with value and working media are sanitized and verified. Devices that fail, or fall under a destroy-only policy, are destroyed. What matters is that every device ends with a record showing which path it took. Remarketing value from sanitized equipment is evaluated per asset based on age, condition, and market demand; it is a pathway to consider, not a promised return.
Our Data Sanitization Process
Scope and policy review
Blue Revive reviews the equipment involved, the media types, and the client’s sanitization policy. The review confirms which data categories require purge and which, if any, require destruction. The plan records those rules before any device is touched.
Collection and serialized intake
Devices are collected under chain of custody and recorded by asset tag and serial number at intake. Drives inside systems are recorded with the host device. The intake record becomes the reference for every later step.
Method selection by media type
Each device or drive is matched to a sanitization method suited to its media: hard drives, SSDs, NVMe, self-encrypting drives, and mobile devices each follow a different path. Devices that cannot be sanitized logically are flagged for destruction at this stage.
Sanitization
The selected method is run on each device. Completion status is captured per serial number. Interrupted or failed runs are recorded rather than retried silently.
Verification
Each device is checked to confirm sanitization succeeded, using the verification suited to the method. Devices that pass are released for reuse or resale. Devices that fail are routed to physical destruction.
Exception handling
Failed, unresponsive, and destroy-only devices move to secure data destruction under the same custody record. The reason for each exception is recorded. No device leaves the process without a final status.
Reporting
The client receives a sanitization record listing each device by serial number, the method used, the verification result, and the final disposition. Records for destroyed exceptions are included. The report ties back to the intake record.
Regulatory Framework
Most data protection laws do not name a sanitization technique. They require that data be protected through disposal or reuse and that the organization can show it was. The table summarizes the rules that most often shape a sanitization program.
Documentation You Receive
Documentation is what turns sanitization from a claim into evidence. Each record is built around the questions an auditor or privacy officer is likely to ask: which devices, which method, did it work, and where did each device end up.
Serialized sanitization record: each device and drive by asset tag and serial number, so the record can be matched to the asset register
Method by device: the technique used for each media type, so a reviewer can confirm flash media was not simply overwritten
Verification result: pass or fail per device, which answers whether sanitization actually worked
Exception list: devices routed to destruction and the reason, so no device is unaccounted for
Chain-of-custody record: from collection through final disposition
Final disposition: reused, resold, returned to lessor, or destroyed, per device
For how sanitization records roll up with other documentation across a program, see Compliance & Reporting.
Frequently Asked Questions
What is the difference between data sanitization and data destruction?
Data sanitization uses logical techniques, such as block erase or cryptographic erase, to remove data while keeping the device usable for reuse or resale. Data destruction physically destroys the media so it cannot be used again. Sanitization preserves value; destruction gives the highest assurance when a device has no reuse value or a policy requires it.
Is overwriting enough for SSDs?
No. Overwriting writes to the areas a computer can address, but SSDs use wear leveling and over-provisioning, which leave data in blocks the host cannot reach. Flash media should be sanitized with a purge technique built for it, such as the drive’s sanitize command or cryptographic erase on a self-encrypting drive, followed by verification. Verification confirms the purge worked.
What changed in NIST SP 800-88 Rev. 2?
Rev. 2, published in September 2025, replaced the 2014 Rev. 1. It focuses on building an organizational sanitization program, points to current industry standards for media-specific techniques, and puts more weight on confirming sanitization worked. It also treats multi-pass overwriting as unnecessary. Policies that still cite Rev. 1 or DoD 5220.22-M are worth updating. Rev. 1 has been withdrawn.
Do you still need DoD 5220.22-M wiping?
No. DoD 5220.22-M is a legacy reference, and its multi-pass overwrite approach was designed for older hard drives. Current guidance in NIST SP 800-88 Rev. 2 treats multiple overwrite passes as unnecessary and does not rely on overwriting for flash media. A policy that requires DoD wiping should be reviewed against current NIST guidance. Updating it usually simplifies the program.
What happens to a drive that fails sanitization?
It is not released for reuse. A drive that will not respond, cannot complete its sanitize command, or fails verification is routed to secure data destruction under the same chain of custody. The sanitization record lists it as an exception with the reason, so every device has a final, documented disposition. The client sees exactly which devices were destroyed and why.
Can sanitized equipment be resold?
Often, yes. Sanitization is what makes remarketing possible, because the device keeps its value. Whether a given device has resale value depends on its age, condition, configuration, and market demand. Value is evaluated per asset rather than promised. Equipment with little remaining value is usually more economical to recycle. The sanitization record travels with each resold device’s history, so the data question is closed before the device leaves.
How do I prove to an auditor that devices were sanitized?
A serialized sanitization record shows each device by serial number, the method used, the verification result, and its final disposition. Matched against the asset register, it lets an auditor trace any retired device from intake to outcome. The chain-of-custody record shows who held the device at each step. Exceptions routed to destruction appear on the same record, so nothing falls outside the file.
Next Steps
A sanitization plan starts with the equipment, the media types, and your policy on which data requires purge or destruction. From there, each device follows a documented path to reuse, resale, or destruction. To plan data sanitization for a refresh, lease return, or retirement, Contact us.
