<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Trust – Certifications</title>
	<atom:link href="http://www.gfi.com/blog/trust-certifications/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gfi.com/blog/trust-certifications/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=trust-certifications</link>
	<description>Brought to you by GFI Software</description>
	<lastBuildDate>Fri, 09 Aug 2013 12:13:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: jesse Dziedzic</title>
		<link>http://www.gfi.com/blog/trust-certifications/comment-page-1/#comment-29963</link>
		<dc:creator>jesse Dziedzic</dc:creator>
		<pubDate>Thu, 20 Oct 2011 18:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=1820#comment-29963</guid>
		<description><![CDATA[Thankfully some bloggers can still write. My thanks for this piece..]]></description>
		<content:encoded><![CDATA[<p>Thankfully some bloggers can still write. My thanks for this piece..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/trust-certifications/comment-page-1/#comment-2652</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Tue, 02 Feb 2010 11:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=1820#comment-2652</guid>
		<description><![CDATA[Hi John, I think I might not have been very clear in my article. You see, the security issue was with the USB drive itself not with the certification. In that FIPS 140-2 lvl2 certifies drives that use approved encryption and have anti physical tempering measures. In the case illustrated in this article the vendor had an application that authenticated the password using approved encryption algorithms but that&#039;s all the application did, once the password was verified it then used the same key to authenticate with the drive itself. 

I am speculating a little here since obviously I didn&#039;t do the research myself but I suspect the vendor uses the same cryptographic key to decrypt the data within the USB drive and then encrypts that cryptographic key with the password provided by the user. The security flaw in this was the vendor&#039;s implementation, that is they used the same cryptographic key on every drive meaning that all a malicious person would need to do is patch the USB drive application to send the proper key irrespective of the decrypted key. This would make it so that the patched application would decrypt any USB drive of that vendor even when a bad password is entered. Since the drive was still using an approved encryption algorithm it still could be certified as FIPS 140-2 lvl 2. 

In a way it&#039;s like a vendor issues a garage door remote where all remotes send the same encrypted signal. No one can decode the signal itself but they don&#039;t need to as any remote can open any door anyway. Likewise here the vulnerability wasn&#039;t with the encryption but with the implementation of that encryption. Hope I was clear. Let me know if you have any more questions.

Conclusion is if a device is Certified FIPS 140-2 level 2 it doesn&#039;t mean that it&#039;s insecure, it just doesn&#039;t necessarily mean it&#039;s secure. Depends on how good a job the vendor did.]]></description>
		<content:encoded><![CDATA[<p>Hi John, I think I might not have been very clear in my article. You see, the security issue was with the USB drive itself not with the certification. In that FIPS 140-2 lvl2 certifies drives that use approved encryption and have anti physical tempering measures. In the case illustrated in this article the vendor had an application that authenticated the password using approved encryption algorithms but that&#8217;s all the application did, once the password was verified it then used the same key to authenticate with the drive itself. </p>
<p>I am speculating a little here since obviously I didn&#8217;t do the research myself but I suspect the vendor uses the same cryptographic key to decrypt the data within the USB drive and then encrypts that cryptographic key with the password provided by the user. The security flaw in this was the vendor&#8217;s implementation, that is they used the same cryptographic key on every drive meaning that all a malicious person would need to do is patch the USB drive application to send the proper key irrespective of the decrypted key. This would make it so that the patched application would decrypt any USB drive of that vendor even when a bad password is entered. Since the drive was still using an approved encryption algorithm it still could be certified as FIPS 140-2 lvl 2. </p>
<p>In a way it&#8217;s like a vendor issues a garage door remote where all remotes send the same encrypted signal. No one can decode the signal itself but they don&#8217;t need to as any remote can open any door anyway. Likewise here the vulnerability wasn&#8217;t with the encryption but with the implementation of that encryption. Hope I was clear. Let me know if you have any more questions.</p>
<p>Conclusion is if a device is Certified FIPS 140-2 level 2 it doesn&#8217;t mean that it&#8217;s insecure, it just doesn&#8217;t necessarily mean it&#8217;s secure. Depends on how good a job the vendor did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mello</title>
		<link>http://www.gfi.com/blog/trust-certifications/comment-page-1/#comment-2591</link>
		<dc:creator>John Mello</dc:creator>
		<pubDate>Mon, 01 Feb 2010 16:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=1820#comment-2591</guid>
		<description><![CDATA[Emmanuel—do you know if the security problem with FIPS 140-2 Level 2 also apply to FIPS 140-2 Level 3?]]></description>
		<content:encoded><![CDATA[<p>Emmanuel—do you know if the security problem with FIPS 140-2 Level 2 also apply to FIPS 140-2 Level 3?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/trust-certifications/comment-page-1/#comment-2437</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Fri, 29 Jan 2010 10:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=1820#comment-2437</guid>
		<description><![CDATA[Yes well I wasn&#039;t expecting any of them to close down really and neither should they. Hopefully they learned from what happened and introduced better QA to ensure something like that doesn&#039;t happen again. I am sure that once the DataTraveler 5000 hits the market it will be very well tested by the community!

On my side I just hope that my article will help people who read it, avoid the mistake of thinking that FIPS 140-2 Level 2 (or any other certification really) is idential to definitely safe. Always remember, certifications just helps one make a good decision by pointing to the right direction, nothing else.]]></description>
		<content:encoded><![CDATA[<p>Yes well I wasn&#8217;t expecting any of them to close down really and neither should they. Hopefully they learned from what happened and introduced better QA to ensure something like that doesn&#8217;t happen again. I am sure that once the DataTraveler 5000 hits the market it will be very well tested by the community!</p>
<p>On my side I just hope that my article will help people who read it, avoid the mistake of thinking that FIPS 140-2 Level 2 (or any other certification really) is idential to definitely safe. Always remember, certifications just helps one make a good decision by pointing to the right direction, nothing else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mello</title>
		<link>http://www.gfi.com/blog/trust-certifications/comment-page-1/#comment-2419</link>
		<dc:creator>John Mello</dc:creator>
		<pubDate>Thu, 28 Jan 2010 19:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=1820#comment-2419</guid>
		<description><![CDATA[Emmanuel—Despite this flaw, it seems that it&#039;s business as usual for some USB drive makers, as this announcement yesterday by Kingston indicates:

&quot;Flash memory device maker Kingston on Wednesday released its DataTraveler 5000 USB flash drive meant for government and enterprise customers. Secured by SPYRUS technology gives it 256-bit AES hardware-based encryption, FIPS 140-2 Level 2 certification, XTS-AES cipher mode and elliptic curve cryptography (ECC) algorithms to meet the US government&#039;s Suite B standards.

&quot;FIPS 140-2 certification meets federal standards set out by the National Institute of Standards and Technology (NIST). Level 2 means the DataTraveler 5000 has a tamper-evident construction, a power-on self test that verifies encryption is operating as it should every time the drive is plugged into a USB port.&quot;]]></description>
		<content:encoded><![CDATA[<p>Emmanuel—Despite this flaw, it seems that it&#8217;s business as usual for some USB drive makers, as this announcement yesterday by Kingston indicates:</p>
<p>&#8220;Flash memory device maker Kingston on Wednesday released its DataTraveler 5000 USB flash drive meant for government and enterprise customers. Secured by SPYRUS technology gives it 256-bit AES hardware-based encryption, FIPS 140-2 Level 2 certification, XTS-AES cipher mode and elliptic curve cryptography (ECC) algorithms to meet the US government&#8217;s Suite B standards.</p>
<p>&#8220;FIPS 140-2 certification meets federal standards set out by the National Institute of Standards and Technology (NIST). Level 2 means the DataTraveler 5000 has a tamper-evident construction, a power-on self test that verifies encryption is operating as it should every time the drive is plugged into a USB port.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.gfi.com @ 2013-08-12 16:45:46 by W3 Total Cache --