Slashdot Mirror


What's Missing From File / Disk Encryption?

lockDrive asks: "Every month, we read a news about personal information leak. Most of the time, either a laptop or a hard disk that contains sensitive information is stolen from a government or corporate office, and the data are not encrypted. Recently, Department of Veterans Affairs had lost a laptop which contained confidential information for 26.5 million veterans. The data were not encrypted. There are many products that provide a solution to such a problem. Microsoft Encrypting File System (EFS), which comes with Windows 2000 and later, encrypts data in a file system and seems to have a decent key recovery system in Windows 2003 Server CA. Products like SecureDoc and DriveCrypt encrypt an entire disk. I have tried some of them and they are not that difficult to use. What is holding people who handle sensitive information (government, health-care, insurance ...) back from encrypting their data? Are the products still too hard to use? Are they concerned about performance loss? Are they not convinced with the security gain? Are they just not adopting the technology quickly? Is there anything missing in the technology?"

10 of 177 comments (clear)

  1. Time by suso · · Score: 2, Interesting

    Time is what is needed. :-D

  2. That reminds me- by sirket · · Score: 2, Interesting

    I've been looking for an encrypted hard drive controller- something that looks to the OS like a normal disk but every single byte written to the disk is encrypted. The moment the power is pulled the key is lost and needs to re-entered when the system reboots. It would look like a disk error but when the "Non-system or disk error" message comes up you enter the key and the system boots normally.

    I would prefer there not be any chance of the OS leaving around un-encrypted information on the swap partition or hacing a back door or any other stupidity. I've seen encrypted controllers but only with 40 bit keys. I'd love to see something with an AES 256 bit key. If nothing is out there I may just have to put together something using an FPGA.

    -sirket

    1. Re:That reminds me- by sirket · · Score: 2, Interesting

      It is stored in one of the FPGA embedded RAM blocks and is wiped the moment power is lost.

  3. Ignorance by Merlynnus · · Score: 5, Interesting
    Clearly the problem is ignorance. And bad habits. And bad security policies.

    It's not a technological problem -- everyone in Windows & Linux land should be using Truecrypt or something similar and being smart about how they handle data. Rather it's a social problem.

  4. lack of proper policies by artifex2004 · · Score: 3, Interesting
    The biggest flaw in these schemes is always the glaringly obvious: nobody bothered to turn them on.
    Without written security policies, nobody knows what they should/can/must not do, and even if they do, they follow the rules inconsistently.

    Take a look at Cisco's SAFE, for example. It explicitly says

    This document presumes that you already have a security policy in place. Cisco does not recommend deploying security technologies without an associated policy. For further information about security policies and their use, consult the SANS Security Policy Project at:
    http://www.cisco.com/go/safe


    If you don't know what you have, who gets to access it, and when, what good is a bunch of hardware and software? You might as well hand all your workers CDs of your databases and cross your fingers. Which, possibly, actually happens in some of these cases. Sadly, this sort of stuff is Day 1 material for CCNA and MCSE and other certifications these days, so it pretty much looks like whoever is running the show in these places can't follow or doesn't know standard industry practices. That's gross negligence, IMO, and nothing to do with any sort of technical failings.
  5. How about a distro w/ initial install support by Tiamat · · Score: 4, Interesting

    I would love to a see a distro, like ubunto, that would ask me if I wanted to create a small boot parition, and a larger *encrypted* primary parition, which would then install to the encrypted partiton, and finally give me the chance to burn a CD from which to boot (or USB stick if my system supported that, etc.). Then, on boot (either from the HD small boot part, or a read-only CD), I'd enter my password to access the root partition. As it stands, getting this done requires some expertise, too much time for most of us, and lot manipulating of files, partitions, etc.. Make it easy!

  6. Cooperation between Linux and Windows? by TerminaMorte · · Score: 2, Interesting

    I'd just like to be able to store 'personal' or 'private' information on a 1GB encrypted flash drive.

    One of the major reasons that has stopped me from using encryption, however, is the lack of compadibility for diffrent operating systems.

    If I encrypt the drive using AES-256 on linux, I'm unable to read it on Windows. If I encrypt it with one of the Windows tools, I'm unable to read it on linux.

    So I'm stuck between only being able to read my information at home on my linux machine, or only on public/windows computers.

  7. -truecrypt? by acomj · · Score: 2, Interesting

    We had someone at work talk about this...

    http://www.truecrypt.org/

    Its not a HW controler, but a mount the file system encrypted. It seems like a well thought idea anyway. And available for Linux.

    1. Re:-truecrypt? by Merlynnus · · Score: 2, Interesting

      Dude: Coffee. Or something. That much stress isn't good for you. You use Truecrypt on your laptop? OOooooh. I bow down to your obvious omniscience.

      Hardware encryption? Hah! Ask the Xbox devs how well that worked for them. Given access to the hardware, it will be broken. But .... you'll have designed it. Oh, I'm sorry, I'm sure that will solve all the hardware encryption problems.

      But mocking aside, check this out: Can I relocate the Windows temp directory somewhere else? Yes. Can I change the location of the Windows swap file? Yes, but that one is problematic, since booting without access to the swap file is difficult.

      But if you're really that paranoid, here's a solution for you:

      Virtualization

      Run your favourite flavor of Linux and install VMPlayer. Still with me? Now create a large encrypted volume. How about a large hidden encrypted volume. On that encrypted volume, create a large VMDK and a Windows VM. Do all your super-secret stuff in the VM. Which resides entirely and completely on an encrypted volume. Tempfiles, swap files, everything are encrypted. If you're are *really* paranoid you could install Truecrypt on the Windows VM.

      See? If you think it through a little bit, you'll recognize that there *are* technological solutions for all levels of paranoia. But all the technological solutions are moot when the (l)users don't adhere to the security policies. Or when no clear security policies exist.

  8. Plausible Deniability by Niet3sche · · Score: 2, Interesting
    Nonsense. I use Truecrypt, and have encrypted a whole drive. *Nothing* on it is unencrypted. It has no partition table. Any sort of analysis of it would show that it is complete indistinguishible from random noise. Taken out of the workstation that it currently resides in, it would be completely and utterly secure. And, unintelligible. Granted, it's not the boot drive, but so what?

    The really great thing about TrueCrypt, as I see it, is plausible deniability. This means that you can "nest" volumes and only have to account for the outer "envelope" when you are tortured by Homeland Security because you are using cryptography. The short of this: it is impossible to distinguish the "signal" of a nested hidden volume from the "noise" of random bits and such on the device.