 




<?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: Encryption by Law? If so, what strength or type?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 11:56:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: sarahcortes</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/#comment-64602</link>
		<dc:creator>sarahcortes</dc:creator>
		<pubDate>Sat, 20 Jun 2009 12:21:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-64602</guid>
		<description><![CDATA[Troy Tate, thanks, are you recommending the law should explicitly require 1024-bit minimum key length? I&#039;m interested in what we feel the law should specify rather than how anyone recommends interpreting the law. Right now the law is totally vague. 

JoeMellott seems to be saying the law should not attempt to require encryption because it is not feasible to come up with a reasonable standard. 

Rklanke seems to agree that specifying encryption in the law is futile since its implementation has so many dependencies and these would also have to beexplicitly specified. 

SbElectric seems to be unclear but suggesting using a NIST standard. An interesting idea, so I asked, which one? there seem to be hundreds and &quot;encryption&quot; is not a NIST cluster topic. 

WIll be waiting to hear responses.]]></description>
		<content:encoded><![CDATA[<p>Troy Tate, thanks, are you recommending the law should explicitly require 1024-bit minimum key length? I&#8217;m interested in what we feel the law should specify rather than how anyone recommends interpreting the law. Right now the law is totally vague. </p>
<p>JoeMellott seems to be saying the law should not attempt to require encryption because it is not feasible to come up with a reasonable standard. </p>
<p>Rklanke seems to agree that specifying encryption in the law is futile since its implementation has so many dependencies and these would also have to beexplicitly specified. </p>
<p>SbElectric seems to be unclear but suggesting using a NIST standard. An interesting idea, so I asked, which one? there seem to be hundreds and &#8220;encryption&#8221; is not a NIST cluster topic. </p>
<p>WIll be waiting to hear responses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sarahcortes</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/#comment-64601</link>
		<dc:creator>sarahcortes</dc:creator>
		<pubDate>Sat, 20 Jun 2009 12:13:58 +0000</pubDate>
		<guid isPermaLink="false">#comment-64601</guid>
		<description><![CDATA[Thx, SbElectric, for your reply. My question regards your opinion of &lt;i&gt;whether and how &lt;/i&gt;encryption should be included in legislaiton like the ones I noted in my question. Not exactly asking &lt;i&gt;what &lt;/i&gt;the standards are. I can see what the laws say, they are totally vague. I am soliciting input from a broad range of people as to their opinions on this topic.

NIST giudelines are great, by the way, which one or ones in particular would you highlight as &quot;encryption&quot; standards? Since tere are hundreds of standards on thet site and they don&#039;t have an &quot;encryption&quot; cluster. 

I&#039;ll be interested to know your answer, thx]]></description>
		<content:encoded><![CDATA[<p>Thx, SbElectric, for your reply. My question regards your opinion of <i>whether and how </i>encryption should be included in legislaiton like the ones I noted in my question. Not exactly asking <i>what </i>the standards are. I can see what the laws say, they are totally vague. I am soliciting input from a broad range of people as to their opinions on this topic.</p>
<p>NIST giudelines are great, by the way, which one or ones in particular would you highlight as &#8220;encryption&#8221; standards? Since tere are hundreds of standards on thet site and they don&#8217;t have an &#8220;encryption&#8221; cluster. </p>
<p>I&#8217;ll be interested to know your answer, thx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rklanke</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/#comment-64502</link>
		<dc:creator>rklanke</dc:creator>
		<pubDate>Wed, 17 Jun 2009 04:10:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-64502</guid>
		<description><![CDATA[Every encryption scheme, regardless of key length, assumes strong passwords. If users set the passwords, expect weak (easily remembered, easily entered, and easily guessed) passwords. Dictating encryption strength or mechanism without dictating password strength leads to false confidence.]]></description>
		<content:encoded><![CDATA[<p>Every encryption scheme, regardless of key length, assumes strong passwords. If users set the passwords, expect weak (easily remembered, easily entered, and easily guessed) passwords. Dictating encryption strength or mechanism without dictating password strength leads to false confidence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joemellott</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/#comment-64494</link>
		<dc:creator>joemellott</dc:creator>
		<pubDate>Tue, 16 Jun 2009 18:32:48 +0000</pubDate>
		<guid isPermaLink="false">#comment-64494</guid>
		<description><![CDATA[I have been looking into the impacts of the MA law, and they specify encryption that uses &quot;... an algorithmic process, or alternative method at least as secure, into a form in which meaning cannot be assigned without the use of a confidential process or key...&quot;, which is pretty wide open as far as actual strengths and methods to meet compliance.  

Further, only data that is transmitted across public networks, wirelessly or stored on laptops needs to be encrypted, so depending on how your organization works this could be a huge deal or trivial.

Having the government specify mimimum encryption strengths seems dangerous to me, as they will probably either be unreasonably hard on the little guy or hopelessly behind the times.]]></description>
		<content:encoded><![CDATA[<p>I have been looking into the impacts of the MA law, and they specify encryption that uses &#8220;&#8230; an algorithmic process, or alternative method at least as secure, into a form in which meaning cannot be assigned without the use of a confidential process or key&#8230;&#8221;, which is pretty wide open as far as actual strengths and methods to meet compliance.  </p>
<p>Further, only data that is transmitted across public networks, wirelessly or stored on laptops needs to be encrypted, so depending on how your organization works this could be a huge deal or trivial.</p>
<p>Having the government specify mimimum encryption strengths seems dangerous to me, as they will probably either be unreasonably hard on the little guy or hopelessly behind the times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy Tate</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/encryption-by-law-if-so-what-strength-or-type/#comment-64469</link>
		<dc:creator>Troy Tate</dc:creator>
		<pubDate>Mon, 15 Jun 2009 20:18:55 +0000</pubDate>
		<guid isPermaLink="false">#comment-64469</guid>
		<description><![CDATA[Implement encryption that people will use and that does not require a significant amount of management overhead (key management - creation, recovery, lifecycle). It should be cost effective for the population size and user education. Any modern system with a key length of 1024bits or better should be adequate.]]></description>
		<content:encoded><![CDATA[<p>Implement encryption that people will use and that does not require a significant amount of management overhead (key management &#8211; creation, recovery, lifecycle). It should be cost effective for the population size and user education. Any modern system with a key length of 1024bits or better should be adequate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 324/327 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 12:00:23 -->