DBAN

Darik's Boot and Nuke — Secure Multi-Pass Drive Wiping

Bootable (x86/x64) GPLv2

What It Does

DBAN is a self-contained bootable tool that securely erases hard drives by overwriting every sector with multiple passes of random data, zeros, or standardized wipe patterns. It ensures that data on a drive is unrecoverable by software-based forensic methods. When you decommission, donate, or repurpose a machine, DBAN is how you guarantee the previous data is gone.

Why You Need It

Deleting files or formatting a drive does not erase the data — it only removes the pointers to it. A free recovery tool can pull that data back in minutes. In enterprise IT and cybersecurity, proper data sanitization is a compliance requirement (NIST 800-88, HIPAA, PCI-DSS). Referenced in:

CompTIA A+ covers data destruction methods and their use cases. Every technician needs to know when to wipe vs. when to physically destroy a drive.

How to Install It

  1. Download the DBAN ISO from dban.org (or search for "DBAN download" — it was acquired by Blancco but the free ISO is still available from mirror sites).
  2. Write the ISO to a USB drive using Rufus (rufus.ie). Select the ISO, choose your USB drive, and click Start. Use DD image mode if Rufus asks — DBAN is a raw bootable image, not a standard ISO.
  3. Boot the target machine from the USB. Press F12 (or your machine's boot key) during POST to access the boot menu.
  4. DBAN loads a text-mode Linux environment. No operating system on the hard drive is involved — DBAN runs entirely from the USB.

How to Use It

1. Quick wipe with autonuke

At the DBAN boot prompt, type autonuke and press Enter. This automatically wipes every detected drive using the DoD Short method (3 passes). Walk away and come back — it runs unattended.

boot: autonuke

2. Interactive mode — select specific drives

Press Enter at the boot prompt without typing anything to enter interactive mode. Use arrow keys to navigate the drive list, press Space to select a drive, then M to change the wipe method, and F10 to start.

3. Choose a wipe method

MethodPassesUse Case
Quick Erase1Non-sensitive drives, fast reuse
DoD Short (5220.22-M)3Standard secure wipe, most common
DoD 5220.22-M7Higher assurance, slower
Gutmann35Maximum paranoia, extremely slow, rarely needed
PRNG StreamConfigurableRandom data fill, good balance

4. Verify completion

When DBAN finishes, it displays a summary screen showing each drive's status as [pass] (successfully wiped) or [fail] (errors encountered). A passing result means every sector was overwritten the specified number of times. Take a photo of this screen for your records — some compliance frameworks require proof of sanitization.

5. When to use DBAN vs. when SSD TRIM suffices

DBAN is designed for traditional spinning hard drives (HDDs). For SSDs, DBAN does not reliably reach all cells because of wear leveling and over-provisioning. For SSDs, use the manufacturer's Secure Erase command (via their utility software) or the ATA SECURITY ERASE UNIT command. Many SSD controllers also support hdparm --security-erase on Linux.

Common Gotchas

DBAN does not work properly on SSDs: Wear leveling means DBAN cannot guarantee all cells are overwritten. Some data may persist in spare cells. For SSDs, use the drive manufacturer's secure erase tool or hdparm. DBAN is for HDDs only.
autonuke wipes ALL drives: The autonuke command erases every drive DBAN detects, including the USB drive you booted from (if DBAN can see it) and any external drives. Disconnect drives you want to keep before booting DBAN, or use interactive mode to select specific targets.
Large drives take hours: A DoD 3-pass wipe of a 2 TB HDD can take 8-12 hours. A 7-pass wipe doubles that. Plan accordingly — start it at end of day and check in the morning. Do not power off mid-wipe; partial wipes leave recoverable data.
RAID arrays may not be visible: DBAN sees individual drives, not RAID volumes. Hardware RAID controllers may hide member disks. Disable or break the RAID in BIOS/RAID controller firmware before booting DBAN so it can see the individual drives.
Physical destruction is sometimes required: For classified or highly regulated data (government, defense, healthcare), software wiping may not meet policy requirements. NIST 800-88 defines three levels: Clear (1-pass), Purge (crypto-erase or degauss), and Destroy (shred/incinerate). Know which level your organization requires.