![](http://investorshub.advfn.com/images/default_ih_profile2_4848.jpg?cb=0)
Monday, March 03, 2008 12:20:34 AM
Steven Sprague replies to: [FDE] DRAM attack - not thwarted at all by Seagate's driveCORRECTION the data on the HDD IS Protected!!!
Sunday, March 02, 2008
http://security-basics.blogspot.com/2008/03/re-fde-dram-attack-not-thwarted-at-all_02.html
Garrett,
There is no time like the present to begin to investigate the tools that have been provided to secure the network.
All enterprise authentication should leverage the TPM.
Start Monday.
Take a wireless 802.1x hot spot and use the TPM to hold the client side keys in a security chip and never in RAM.
This is done by asking the original keys to be created in the TPM and MSCAPI pretty much takes care of the rest. When you create a client side certificate click advanced on the CA request and use the CSP (cryptographic Service Provider) for the TPM. If you select that the keys are not migratable, then the secret key will never leave the chip. Once this is done you have authentication keys on the TPM that can be used for many network purposes. This will dramatically reduce the attack vectors on authentication.
P.S. this only works if you turned your TPM on in bios.
Only by machines with Seagate Drives
Read as much as you can on Intel’s VPRO and *T technologies. This is how we will create secure processing in the future.
Security takes hardware- It worked for cellphones, set top boxes, garage doors, ….. No it’s time for you to use it on your PC.
To ultimately thwart DRAM all memory must be encrypted all of the time. This is no different then all network traffic must be encrypted.
Steven Sprague
CEO Wave Systems Corp.
From: fde-bounces@www.xml-dev.com [<a href="mailto:fde-bounces@www.xml-dev.com" target="_blank"mailto:fde-bounces@www.xml-dev.com</a] On Behalf Of Garrett M. Groff
Sent: Saturday, March 01, 2008 12:14 AM
To: fde@www.xml-dev.com
Subject: Re: [FDE] DRAM attack - not thwarted at all by Seagate'sdriveCORRECTION the data on the HDD IS Protected!!!
I concede your points. My frustration is not with Secude's hardware+software solution specifically. In fact, I think hardware-based encryption (like the Momentus drive) is the way to go in the long haul (hardware+software attacks are typically more difficult than software-only attacks). Just a bit frustrated that I can't sleep as easy at night knowing that the "theoretical" RAM analysis technique will (soon?) be used by more than a group of researchers at Princeton, realistically.
- Garrett
----- Original Message -----
From: Larry Massey
To: fde@www.xml-dev.com
Sent: Friday, February 29, 2008 3:30 PM
Subject: Re: [FDE] DRAM attack - not thwarted at all by Seagate's driveCORRECTION the data on the HDD IS Protected!!!
Garrett:
Glad you “conveniently” received that email…J
Yes, you may be a bit too picky.
Our solution is to solve a Data At Rest problem that in pure Software Laptop Encryption products is broken by exposing the encryption key residing in PC DRAM and NOT to solve the problem of securing the contents of DRAM which would a different data exposure problem, of course.
We make no claim to solve the problem of data exposed in DRAM, simply to not put data in DRAM at a point in time that it could be exposed and used to defeat HDD on board encryption technology. You may want to spend some time learning more about the Seagate drive, as it is quite an interesting and secure technology.
If any of you will be attending the Data Protection Summit in LA next month, we will have a presentation on this specific topic (again DAR only), I will also be attending and would love to meet any members of this very enjoyable although overly cloaked group on this blog. Maybe we can even get together for a dinner one evening. I am sure that some of this blogs under cover vendors might even be willing to foot the bill.
Regards,
Larry
___________________________________________________
Larry Massey
President
SECUDE IT Security, LLC
380 Sundown Drive
Dawsonville, GA 30534 USA
Tel : +1 706 216 8609
Fax: +1 706 216 4696
Mobile : +1 706 215 3854
larry.massey@usa.secude.com
www.secude.com
From: fde-bounces@www.xml-dev.com [<a href="mailto:fde-bounces@www.xml-dev.com" target="_blank"mailto:fde-bounces@www.xml-dev.com</a] On Behalf Of Garrett M. Groff
Sent: Friday, February 29, 2008 2:07 PM
To: fde@www.xml-dev.com
Subject: [FDE] DRAM attack - not thwarted at all by Seagate's drive
I conveniently got an email from Secude in my inbox. One of the closing paras had the following:
As you continue your investigation of disk-encryption technologies, I invite you to contact us to learn more about our partnership with Seagate and other hard drive manufacturers and how we eliminate the types of vulnerabilities found in DRAM attacks. By encrypting data at the drive level, we are able to offer you the highest level of protection.
Of course, that's not true at all. The vulnerability of data residing in DRAM still exists. That will be the case until we get "secure RAM," or something along those lines.
However, it is true that the particular attack involving reading the FDE key directly from RAM is defeated since that key is never written to RAM.
Maybe I'm being too picky here, but looking ahead, this technique could be used to read information from any application that happens to be open at the moment using software that looks for juicy keywords (like "confidential" or "password"). Doesn't that seem like the next logical threat once the "low-hanging fruit" (such as it is) of cold-boot key discovery is patched? I mean, how long are we going to have secure disks with wide-open RAM chips?
- Garrett
cooler
Sunday, March 02, 2008
http://security-basics.blogspot.com/2008/03/re-fde-dram-attack-not-thwarted-at-all_02.html
Garrett,
There is no time like the present to begin to investigate the tools that have been provided to secure the network.
All enterprise authentication should leverage the TPM.
Start Monday.
Take a wireless 802.1x hot spot and use the TPM to hold the client side keys in a security chip and never in RAM.
This is done by asking the original keys to be created in the TPM and MSCAPI pretty much takes care of the rest. When you create a client side certificate click advanced on the CA request and use the CSP (cryptographic Service Provider) for the TPM. If you select that the keys are not migratable, then the secret key will never leave the chip. Once this is done you have authentication keys on the TPM that can be used for many network purposes. This will dramatically reduce the attack vectors on authentication.
P.S. this only works if you turned your TPM on in bios.
Only by machines with Seagate Drives
Read as much as you can on Intel’s VPRO and *T technologies. This is how we will create secure processing in the future.
Security takes hardware- It worked for cellphones, set top boxes, garage doors, ….. No it’s time for you to use it on your PC.
To ultimately thwart DRAM all memory must be encrypted all of the time. This is no different then all network traffic must be encrypted.
Steven Sprague
CEO Wave Systems Corp.
From: fde-bounces@www.xml-dev.com [<a href="mailto:fde-bounces@www.xml-dev.com" target="_blank"mailto:fde-bounces@www.xml-dev.com</a] On Behalf Of Garrett M. Groff
Sent: Saturday, March 01, 2008 12:14 AM
To: fde@www.xml-dev.com
Subject: Re: [FDE] DRAM attack - not thwarted at all by Seagate'sdriveCORRECTION the data on the HDD IS Protected!!!
I concede your points. My frustration is not with Secude's hardware+software solution specifically. In fact, I think hardware-based encryption (like the Momentus drive) is the way to go in the long haul (hardware+software attacks are typically more difficult than software-only attacks). Just a bit frustrated that I can't sleep as easy at night knowing that the "theoretical" RAM analysis technique will (soon?) be used by more than a group of researchers at Princeton, realistically.
- Garrett
----- Original Message -----
From: Larry Massey
To: fde@www.xml-dev.com
Sent: Friday, February 29, 2008 3:30 PM
Subject: Re: [FDE] DRAM attack - not thwarted at all by Seagate's driveCORRECTION the data on the HDD IS Protected!!!
Garrett:
Glad you “conveniently” received that email…J
Yes, you may be a bit too picky.
Our solution is to solve a Data At Rest problem that in pure Software Laptop Encryption products is broken by exposing the encryption key residing in PC DRAM and NOT to solve the problem of securing the contents of DRAM which would a different data exposure problem, of course.
We make no claim to solve the problem of data exposed in DRAM, simply to not put data in DRAM at a point in time that it could be exposed and used to defeat HDD on board encryption technology. You may want to spend some time learning more about the Seagate drive, as it is quite an interesting and secure technology.
If any of you will be attending the Data Protection Summit in LA next month, we will have a presentation on this specific topic (again DAR only), I will also be attending and would love to meet any members of this very enjoyable although overly cloaked group on this blog. Maybe we can even get together for a dinner one evening. I am sure that some of this blogs under cover vendors might even be willing to foot the bill.
Regards,
Larry
___________________________________________________
Larry Massey
President
SECUDE IT Security, LLC
380 Sundown Drive
Dawsonville, GA 30534 USA
Tel : +1 706 216 8609
Fax: +1 706 216 4696
Mobile : +1 706 215 3854
larry.massey@usa.secude.com
www.secude.com
From: fde-bounces@www.xml-dev.com [<a href="mailto:fde-bounces@www.xml-dev.com" target="_blank"mailto:fde-bounces@www.xml-dev.com</a] On Behalf Of Garrett M. Groff
Sent: Friday, February 29, 2008 2:07 PM
To: fde@www.xml-dev.com
Subject: [FDE] DRAM attack - not thwarted at all by Seagate's drive
I conveniently got an email from Secude in my inbox. One of the closing paras had the following:
As you continue your investigation of disk-encryption technologies, I invite you to contact us to learn more about our partnership with Seagate and other hard drive manufacturers and how we eliminate the types of vulnerabilities found in DRAM attacks. By encrypting data at the drive level, we are able to offer you the highest level of protection.
Of course, that's not true at all. The vulnerability of data residing in DRAM still exists. That will be the case until we get "secure RAM," or something along those lines.
However, it is true that the particular attack involving reading the FDE key directly from RAM is defeated since that key is never written to RAM.
Maybe I'm being too picky here, but looking ahead, this technique could be used to read information from any application that happens to be open at the moment using software that looks for juicy keywords (like "confidential" or "password"). Doesn't that seem like the next logical threat once the "low-hanging fruit" (such as it is) of cold-boot key discovery is patched? I mean, how long are we going to have secure disks with wide-open RAM chips?
- Garrett
cooler
Join the InvestorsHub Community
Register for free to join our community of investors and share your ideas. You will also get access to streaming quotes, interactive charts, trades, portfolio, live options flow and more tools.