DoD 5220.22-M and Gutmann are both overwrite methods for erasing hard drives. DoD 5220.22-M overwrites data in 3 passes (or 7 in the extended "ECE" version), while the Gutmann method uses 35 passes. For any modern hard drive, the extra passes of Gutmann add hours or days without making the data meaningfully harder to recover; a 3-pass DoD wipe, or even a single verified pass, is enough. For SSDs, neither method is the right tool. This guide explains where each method came from, what the passes do and how to choose.
Quick comparison
| DoD 5220.22-M | DoD 5220.22-M ECE | Gutmann | |
|---|---|---|---|
| Passes | 3 | 7 | 35 |
| What is written | A character, its complement, then random data | Two 3-pass DoD runs with a random pass between them | 4 random passes, 27 fixed patterns, 4 random passes |
| Designed for | Hard drives of the 1990s and later | Same, with extra margin | Old MFM/RLL-encoded hard drives |
| Time on a 1 TB hard drive | Roughly 6 to 12 hours | Roughly 14 to 28 hours | Several days |
| Useful on modern hard drives? | Yes | Yes, but slower than needed | Works, but massive overkill |
| Right for SSDs? | No | No | No |
Times are estimates and depend heavily on the drive's speed and whether each pass is verified.
What is DoD 5220.22-M?
DoD 5220.22-M is the US Department of Defense's National Industrial Security Program Operating Manual (NISPOM). Older editions included a table of approved methods for clearing and sanitizing media, and the overwrite procedure from it became widely known as "the DoD wipe":
- Pass 1: overwrite every sector with a fixed value (for example, zeros).
- Pass 2: overwrite with the complement of that value (for example, ones).
- Pass 3: overwrite with random data, then verify.
The 7-pass ECE variant runs the 3-pass method, then a random pass, then the 3-pass method again. Software uses it when people want more margin.
It is worth knowing that later revisions of the manual stopped specifying an overwrite pattern and point to other guidance instead. When software offers "DoD 5220.22-M", it means the well-known overwrite pattern, not a current certification. Saying a drive was wiped "to DoD 5220.22-M" describes the method used, nothing more.
What is the Gutmann method?
Peter Gutmann, a computer scientist, published a paper in 1996 on recovering data from magnetic media. Hard drives of that era used encoding schemes (MFM and RLL) where faint traces of earlier data could, in theory, be read with specialist lab equipment. He designed 35 overwrite patterns so that whatever encoding a drive used, some of the passes would target it.
Gutmann himself later pointed out that running all 35 passes on a modern drive makes little sense. Drives since the late 1990s use very different encoding and pack data so densely that the patterns aimed at old encodings do nothing extra. A few random passes are the part that matters.
How many passes do you actually need?
For a modern hard drive, the widely cited NIST SP 800-88 guidance treats a single overwrite pass as sufficient to "clear" data against recovery with software tools, and there is no published demonstration of recovering meaningful data from a modern hard drive after one full overwrite. In practice:
- One verified pass stops recovery software and is fine for most personal use.
- DoD 3-pass is a reasonable choice if you want extra reassurance or a recognized method name for your records.
- DoD 7-pass is for people who are required to use it or simply prefer more margin and have the time.
- Gutmann 35-pass is mostly a matter of preference or policy. It is not harmful on a hard drive, just very slow.
What matters more than the pass count is that the whole area is actually overwritten, including bad-sector handling and verification. A method that reads each pass back to check it was written is better evidence than a high number of unverified passes.
Why neither method suits SSDs
Both methods assume that writing to a location replaces what was there. SSDs and USB flash drives use wear leveling and keep hidden spare space, so overwrites often land in different physical cells and the old data can survive in places software cannot reach. Repeating passes just adds wear. For an SSD, the right approach is the drive's own secure erase or sanitize command, usually through the manufacturer's tool, as explained in how to securely erase an SSD. For flash sticks, see how to wipe a USB flash drive.
Built-in Windows options
Windows does not offer DoD or Gutmann by name, but it has two overwrite tools:
cipher /w:C:\overwrites free space in three passes (zeros, 0xFF, random). It does not touch existing files. See how to wipe free space in Windows.diskpartfollowed byselect disk Nandclean allwrites zeros over an entire disk once. That is a single pass, which is adequate for a hard drive you are disposing of.
Neither produces a report, and neither verifies the passes.
Choosing a method in Evidence Wipe
Evidence Wipe's SSD-Aware Erasure detects each drive's type first. On hard drives you can choose DoD 5220.22-M (3 pass), DoD 5220.22-M ECE (7 pass) or Gutmann (35 pass), and every pass is read back and verified. On SSDs and NVMe drives it does not offer many-pass overwrites; it uses one verified pass plus TRIM, following NIST 800-88 guidance, and reminds you that the manufacturer's sanitize tool is the most complete option for retiring an SSD. Each shred, wipe or erase ends with a Verification Report that records the method, the drive and the time. See the feature list for more.
Frequently asked questions
Is one pass enough to wipe a hard drive?
For modern hard drives, a single full overwrite stops recovery with software tools, and NIST SP 800-88 treats it as sufficient for clearing. Extra passes add reassurance and time rather than meaningful protection.
Is DoD 5220.22-M still a current standard?
Later revisions of the DoD manual no longer specify an overwrite pattern. The name now refers to the well-known 3-pass method, and many policies reference NIST SP 800-88 instead.
Should I use the Gutmann method on an SSD?
No. Gutmann was designed for old hard drive encodings. On an SSD it adds wear without reaching hidden flash areas; use the drive's secure erase or sanitize command instead.
