crwdns2936637:0crwdne2936637:0 crwdns2853008:0crwdne2853008:0 crwdns2918746:0crwdne2918746:0

crwdns2944351:0crwdnd2944351:0How to safely and securely destroy data on SSDs and memory stickscrwdnd2944351:0crwdne2944351:0

crwdns2933797:0Philip Le Richecrwdnd2933797:0crwdne2933797:0

crwdns2936043:0crwdne2936043:0 crwdns2933505:0crwdne2933505:0 Philip Le Riche

crwdns2933769:0crwdne2933769:0
crwdns2933771:0crwdne2933771:0
crwdns2933801:0crwdne2933801:0
crwdns2866306:0crwdne2866306:0
Storage
Type
technique
Title
How to saely and securely destroy data on SSDs and memory sticks
Introduction
Data destruction on hard drives is comparatively easy, either by overwriting, though this may take a long time, or more securely by physcal destruction. However, with solid state disks (SSDs) and memory sticks, physical destruction is the only safe method. This is because data is not written to fixed locations like on a hard disk, but to spread across the least used memory cells in order to spread out the wear caused by every write operation.
The smart thing to do is to enable encryption before you write any sensitive data, then all you have to do is change the key or unlock code and destroy any record of it, and no one will be able to recover your data. On Windows, you can use Bitlocker, or FileVault on Macs. You can use either of those on memory sticks, or Veracrypt, which also works on Linux. You should ''always'' encrypt your memory sticks as they are so easily lost.
Time Required Min
crwdns2931273:0crwdne2931273:0
Time Required Max
crwdns2931273:0crwdne2931273:0
Difficulty
Easy
Conclusion
To reassemble your device - err, forget about it!
Author
Philip Le Riche
Public
crwdns2853046:0crwdne2853046:0

crwdns2943215:0crwdne2943215:0

  • Hammer x1 added.
  • Bosch COLD CHISEL 25X400 MM 1618600202 x1 added.
  • Dremel x1 added.

crwdns2935255:0crwdne2935255:0

  • In Progress added.
  • Community-Contributed Guide added.

crwdns2933623:0crwdne2933623:0

crwdns2933815:01crwdne2933815:0
crwdns2933769:0crwdne2933769:0
crwdns2933771:0crwdne2933771:0
stepid 288011 stepid 288011
crwdns2933815:02crwdne2933815:0
crwdns2933769:0crwdne2933769:0
crwdns2933771:0crwdne2933771:0
stepid 288013 stepid 288013
crwdns2933815:03crwdne2933815:0
crwdns2933769:0crwdne2933769:0
crwdns2933771:0crwdne2933771:0
stepid 288014 stepid 288014