Secure IronKey Flash Drive Will Self-Destruct in 3...2...1...

Illustration for article titled Secure IronKey Flash Drive Will Self-Destruct in 3...2...1...

Designed to be the world's most secure flash drive, the IronKey employs military-grade AES hardware-based encryption using its IronKey Cryptochip. The encryption keys are stored on the drive itself and your password is required in conjunction with the keys to access and decrypt files. If you forget your password, you may be in trouble; after ten consecutive failed password attempts, the IronKey self-destructs (internally) and erases everything on the drive using "flash-trash" technology that physically overwrites every byte, making the data completely unrecoverable.

Illustration for article titled Secure IronKey Flash Drive Will Self-Destruct in 3...2...1...

The hardware encryption is one aspect of the IronKey, but the online component is another. When you log in to the IronKey website (which again requires both your password and your IronKey to be physically plugged in to your machine), you can activate their secure web-browsing service which turns FireFox into a malware-protected, "stealth surfing" application. Other security-nut features include a "potting" technique that fills the innards of the key with black goo, waterproofing it past military standards and preventing hardware crypto-analysis. $79 will get you 1GB of peace of mind, but the biggest option is the 4GB drive for $149. [IronKey via EverythingUSB]

Share This Story

Get our `newsletter`

DISCUSSION

brian-stinar-old
brian.stinar

OK, so what happens if I do the following?

1.) Mount the drive and perform a dd to get all the encrypted data

2.) Save the raw results of the dd to a file someplace.

3.) for (i = 0, i < 9, i++){

attempt password crack

} // end for

copy image back;

end;

So, 9 crack attempts and a 1 gig copy. Throw in a bunch of similar drives that will accept the image created in 1 & 2 and run the above in parallel.

Or, even better, do an analysis on the image between crack attempts and figure out what changed. Then, just copy the changed segment(s) back. Unless they distribute this counter across the whole drive somehow, I bet this would work.

Anyone want to send me a couple of these for free to try my ideas out? I'll (attempt to) publish something in an open journal if I find anything cool. I think the 4 gig drives would be MUCH better for testing...