Data Destruction HOWTO: Difference between revisions
No edit summary |
|||
| Line 7: | Line 7: | ||
==From storage== | ==From storage== | ||
Secure storage for devices needs to have its own inventory, which needs to be checked against the contents ''every time'' the storage is opened. This can be as simple as a list on the inside of the door, but we need to have it. | Secure storage for devices needs to have its own inventory, which needs to be checked against the contents ''every time'' the storage is opened. This can be as simple as a list on the inside of the door, but we need to have it. | ||
Currently (as of 2013-05-05) drives to be wiped are stored in a blue toolbox marked "Drives to be wiped". This toolbox should be kept locked. Whomever leads the events at FCS should hold the key for the duration of the event. Hopefully someone trustworthy at FCS can keep the key between events, otherwise we need to invent a secure way to keep the key. There is no inventory list for the contents of the box as yet (when I left all the drives had been or were being wiped) but we'll have to stick one in the box next week. | |||
=Wipe device= | =Wipe device= | ||
Revision as of 02:47, 5 May 2013
Get a device
At receiving
Data destruction, when done right, takes a long time. The donor is not likely to want to hang around and wait until it's done. Therefore, we need to store the devices securely while they wait for wiping. When we receive a donation, we need to get it to Evaluation ASAP. During Eval the drive(s) need to be pulled.
From storage
Secure storage for devices needs to have its own inventory, which needs to be checked against the contents every time the storage is opened. This can be as simple as a list on the inside of the door, but we need to have it.
Currently (as of 2013-05-05) drives to be wiped are stored in a blue toolbox marked "Drives to be wiped". This toolbox should be kept locked. Whomever leads the events at FCS should hold the key for the duration of the event. Hopefully someone trustworthy at FCS can keep the key between events, otherwise we need to invent a secure way to keep the key. There is no inventory list for the contents of the box as yet (when I left all the drives had been or were being wiped) but we'll have to stick one in the box next week.
Wipe device
Using DBAN
Using wipe
Using shred
https://www.gnu.org/software/coreutils/manual/html_node/shred-invocation.html
Shred is part of coreutils, and therefore should be present on most GNU/Linux installs by default (not on android, nor on other BusyBox-based userland)
Return device to inventory
- Label device as wiped
- Mark as such in inventory
- Place in appropriate location