Intel Launches Self-Encrypting SSD
MojoKid writes: Intel just launched their new SSD 2500 Pro series solid state drive, the follow-up to last year's SSD 1500 Pro series, which targets corporate and small-business clients. The drive shares much of its DNA with some of Intel's consumer-class drives, but the Pro series cranks things up a few notches with support for advanced security and management features, low power states, and an extended management toolset. In terms of performance, the Intel SSD 2500 Pro isn't class-leading in light of many enthusiast-class drives but it's no slouch either. Intel differentiates the 2500 Pro series by adding support for vPro remote-management and hardware-based self-encryption. The 2500 Pro series supports TCG (Trusted Computing Group) Opal 2.0 features and is Microsoft eDrive capable as well. Intel also offers an administration tool for easy management of the drive. With the Intel administration tool, users can reset the PSID (physical presence security ID), though the contents of the drive will be wiped. Sequential reads are rated at up to 540MB/s, sequential writes at up to 480MB/s, with 45K – 80K random read / write IOps.
I don't trust vPro.
Got some benchmarks to quote to back that up? AES in hardware is very fast.
Uh, you aren't really comparing equal things. Your post is incredibly stupid.
Self-encryption? So it encrypts itself? Wow. On my laptop I have to encrypt my drive myself. Takes ages to work out all the ciphers
My new device is designed to accept any amount of data and any rate imaginable. Once stored, the data can *never* be retrieved, no matter what is tried. And this new technology is surprising affordable. Call now for your new StorageBrick 3K!
The usual comment, if you care about your drive being able to be unencrypted when the right govt authorities decide to go snooping, it'd be best not to trust this...
Great point of reference:
https://plus.google.com/+Theod...
What is so spacial about this drive's encryption?
We all know, at this point, that these tech hardware companies are total butt-fuck buddies with clandestine government organizations.
We all know, at this point, that as a result of the aforementioned butt-fuck buddies relationship, all hardware can be considered compromised before you even open the damn box.
I don't know about you all, but I'm far more concerned that an organization with the power to take away my life and/or freedom can access my data without my permission or knowledge than infamous Russian credit card scammer "Peggy."
That be my 2 pennies.
An enigma, wrapped in a riddle, shrouded in bacon and cheese
Some of the Samsung SSD drives have encryption since 2009. I don't use it because one has to setup the ATA password to enable it, and does not feel as secure. http://www.samsung.com/global/...
I'm amazed at how willy nilly people are about accepting encryption they can't see. I've seen so many fraudulent or completely broken products. They use weak encryption (like XOR) to non-existent encryption (password 'protect'). Sometimes what could be a safer design (like hardware keypads on hard drives that prevents passwords from being sniffed) isn't simply because companies have limited the password length (six characters digits only for example). Major vendors are no better either. They're not releasing the code and it's been shown that they've even done things like cripple (Intel) security features (hardware based random data) such that any encryption thats utilized it will be severely weakened or broken.
Even software based encryption isn't bad. Out of habit, I encrypt all drives in use (be it LUKS, BitLocker, or Apple's Disk Image.)
I'm guessing the drive will appear to Windows the same way a drive does after running "manage-bde -on X:" where X: is the disk. The drive is -encrypted-, but not -locked-, where the master encryption key is stored as plaintest. Future adding of key protectors remedies this, and using the Windows format command zeroes all regions where the master key is located, making recovery of data extremely difficult.
All and all, I'd buy this. For workstations/desktops in a company or organization, with self-encrypting SSDs, I can repurpose them with a simple secure erase or a secure TRIM command (blkdiscard -s /dev/sdx.) I can donate a computer with one of these drives, and know quite well any data that was formerly on the drives is gone, and won't haunt me later on [2].
As said previously, I have a list of things I protect my data from, and first on my list is Joe Meth-Mouth who grabs a laptop, hands over to Jack Fence. With good SSD encryption [1], Jack Fence will get the drive, but not the data... and I can always buy a new drive and restore my data from other sources.
The vPro stuff can't hurt. IMHO, Intel is the best out there when it comes to SSD (especially in torture test reviews with sudden depowerings of drives in mid-write cycle.)
TL;DR... I'd buy this drive in a heartbeat.
[1]: I use BitLocker with TPM + PIN + USB. This way, if I have my USB flash drive with me, I know the machine isn't going to be unlocked by a bad guy. This isn't a coercion/duress scenario (covered by the usual XKCD link), but a scenario of a theft. This reduces a theft to "just" hardware, rather than hardware + data.
[2]: I'd run a DBAN on the drive for good measure, zeroing it, then run another TRIM.
... treat it as a regular unencrypted drive and apply proper encryption on top. Next.
Hardware doesn't have DNA, does this come straight from a marketing blurb?
Did Intel just discover they can advertise the fact that SandForce controllers have been doing this already for quite a long time. In my experience most SSD's are already encrypted if you want it or not for the added bonus of hiding their wear leveling and bad block information. This has had the side effect that if your controller dies, you're fucked for data recovery off the bare NAND chips.
Because you said so...? People have been using full disk encryption on normal drives for a very long time now without too much complains for most workloads. Something designed specifically for full disk encryption should have less of an impact.
The self encryption is nothing but a marketing trick. Who among us can believe that a company like Intel hasn't built in back doors to access the data fully unencrypted? Let's not fool ourselves.
This idea is amazing.
Instead of having:
- full control over the encryption software
- full control over the encryption key
- data that goes in clear in the ram, then is never seen in clear by the hard-drive
- performance nearly identical through either hardware-enabled encryption (AES...), or even software based implementations (even a smartphone can do it transparently)
We're trading all this for:
- who knows what really happen down there
- hey, is your secure key even used for anything more than ciphering a header?
- data goes in clear in the ram, then in clear to the drive, that do whatever with it. It's so easy to make sure an SSD doesn't make invisible copy too.
- performance nearly identical through (supposedly) hardware encryption.
Yeah, no, please stop fixing problem that doesn't exist.
I suggest encrypting everything multiple times with a more simple encryption algorithm. I find it gives me twice the security at virtually no performance loss whatsoever. Myself, I use ROT13 twice.
If we colonize Mars, it won't be the World Wide Web anymore. UWW?
Probably forced Mcafee scans.
There are two types of people in the world: Those who crave closure
Now it's self-encryption. Caveat Emptor, of this self-deceit!
At my work getting a McAfee message after every extreme slowdown would seem to support your hypothesis.
You probably have a bad flux capacitor.
Self-decryption available for several instances of the U.S gov.
And as a bonus, you get back-doors. This is a completely useless product.
this "new" technology was announced in BYTE mag, some 30+ years ago... then billed as WOM (write-only memory)...
My kingdom for another mod point. We kept a copy of that article on the wall at a previous employer, and we threatened the software group with it every week or so. Marketing thought it was real and wanted to corner the market on this "write only memory" fad. Thank you for the memories.
First of all this article is nothing more than a giant slashvertisement.
Second of all, essentially every SSD on the market self-encrypts, because it is how the secure wipe feature of SSDs functions. Any SSD that is locked with a password is encrypted and unreadable. This is not a new or novel feature at all, and whoever decided this was newsworthy should not be posting articles to slashdot.
Can I set my own key? Set and maintain my own hash? No?
Not interested.
We want true, user-controlled security, not vendor provided.
We've learned our lessons already. The trust is gone.
If the drive's software were flashable (the device could be updated with different software) and the software were Free Software, there would be no reason to fear Intel's connection to the NSA. Users would have the freedoms they need to make sure the software does what they want it to do. Proprietary encryption, no matter who writes it or distributes it, is always untrustworthy for the same reason proprietary software is untrustworthy—you don't really know what it's doing and neither does anyone you can trust to help you understand what it's doing. Furthermore you can't make it do what you want and you can't help others by distributing improved versions that respect other user's freedoms.
Digital Citizen
Ok that's all I had to say, glad to see it's happening now.
On a clear disk you can seek forever ...
Sequential reads are rated at up to 540MB/s, sequential writes at up to 480MB/s, with 45K – 80K random read / write IOps. I used , very fast. http://saigonlinhchi.com/
At the bottom of the revealed Pandora's Box of NSA horrors is this: now, even a jury of Red-State yokels have pause for belief when the defense can say to them: planting such evidence is childs' play for the organs of state security - step out of line and you may be next.
I have a self encrypting hard drive already.
IBM Deskstar from last decade.
Unfortunately no one has the key....
This is one of the many reasons I am glad I can almost always use Linux at work.