Slashdot Mirror


Self-Encrypting Hard Drives and the New Security

In a recent blog post, CNet's Jon Oitsik has called for a policy shift with respect to data encryption. A new standard by the Trusted Computing Group promises the availability of self-encrypting hard drives soon, leading some to call for immediate adoption. Will this create even more security problems due to lazy custodians, or should someone responsible for keeping your information safe be required to move to the new hardware? Hopefully the new hardware comes with a warning to continue to use other data protection measures as well.

20 of 205 comments (clear)

  1. self encrypting, probably self-defeating too by petes_PoV · · Score: 4, Insightful
    And the very first thing the users will do is write down the encryption key, so they don't forget it.

    After all, what's the point of having all your data on a disk that you can't access? It's far more likely that the user(s) will forget the key, than for the drive to fail. However, the result will be the same in both cases: inaccessible data and if past experience is anything to go by, no backups (which would also have to be encrypted, again with the isssue over keys).

    Until the average PC user radically rethinks their attitude towards their computers - whether at work or play, this seems just one step too far.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  2. Re:hmm by Shakrai · · Score: 2, Insightful

    My first thought was that the encrypted hard drives will probably have a back door built into them to keep us safe from all those kiddie pornographers..... Think of the children!

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.
  3. Re:Propriety Encryption by Shakrai · · Score: 4, Insightful

    You got a funny mod but it should be insightful. That was my first thought......

    Don't worry though, it's for your protection. Think of the children/terrorists!

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.
  4. I want one with a removable key by davidwr · · Score: 5, Insightful

    It's hard to do with fixed drives, but I want USB drives and memory sticks that come with their own dongle-key that plugs into the storage device, so they key can be separated from the drive. Even better if it has its own keypad or fingerprint reader for authentication. "Something you have, plus something you know."

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  5. Re:Propriety Encryption by dgatwood · · Score: 4, Insightful

    I wouldn't worry about back doors. Given the history of "secure" hardware devices, I'd be more worried about them turning the password trivially into a 64-bit key, using XOR with the key, and storing the key in unencrypted flash for verification....

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  6. Encryption != Security by elrous0 · · Score: 4, Insightful

    If it's a proprietary system where some insecure company or insecure government agency has the keys, why even bother? If anything, it's only providing you with a dangerously false sense of "security."

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
  7. Really? by fuzzyfuzzyfungus · · Score: 4, Insightful

    I want some of what this guy is smoking. He seems to be under the impression that, because the encryption is handled in hardware, there will be no software to deal with. And what, pray tell, will configure the hardware, and set crypto keys, and hold them in escrow in case of the inevitable forgetting, and change them if needed, and so on and so forth?

    Hardware encryption certainly has its advantages; but if you can't handle deploying software encryption now, I'm deeply skeptical of your ability to handle deploying hardware encryption.

  8. How can you trust it to not have a back door? by Eric+Smith · · Score: 2, Insightful
    The big risk with FDE is that the drive may, unbeknownst to the owner, cache and store the encryption keys somewhere inside the drive, either on the media or in nonvolatile memory, making it available to those that know where to find it.

    Even if the standard drive firmware doesn't do that, how would you know that the firmware of the drive wasn't modified sometime after manufacture and before purchase to install such a back door?

    If you were an agent of some government that wanted to be able to access data on disk drives whose owners believe them to be encrypted, what better way to do that than to either convince the drive vendors to install a back door for you, or to let you tamper with the drives at some point in the process? That would eliminate a whole lot of hassle for you, and there are only a few drive vendors you'd have to subvert.

    I think I'll stick to LUKS and dm-crypt. It's not a perfect solution, and it's still possible that someone could subvert my encryption, but doing it in the software I have some measure of control over clearly makes it harder for them than doing it in hardware that I have no choice but to trust blindly.

    Am I paranoid? Sure. Probably no one is trying to steal my keys or my data. But the likelyhood of the existence of a back door has NOTHING to do with whether the bad guys (or maybe the good guys?) are interested in my data. Even if no one intends to steal my data today, once a back door exists it can be used against me in the future.

  9. Re:Multiple security layers by GMFTatsujin · · Score: 5, Insightful

    Unless it does something unexpected, such as, say, making it a nightmare to recover files off the drive for legitimate reasons.

    I foresee a lot of IT departments pulling their collective hair out on this one: some Executive Director with a penchant for buying the Shiny New Thing stores mission critical data on a self-encrypting drive, some motherboard component on the computer blows up, and now the hard drive -- while fine -- is inaccessible.

    Yay.

  10. Three problems by Todd+Knarr · · Score: 4, Insightful

    Three problems with the idea:

    1. Transferring media to new systems. I've already seen a case at work where an encrypted laptop drive was fully intact and working, but the laptop it was in was dead and had to be replaced. The drive was a complete loss, because it couldn't be used as the boot drive in the new laptop (different manufacturer) and there wasn't any software that could be used to supply the boot password to the drive when connected by any other method.
    2. Suspend/hibernate. We've found that a lot of the laptop models where I work don't correctly handle returning from a suspend and/or hibernate state. The most common case is that the laptop simply returns to normal operation from the suspend state without requiring re-entry of passwords. Most users simply put their laptop into suspend state rather than powering it down, which means anyone stealing the laptop can completely ignore the drive encryption. Standard Windows screen locking doesn't help much, once the laptop's unsuspended it's network interface is active and it can be remotely compromised and the screen lock disabled.
    3. Law enforcement. If the drive encryption is truely secure, LEOs will insist on having a back-door to let them decrypt a suspect's drive to search for evidence even if the suspect won't give them the passwords. If such a back-door exists, it'll quickly be broken and software produced to gain access to an encrypted drive through that channel rendering the encryption useless.

    #2 can be dealt with going forward in the hardware and OS. #1 can be dealt with going forward with standardized encryption and hardware protocols. #3... is intractable.

    1. Re:Three problems by Creepy+Crawler · · Score: 3, Insightful

      Then DM_CRYPT solves all three.

      1. There's a /boot partition which provides basic bootup services, like entering pass phrases. Any machine that can read standard HD's can read the dm_crypt system.

      2. Hibernate is inherently unsafe, unless the hibernation itself is encrypted. And once there, why not just fresh-boot? And about standby, require as a system policy to log out before standby. Then they must hack the standard system to get even a user account. Also, you did not specify memory holes like firewire. They're equally dangerous, if not moreso.

      3. Linux is open source, so we would see any attempted exploits in dm_crypt. There might be, but we'll find it eventually.

      --
  11. Re:Multiple security layers by Todd+Knarr · · Score: 3, Insightful

    Or worse, said Executive Director stores information on that drive that's relevant to a lawsuit. And when you have to tell the court that you've lost evidence because of this, you end up facing the possibility of losing some points in the case (or even the entire case) as sanction for spoliation of evidence. Even if the evidence would have exonerated your company. We won't even discuss the fun if it's tax- or SEC-related.

  12. Re:Lock out vs lose data by TubeSteak · · Score: 3, Insightful

    While the focus will be on preventing data from being accessed when the PC is stolen, this will come with the rather severe side effect that a significant number of users will irreversibly lock themselves out of all their data by losing/forgetting their pass phrase. Too bad you can't reduce the first problem without increasing the second.

    Are the contents of your wallet at least as valuable, to you, as the content of that encrypted hard drive?
    Good, then write down the passphrase and put it in your wallet.

    I bet most people take a lot more care with their wallet than they do with their work passwords.

    --
    [Fuck Beta]
    o0t!
  13. Re:Multiple security layers by Lord+Ender · · Score: 5, Insightful

    No. Worthless security measures are bad for security because they provide a false sense of security. This influences behavior. So bad "encryption" really can be worse than plain text.

    --
    A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
  14. Re:Looks like DRM/proprietary lock-in (itsatrap) by mrsteveman1 · · Score: 3, Insightful

    Self encrypting would be in the drive no?

    So to an operating system, once the drive has been unlocked by a firmware command it should appear as a cleartext ATA device.

  15. Re:Multiple security layers by mrsteveman1 · · Score: 2, Insightful

    That's why you do separate encrypted offsite backups. Encrypted transport over some cable or network to another encrypted container like a LUKS volume or something.

    You should never rely entirely on one copy of data anyway, this seems to be just a way to protect drive data from theft.

  16. Re:Trusted Computing Group reputation? by afidel · · Score: 3, Insightful

    No, the trusted computer group grew out of an effort at Microsoft to allow secure network booting of clients. Without hardware encryption and bidirectional authentication it was a feature that customers asked for but which they would never have been able to accomplish. There has been talk of using such technology to implement better DRM, but so far it has come to naught even with Vista/Win7. In fact the TPM keystore is available for anyone to use via a fully documented interface and I believe there is a Linux module that allows you to use it. The biggest problem I have is that many TPM 1.2 implementations allow the key out of the keystore along an unencrypted bus which means there is a non-trivial but attainable attack vector against them. Personally I wish Dell wasn't the only vendor supporting TPM in server class systems because I would love to use bitlocker for remote office servers but I can't stand Dell's equipment or support.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  17. Re:64-bit key? by sheddd · · Score: 2, Insightful

    And you get modded informative. Nice!

  18. Re:Propriety Encryption by Anonymous Coward · · Score: 1, Insightful

    That is not user failure, it is a design failure.

    What do you expect when you give a user a portable, a smart card and a pin code while telling them "you need the card and the code to access the computer" ?

    The typical user / office drone will be much more concerned about not being able to use the portable when he accidentally leaves the card at home, or forgets the code, than he is about the possibility of data theft.

    He perceives the chance of this happening to be much higher than the chance of the portable being stolen.

    Combine that with the fact that he will be lambasted by his boss if he forgets the card, and can not work because of it, and it is easy to see why the user sees data theft as the lesser problem of the 2.
    (Especially because typically he is not blamed for the portable being stolen, those things "just happen".)

    The only thing to make ANY security system with "users" secure, is to make sure that the users have an incentive to keep it secure by following the proper procedures.
    That means rewarding compliance and/or heavy sanctions for non-compliance and an audit procedure for the lot. (for example, in your case you could randomly check peoples bags when they go home and take disciplinary actions when they are non-compliant)

  19. I won't touch it until the firmware is open. by Ungrounded+Lightning · · Score: 2, Insightful

    Having the disk drive processor or special-purpose logic on the drive do the encryption/decryption is a fine division of effort.

    But until the firmware is open (and there's a way to check that it's what's really running) I won't use such a thing. (Except maybe in transparent mode with the REAL crypto being in software on the machine.)

    There are too many opportunities for data compromise with built-in, proprietary and closed, firmware encryption: Faulty design, government back doors, and bad-guy back doors to name just three.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way