Slashdot Mirror


Confidential Data Not Safe On Solid State Disks

An anonymous reader writes "I always thought that the SSD was a questionable place to store private data. These researchers at UCSD's Non-Volatile Systems Laboratory have torn apart SSDs and have found remnant data even after running several open source and commerical secure erase tools. They've also proposed some changes to SSDs that would make them more secure. Makes you think twice about storing data on SSDs — once you put it on, getting it off isn't so easy."

56 of 376 comments (clear)

  1. Nuke it from orbit by ColdWetDog · · Score: 2, Funny

    It's the only way to be sure.

    --
    Faster! Faster! Faster would be better!
    1. Re:Nuke it from orbit by DigiShaman · · Score: 3, Funny

      Or in a microwave. That seems to destroy the gates on the chip. 10 seconds on High should be enough. Just be sure to only place the PCB and not the entire drive as they can contain lots metal.

      --
      Life is not for the lazy.
    2. Re:Nuke it from orbit by MachDelta · · Score: 3, Interesting

      The most fun I ever had disposing of a HDD was when I worked as a mechanic. One of the POS systems was being replaced and the drive in it was going to be shredded. It was a slow day then, so I bugged our IT guy to let me have a crack at it. With an evil grin, I took it out to a workbench, stuffed it in a vice, and beat the piss out of the casing with a hammer. Once it was suitably mangled I started taking it apart with a prybar and screwdriver (gotta save those magnets!) until all I had left was the stack of platters. I took them to the 10 ton press in the back and squished it into a platter-pizza. Then I went to the corner and took the Oxyacetylene torch to that sum'bitch, entertaining myself by doodling molten penises and happy faces in it.

      Best day at work EVAR.

    3. Re:Nuke it from orbit by lgw · · Score: 4, Insightful

      TrueCrypt volume inside a TrueCrypt volume

      You, dawg, I heard you liked TrueCrypt.

      The headline should just read "Confidential data not safe on unencrypted disk". Modern hard drives also arean't as easy to 100% delete as one might think - once a sector gets "spared out" there's no easy way to delete it, and there will still be readible data there. That just happens a lot less frequently than SSD load/wear balancing.

      Of course, any media can be adequetly destroyed by shredding - if you really care, this isn't a problem to solve with software.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    4. Re:Nuke it from orbit by Calydor · · Score: 4, Funny

      This is when you tell us he re-assembled it, loaded up some Linux Drive Recovery program and pulled all the data to safety, right?

      --
      -=This sig has nothing to do with my comment. Move along now=-
    5. Re:Nuke it from orbit by vadim_t · · Score: 3, Informative

      And what good is that?

      Again, this is a SSD, not a hard disk. The PCB contains both the interface and the data storage parts. If you microwave that, you've destroyed everything that was important. It's no use to unsolder anything, the flash chips themselves are destroyed by microwaving.

      The part you would skip on microwaving is the metal casing, which contains no data.

    6. Re:Nuke it from orbit by trentblase · · Score: 2

      The headline should just read "Confidential data not safe on unencrypted disk"

      The headline should just read "Confidential data not safe"

    7. Re:Nuke it from orbit by d6 · · Score: 2

      should have called the vendor and done an RMA on it afterwards.

      "It just quit working, I don't understand..."

  2. My secure erase method still works! by MetalliQaZ · · Score: 3, Funny

    1 electric drill, 1 work bench, and some bored interns.

    --
    "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
    1. Re:My secure erase method still works! by loshwomp · · Score: 3, Funny

      And here I thought you were going to bore holes in the SSDs. Boring holes in the interns is just cruel.

  3. Blend it... by Goffee71 · · Score: 2, Funny

    ... try reading anything from the ensuing dust.

    --
    If he's the Walrus then can I be a penguin please?
  4. How about by Anrego · · Score: 4, Insightful

    Encrypting it?

    Is taking data off really an issue anyway. If it's confidential data, destroy the disk when you need to dispose of it. Not repurposing or re-selling hardware with sensitive information on it sounds like a no-brainer.

    1. Re:How about by initdeep · · Score: 4, Funny

      STOP USING LOGIC ON /.

    2. Re:How about by Guspaz · · Score: 2

      SandForce SSD controllers encrypt all data as it hits the SSD. That does nothing to protect against plugging the drive into a computer and using it (a secure delete would handle that), but it *does* protect against people accessing the NAND chips directly. That and the fact that SandForce drives use compression/deduplication/other tricks and properly support secure erase would make it exceedingly difficult to recover data.

    3. Re:How about by camcorder · · Score: 2

      One of the SSDs out of 8 they tested has built in encryption. And according to article although it's faster to sanitize data (ie. sanitizing the encryption key), since leftover encrypted data might leave cryptanalysis options, it might be insecure. (though theoretically it is.)

    4. Re:How about by noidentity · · Score: 2

      A problem with full-disk encryption is that it's hard to verify that it's really encrypted on the disk. You have to trust that the manufacturer didn't cut corners and just fake encryption, or botch implementation.

    5. Re:How about by mysidia · · Score: 2

      You had better choose your random number generator wisely, or your data may not be as secure as you think.

      You don't have to use a "random number generator". You can capture truly random values, since you only have to do it once.

      For example, you can hook up a USB geiger counter, place it near a decaying radioactive sample, and collect values measuring the nanosecond timings between photons triggering the counter.

      Why not just use a proven encryption method to encrypt everything, then even if someone acquires all of your drives,

      There is no such thing as proven encryption. Any encryption algorithm is subject to possibly being broken. And having vulnerabilities. It is possible someone has already broken AES and can decrypt any ciphertext, but they have just not revealed that fact to the public yet.

      Entropy methods of masking data involving truly random values cannot be "cracked" by brute forced by finding a hole in a cipher, because there is no cipher.

      the data is still secure. (assuming proper key management, of course).

      The data is more secure than if it had been plaintext. The data is less secure than if the drive had been destroyed

      With a 'key drive' or 'one time pad' that is not disposed with the drive, the data is just as secure as if the drive had been destroyed, assuming a valid implementation of the OTP method.

    6. Re:How about by Anonymous Coward · · Score: 2, Insightful

      Congrats... I think you've just built a hard drive sized One Type Pad. Unless I'm missing something, this is horribly vulnerable if an attacker can "borrow" your disk at multiple snaps in time (as you are essentially reusing the one time pad everytime you delete/modify files, so the attacker can now calculate oldfile xor newfile ... if I know at snapshot one I hadn't sent you somebigimage.jpg and at snapshot two, I can basically xor my two snapshots and then xor somebigimage.jpg over all the non-zero fragments and see what file you deleted that freed up space for somebigimage (oversimplified but still and issue)

  5. Treat it like any other secure system by Brett+Buck · · Score: 2

    The solution is the same as hard drives in any secure system - use it, and when you are done, destroy it. Say you get 3 years out of an SSD, the cost of replacing it is trivial over the long haul. Nobody serious about security erases conventional platter HDs and hopes that's good enough.

    1. Re:Treat it like any other secure system by somersault · · Score: 2

      "Trust but verify"? Verification results from the exact opposite of "trust" :p You're right to verify, but saying stuff like that sounds silly..

      --
      which is totally what she said
    2. Re:Treat it like any other secure system by Solandri · · Score: 5, Insightful

      From what I've seen, it's not the end-of-life disposal of drives which leads to this type of data leak. It's when a drive dies under warranty and you send it to the manufacturer for a replacement. Since it's non-functional, you can't erase it. Since you need to return it without any signs of abuse for a warranty replacement, you can't destroy it.

      The manufacturer usually just fixes it, and sells it as a refurb / sends it out as a replacement drive for others which have failed under warranty. They just do a quick format, or sometimes even don't bother formatting, before sending the fixed drive out. Meaning the new recipient of your old drive has all your data.

    3. Re:Treat it like any other secure system by jittles · · Score: 4, Informative

      The lack of security of SSD's is not new! So unoriginal, in fact, that Truecrypt.org doesn't even recommend that you encrypt an SSD drive!

    4. Re:Treat it like any other secure system by causality · · Score: 3, Insightful

      "Trust but verify"? Verification results from the exact opposite of "trust" :p You're right to verify, but saying stuff like that sounds silly..

      Verification is after-the-fact. Prior to that, the vendor could still do something dishonest like fail to deliver on its promises. You're trusting them not to do that as indicated by your willingness to do business with them in the first place. Verification is an attempt to check against not only dishonesty on their part but also well-intentioned mistakes that wouldn't strictly be issues of trustworthiness.

      It's sort of like when I deposit cash at a bank. If I tell them "this is 200 dollars, please put it into my account" they are going to count the money. I don't take that as an accusation that I am trying to deceive them, because it isn't. It's a standard practice because multiple pairs of eyes are more likely to catch both honest mistakes and deliberate deception. That's an example of "trust but verify".

      It's not really so silly and it's far less extreme than "I want to be involved in each step of the process so I can watch your every move". That would be distrust.

      --
      It is a miracle that curiosity survives formal education. - Einstein
    5. Re:Treat it like any other secure system by camperdave · · Score: 2

      You should pull every $RANDOMth item off a production line because if your production process has a fault cycle that is a multiple of N items long you'd never catch it.

      --
      When our name is on the back of your car, we're behind you all the way!
    6. Re:Treat it like any other secure system by the+phantom · · Score: 2

      If you are that concerned about the security of your data, then you either encrypt all of your data, in which case it probably doesn't matter what happens to the drive after you get rid of it; or you destroy the drive and suck up the cost of a new one (or you are a large customer, and have an agreement with the vendor which allows you to destroy the drive and get a replacement). Security, convenience, or low cost---pick one.

    7. Re:Treat it like any other secure system by WuphonsReach · · Score: 2

      If you are that concerned about the security of your data, then you either encrypt all of your data, in which case it probably doesn't matter what happens to the drive after you get rid of it; or you destroy the drive and suck up the cost of a new one (or you are a large customer, and have an agreement with the vendor which allows you to destroy the drive and get a replacement). Security, convenience, or low cost---pick one.

      Exactly. Large companies generally have agreements to cover this. A lot of them just unscrew the cover plate off the drive that contains the serial number and model number information and only send that back to the manufacturer.

      --
      Wolde you bothe eate your cake, and have your cake?
    8. Re:Treat it like any other secure system by geekoid · · Score: 2

      For easy of use, be sure to encrypt everything twice with ROT13

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  6. Encryption by __aardcx5948 · · Score: 2, Insightful

    It doesn't matter if you can get hold of ALL of the data, if it's encrypted you're fucked. Nothing to see here, move along.

  7. for the truly paranoid by Seggybop · · Score: 2

    I thought we'd already agreed that the only way to be really sure that your data is gone is to physically destroy the drive. If you've got data that's really so sensitive that someone's going to spend serious resources to extract it, the actual price of a drive is nothing. Smash it and call it good.

  8. wipes are vendor specific by gad_zuki! · · Score: 4, Informative

    I know OCZ has its own wipe utility and I believe intel too. Using wiping software designed for mechanical disks makes absolutely no sense and the results from this study are 100% predictable. Oh your Gutmann wipe pattern for circa1991 MFM drives doesn't wipe SSDs? You don't say! If you needed to securely wipe one, use the proper tool.

    That said, it would be nice if there was some standard way of doing this.

    1. Re:wipes are vendor specific by mlts · · Score: 2

      What would be nice is to have the ATA erase command standardized, so this can be easily done.

      Command gets handed to the drive controller, controller does the erasing the right way, where on a hard drive, it zeroes out sectors, even the ones on the bad sector relocation table, and sectors marked as bad. On a SSD, it zeroes out everything regardless of the status with regards to wear leveling.

      Even better would be having the drive controller encrypt all data, storing the key as a value in NVRAM. Then when it gets handed an erase command, it replaces the key stored with one randomly generated.

      Even better would be to have the drive controller to have its own free space bitmap. After being zeroed, if a sector is read without being written to, the controller returns just zeroes, regardless of the actual data present. If the sector was written to, the controller marks it as used in the bitmap and then returns the sector's data on subsequent writes. This way, an erase command can be almost immediate (flagging everything in the bitmap as free), and outside of yanking the controller and looking at the platters/cells, there is no way to retrieve the data that was erased. Bonus points if the controller zeroed out data in the background.

    2. Re:wipes are vendor specific by causality · · Score: 3, Funny

      Using wiping software designed for mechanical disks makes absolutely no sense and the results from this study are 100% predictable.

      If people were never surprised by predictable things the entire news industry would take a nosedive and be reduced to a shadow of its current self. It'd fuck up the economy!

      --
      It is a miracle that curiosity survives formal education. - Einstein
    3. Re:wipes are vendor specific by blueg3 · · Score: 2

      That was their question, too, and they address it in the paper.

  9. Re:How is that different than spinning disks? by firesyde424 · · Score: 2

    You know, I've never understood this one. If you have written a zero to every sector on the hard drive, including the hidden space, how in the world is it possible to recover any data at all?

  10. thermite will fix that by WhiteDragon · · Score: 4, Insightful

    Thermite will fix everything! [s/fix/destroy] :-)

    --
    Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
  11. truecrypt by SharpFang · · Score: 5, Insightful

    encrypt the data before writing. at no point in its existence will it appear anything but white noise to unauthorized parties.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  12. Re:How is that different than spinning disks? by Zironic · · Score: 3, Informative

    It's because the bits in the harddrive aren't actually binary but rather values that are intepreted as 1 or 0. For instance a value of 0.6 would be interpreted as 1 and 0.4 would be 0.

    This means that if you look at the exact value rather then the interpretation you can make a guess at what values it has been before.

  13. Re:dd by Zironic · · Score: 3, Informative

    According to RTFA they can recover almost 100% of the data from a 0'd HD, 90% of the data from a randomed HD and 1-10% from a HD that has run extremely extensive random HD passes (Like Gutmann)

    This is due to SDD's working differently then the standard HD's.

  14. Re:How is that different than spinning disks? by Rashkae · · Score: 3, Informative

    By scanning the surface of the platter with specialized equipment, it's possible to detect residual magnetization 'around' the area written by the drive head and determine where there used to be a bit. Actually using this technique to recover anything outside of a laboratory experiment (where the drive was only written to and erased with 0's once) is a myth, however. No one does this, not even CTU.

  15. It is difficult by crow · · Score: 2

    You can't do a secure erase from software, because data may still exist in blocks that were remapped by the firmware due to errors or for write leveling. When you write to an SSD, the new data goes in a free block, and the old block is marked free. To do a real secure erase, you have to work with the SSD firmware, and even then, you can't be sure if data may still exist on bad blocks that can't be written to.

    So the only way to be sure is to physically destroy it, and flash is reliable enough that it's difficult to be certain that you've truly destroyed it.

    So as everyone else is saying, the only good solution is to encrypt everything, and don't store the keys in flash.

  16. Re:How is that different than spinning disks? by gstoddart · · Score: 3, Informative

    You know, I've never understood this one. If you have written a zero to every sector on the hard drive, including the hidden space, how in the world is it possible to recover any data at all?

    Essentially, residual magnetism and other sciency-bits.

    Suffice it to say, simply writing a bunch of zeros doesn't erase all traces of what was on. With old school HDs, you needed to write random data to each location multiple times -- there's a DoD spec for doing it (DoD 5220.22-M).

    I believe the article is saying that it doesn't seem to work with SSDs.

    --
    Lost at C:>. Found at C.
  17. I think I'm safe by lxw56 · · Score: 5, Funny

    I challenge anyone to find my MicroSD card. I've conducted extensive security audits to verify that no attacker, even one with inside information, can gain electronic or physical access to the disc.

    1. Re:I think I'm safe by RapmasterT · · Score: 4, Funny

      I challenge anyone to find my MicroSD card. I've conducted extensive security audits to verify that no attacker, even one with inside information, can gain electronic or physical access to the disc.

      Translation: "I lost the tiny little bastard and can't fucking find it!"

    2. Re:I think I'm safe by SharpFang · · Score: 2

      thanks for update.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  18. Re:what, you don't have a firepit? by tragedy · · Score: 2

    Sure, but the drive casing probably didn't break open. It would have been made of aluminum, most likely, which isn't the best heat sink, but is better than nothing. The heat it was exposed to was probably intense but brief. So, the platters inside the drive were probably only exposed to a small amount of heat for a short period of time. The overnight fire that the grandparent post referred to would be hundreds of times longer and probably hotter too.

  19. Summary by Orgasmatron · · Score: 5, Informative

    Block storage devices have more capacity than they report. Magnetic disks keep a small reserve of unallocated blocks as a hedge against blocks that fail in use. SSDs keep a much larger reserve because they can only erase in increments that are relatively large compared to their block size.

    If you overwrite a sector on a magnetic disk, you will almost always destroy all traces of the old data. The exception is when the drive thinks the old sector has failed or is about to fail, in which case you get an entirely new sector, and your old data is still (possibly) on the old sector. Attacks using magnetic force microscopes to read data from track fringes were possible a decade ago, but there is no reason to think it is possible on a modern drive.

    If you overwrite a sector on a SSD, the SSD gives you a whole new block from a list of free blocks, and adds the address of the old block to the list of deleted blocks. Blocks are moved from the deleted list to the free list when the SSD has some free time, or when one is really needed. There is currently no mechanism to force the SSD to actually erase a sector.

    This is all known, and there are mechanisms built into the specs to provide a secure erase. What their research is showing, however, is that these mechanisms don't always work. A number of them are buggy, and at least one just plain lies, claiming to have done the secure erase, but actually just doing the normal pointer update trick just like any other write.

    --
    See that "Preview" button?
  20. Re:How is that different than spinning disks? by bitslinger_42 · · Score: 2

    It is important to note the section on feasibility in that Wikipedia link... Peter Gutmann did the original (public sector) research on recovering overwritten data on MFM hard drives with very low byte densities (by today's standards). Peter revisited the subject and found that a single overwrite pass, even if only zeroing out every bit, was sufficient to defeat the technique on "modern" drives (i.e. drives larger than 15GB and made in the past 5-7 years).

  21. Re:How is that different than spinning disks? by blueg3 · · Score: 2

    This means that if you look at the exact value rather then the interpretation you can make a guess at what values it has been before.

    In theory, maybe. In practice, it's simply not possible. The conventional wisdom that you need to overwrite multiple times, or with patterns, or with random noise, or anything other than just a single pass of zeros is nothing but a myth.

  22. you mean reading the entrails? by G3ckoG33k · · Score: 3, Funny

    You couldn't possibly seriously mean we should start reading the entrails? That is soo medieval.

  23. Re:How is that different than spinning disks? by BetterSense · · Score: 4, Informative

    It IS pretty much impossible, but that's not going to stop people from perpetuating the wive's tale for decades to come.

    I actually have seen Magnetic Force Microscopy used as a tech demo to image the bits on a floppy disk. I asked the process owner if it could be used to extract data, and he just rolled his eyes. He said that besides the issues with modern hard drives having bits that are orders of magnitude smaller both in size and in magnetization, it's just impractical to extract any data, which should be obvious since it takes like 10 minutes to image a handful of bits. A handful of bits that could mean anything, and be anywhere on the disk platter, and anywhere in the file system, and which could represent erased or scrambled or encypted data anyway. I think the idea that you could go beyond even that and divine what bits were written "UNDER" the current ones is just fantasy. I have heard rumors that NSA has made purchases of a large quantity of scanning probe microscopes for this purpose, but they could have just been buying some for testing...manufacturing volume for scanning probe microscopes is such that an order of a half-dozen of them would be an overwhelmingly large order.

  24. Re:dd by blueg3 · · Score: 2

    No, that's only for attempting to perform a secure erase of a single file. The results for trying to secure-erase single files are so bad (and since there is no ATA command to securely erase only particular blocks on a drive) that it is unsafe to write data to an SSD and then hope to reliably remove that data from the drive without zeroing the entire drive.

    If you'll RTFA carefully, though, you'll note that for all but one drive they tested, zeroing the entire drive was reliable. One drive had about 1% of the original data remaining after 20 passes. One drive was entirely erased in one pass. The other drives were entirely erased within 2 passes.

    So, zeroing an entire SSD works as long as you use more than one pass. Zeroing individual files on an SSD doesn't work.

  25. Re:Pure crap by Rockoon · · Score: 2

    Give her a gift card for a spa or other "nice" thing to do for the day. She will (A) love you for it, (B) never need to know that you had a kiddie porn drive, or (C) that you baked said kiddie porn drive in the oven while downloading midget porn as a replacement.

    --
    "His name was James Damore."
  26. Re:How is that different than spinning disks? by Anonymous Coward · · Score: 2, Informative

    This is a very popular myth, but after hunting for comfirmation a few years ago I came up empty. Even the original author no longer stands behind this assertion. It's widely considered to be debunked: http://www.lawtechguru.com/archives/2009/03/11_multipass_erasure_myth_debunked.html

  27. Amended platter removal terms by lullabud · · Score: 2

    They later amended the platter removal terms with the following text, but still nobody accepted it.

    If the challenger is an established data recovery business located in the United States of America (We would need to see Articles of Incorporation, a current business license and one other form of business identification in order to determine that they are indeed a professional, for-profit, established data recovery business) or a National government law enforcement or intelligence agency (NSA, CIA, FBI), then we will allow these type of organizations to disassemble the drive and to keep the drive for thirty (30) consecutive days.

  28. Re:How is that different than spinning disks? by Firethorn · · Score: 2

    Well, the DoD still seem to prefer more 'aggressive' techniques, and apparently don't agree with NIST on this (I believe this is what you were referencing):

    1. We're paranoid
    2. We still have old discs laying around. 10GB? Hah! I've seen 40 MB units, still operational, within the last year.
    3. We want to be *SURE*, and the human factor is taken into account - we're willing to overkill on modern drives(and modern is relative), in order to make sure the older ones get wiped properly.

    --
    I don't read AC A human right
  29. Re:How is that different than spinning disks? by toddestan · · Score: 2

    As someone else who's played around with magnetic force microscopes, recovering data off of a disk would be extremely time consuming. As the parent mentioned, you're talking several minutes to capture an image that's maybe 100 square micrometers (10x10 um). A floppy disk has several million square micrometers of surface area to image per side - you're literally talking centuries to read a disk this way.

    The other problem is resolution. I haven't seen a microscope yet that can see the bits on a modern hard drive. If you want to see bits, you're generally imaging a floppy disk, or an old MFM/RLL hard drive. Zip disks also work well.

    Of course, it could still be the wrong tool for the job. A $100k magnetic force microscope may take centuries to read a diskette, but a cheap $15 floppy drive can do it in about a minute.