You should use a 'secure erase' utility (e.g.
HDDErase. This is more secure than using an overwrite program, e.g. DBAN.
There are several advantages to using a secure erase utility:
1. An overwrite program cannot clear 'spare', 'bad', 'pending' or 'reallocated' sectors. These sectors could remain accessible to data recovery tools.
2. On an SSD, you waste flash cycle life - whereas on an SSD secure erase, pre-erases all the flash restoring factory performance.
3. It's faster to run a secure erase - with a host based overwrite tool, the PC has constantly dump data to the drive (on low end PCs, e.g. atoms, this can be a bottleneck, as the drive can be faster than the system bus) With a secure erase tool, no data is sent to the drive, the erase is performed by the drive's internal CPU.
4. A secure erase utility can guarantee that the drive is securely wiped. An overwrite tool can't unless you verify the whole drive. HDDerase 'locks' the drive, before erasing, and only 'unlocks' the drive when erasure is complete. A 'locked' drive will not respond to normal commands, until it is unlocked. So, if there is a power failure, or spontaneous reboot - the drive will not be usable if the erasure didn't complete (just re-run the erasure and let it finish to 'unlock' the drive). Note: there is a potential pitfall here - some BIOSs have a bug, where if they detect a 'locked' hard drive, will refuse to boot. If you have such a defective BIOS and the erase is interrupted part-way, your comp may not reboot, and you'll have to transfer the drive to a PC with a working BIOS, to unlock it.