Rocstor's Ultra Secure SmartCard-Based Portable Hard Drive
At CES 2012, Rocstor displayed a prototype of its Amphibious -- a highly secure portable hard drive that connects via Firewire 800 or USB and that can't be mounted without first using a smartcard and a pin code.
In situations that demand portable hard drives, but that are highly sensitive to the chance of drive misplacement or loss, Rocstor's Amphibious is a solution that might mitigate the risk.
Rocstor is at CES 2012 showing a prototype of the Amphibious. The drive's security features are its most important differentiators. Though a sledge hammer might crack it open (we didn't try), there are no visible screws or entry points for gaining easy access to the actual disk drive. But the Rocsafe's most notable features are the numeric keypad on its glassy surface and a smartcard slot. Without an authorized smartcard and self-selected PIN code, the drive cannot be mounted by a PC or Mac.
According to Rocstor director of sales Anthony Rink, the Amphibious is compliant with the AES 256 CBC specification and is FIPS 140-2 Level 2 certified. The drive is manufactured in Los Angeles so that it satisfies the Trade Agreement Act provisos that make it possible to sell the drive to the US Government. Rink claims the drive is also HIPAA compliant as well. The drive can also be configured as a boot drive for either Mac OS X or Windows.
In the embedded video below, Rink discusses how the Amphibious is manufacturer independent. In other words, other smart cards like a smart government issued ID (for example, one that opens doors in government installations for example). It's available in a variety of capacities ranging from 320 G-bytes to 1 terabyte.
Rocstor's expecatations are that the drive is going to be available by the end of Q1 2012. More information is available from Rocstor.com.
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.
As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Published: 2014-10-25 The Payment for Webform module 7.x-1.x before 7.x-1.5 for Drupal does not restrict access by anonymous users, which allows remote anonymous users to use the payment of other anonymous users when submitting a form that requires payment.
Published: 2014-10-25 The slapper function in chkrootkit before 0.50 does not properly quote file paths, which allows local users to execute arbitrary code via a Trojan horse executable. NOTE: this is only a vulnerability when /tmp is not mounted with the noexec option.
Published: 2014-10-25 The shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "$(" command-substitution sequences, a different vulnerability than CVE-2014-1928....
Published: 2014-10-25 The shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "\" (backslash) characters to form multi-command sequences, a different vulner...
Published: 2014-10-25 python-gnupg 0.3.5 and 0.3.6 allows context-dependent attackers to have an unspecified impact via vectors related to "option injection through positional arguments." NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.