Technique versus method
In everyday speech, method, and technique are used interchangeably. In operational work the difference matters. A sanitization method names the action and the strength it must reach: clear, purge, or destroy, on the scale of NIST SP 800-88. A sanitization technique is the concrete mechanism that delivers that action on a specific medium: overwriting sectors, degaussing magnetic domains, calling the controller's erase function, destroying an encryption key, or shredding the device.
The consequence is practical. Policy is written in methods, and execution happens in techniques. A policy may require that drives from departing staff be purged, but the engineer holding a failing SSD chooses the mechanism. One technique can even serve two methods: degaussing purges a magnetic disk while destroying it.
The core techniques
Five mechanisms cover nearly all sanitization in practice, and each has a physical basis that determines where it works. On a functional magnetic disk, one overwrite pass defeats software recovery. Extra passes add time, not assurance.
Each mechanism answers a different kind of remanence: the data that survives on a medium after ordinary deletion.
| Technique | How it works |
|---|---|
| Overwriting | Writes a fixed pattern over addressable storage with standard commands |
| Degaussing | A strong magnetic field erases the domains; the drive is destroyed |
| Block erase and drive-native sanitize | Run by the controller, reaching cells the host cannot address |
| Cryptographic erase | Destroys the encryption key, leaving every sector unreadable ciphertext |
| Physical destruction | Shredding, disintegration, pulverization, or incineration |
Why no single technique fits every medium
What makes a technique correct is not its strength on paper but the physics of the medium. An overwrite pass that leaves nothing recoverable on a hard disk does not reach the cells an SSD controller has taken out of view.
Flash defeats overwriting. Wear leveling and over-provisioning keep part of the physical cells outside the host's address space, beyond the reach of any overwrite command. The technique of record for SSDs is the controller's sanitize function or a cryptographic erase. A drive too damaged to run either goes straight to destruction.
Cloud storage fails every physical technique for the opposite reason: the tenant never touches the medium. Whether the blocks of a deleted volume are zeroed before reuse is a property of the platform. Erasure is therefore either cryptographic, by destroying the key, or contractual, under the provider's commitments.
Techniques by medium
Each medium rules out some techniques. A ✓ marks a technique that works on that medium, and a ✗ marks one that fails or cannot be applied. Cryptographic erase counts only where the medium was encrypted from first use. For SSDs, the controller's own sanitize function is the other technique of record.
| Medium | Overwriting | Degaussing | Cryptographic erase | Destruction |
|---|---|---|---|---|
| Hard disk drives | ||||
| SSDs and flash media | ||||
| Magnetic tape | ||||
| Optical media | ||||
| Cloud storage |
Strength, verification, and failure
A technique is judged against the strength its method demands. Clearing must defeat ordinary software recovery tools. Purging must make recovery infeasible even in a laboratory. Destruction must defeat anyone. An overwrite that is enough to reuse a laptop internally becomes inadequate when that laptop is resold. The technique is the same, but the verdict changes because the destination changed.
Execution without verification is an assumption, not sanitization. After overwriting, a sample of the space is read back to confirm that nothing recognizable returns. A block erase records its completion status. Destruction is documented by serial number, method, and chain of custody. Within a media sanitization program, each of these records is kept with the job. A drive that fails halfway through an overwrite accepts no more commands and goes to destruction.
Most failures come from applying a technique to a medium it was never designed for. Multi-pass overwrites on an SSD wear the drive while retired cells keep their data. Degaussing flash or optical media does nothing. Coarse shredding of an SSD can leave fragments with readable data, so shred size must match the areal density. Quick formats presented as sanitization, cryptographic erases with a second live copy of the key in a backup, and cloud volumes assumed clean because the console said deleted are also common. Each technique was run honestly and proved nothing. The medium decides the outcome, not the effort.
Choosing under constraints
Between policy and action sits an engineering decision that weighs practical constraints against the required strength. Check the points in order:
- 1
Confirm the medium
Identify the storage type and whether the medium still accepts commands. A drive that no longer responds has one technique left: destruction.
- 2
Match the technique
Using the table above, rule out techniques the medium cannot support, such as overwriting on flash.
- 3
Weigh throughput
Overwriting takes hours per terabyte, while a cryptographic erase takes seconds.
- 4
Check key management
Cryptographic erase presumes encryption from first use and no surviving key copies in backup or escrow.
- 5
Account for cost and location
Degaussers and shredders are costly, and destruction ends reuse value. A branch without that equipment relies on software erasure or courier custody.
Where to start
Start with the medium, not the tool. List the devices that leave your organization, the storage type inside each one, and the technique that works on it. Treat a deleted file as still present until one of those techniques has run.
Erasure is only finished when the record says so. Keep the method, the technique, the serial number, and the person who signed off with each device.
The strongest technique is the one that matches the medium, not the one that runs longest.
Anexet Team