<?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: Does Governor Sanford Have an Email Security Problem?</title>
	<atom:link href="http://www.mailprotector.com/blog/2009/06/announcements/does-governor-sanford-have-an-email-security-problem/260/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mailprotector.com/blog/2009/06/announcements/does-governor-sanford-have-an-email-security-problem/260</link>
	<description>Simply Secure</description>
	<lastBuildDate>Tue, 01 Sep 2009 14:50:22 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Setzer</title>
		<link>http://www.mailprotector.com/blog/2009/06/announcements/does-governor-sanford-have-an-email-security-problem/260/comment-page-1#comment-27</link>
		<dc:creator>David Setzer</dc:creator>
		<pubDate>Fri, 26 Jun 2009 22:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailprotector.net/blog/?p=260#comment-27</guid>
		<description>Bryan, you&#039;re right about TLS and SSL only encrypting the transmission, however this is a huge step in the right direction. Right now the vast majority of email is flying around the Internet, Cell, Data and Wireless networks (including hotels, airports and other public places) totally in the clear. By encrypting the transmission you eliminate a large population of sniffers either wired or wireless and reduce the potential culprits to a very small identifiable minority. It&#039;s also a very easy step that users can take which doesn&#039;t require any additional technological skill set on their part.

The voracity of internal security among email hosting organizations differs, I&#039;m sure, by organization but at least in our case, we know that it would be easier for someone to break into a user&#039;s home and crack their laptop than a rouge employee to open a customer&#039;s email. While we still don&#039;t know how The State obtained these messages, we can be fairly assured that were they obtained illegally by an ISP employee this person will be looking at criminal charges just as the college student that hacked Sarah Palin&#039;s email account a few months back.

Don&#039;t get me wrong, desktop-to-desktop encryption with a solution like PGP is good. But it takes a level of user sophistication and coordination generally not found in the populace. And, in the end, if the leak comes from someone with personal access to the local system it doesn&#039;t matter how the messages are encrypted, they&#039;ll be read.</description>
		<content:encoded><![CDATA[<p>Bryan, you&#8217;re right about TLS and SSL only encrypting the transmission, however this is a huge step in the right direction. Right now the vast majority of email is flying around the Internet, Cell, Data and Wireless networks (including hotels, airports and other public places) totally in the clear. By encrypting the transmission you eliminate a large population of sniffers either wired or wireless and reduce the potential culprits to a very small identifiable minority. It&#8217;s also a very easy step that users can take which doesn&#8217;t require any additional technological skill set on their part.</p>
<p>The voracity of internal security among email hosting organizations differs, I&#8217;m sure, by organization but at least in our case, we know that it would be easier for someone to break into a user&#8217;s home and crack their laptop than a rouge employee to open a customer&#8217;s email. While we still don&#8217;t know how The State obtained these messages, we can be fairly assured that were they obtained illegally by an ISP employee this person will be looking at criminal charges just as the college student that hacked Sarah Palin&#8217;s email account a few months back.</p>
<p>Don&#8217;t get me wrong, desktop-to-desktop encryption with a solution like PGP is good. But it takes a level of user sophistication and coordination generally not found in the populace. And, in the end, if the leak comes from someone with personal access to the local system it doesn&#8217;t matter how the messages are encrypted, they&#8217;ll be read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.mailprotector.com/blog/2009/06/announcements/does-governor-sanford-have-an-email-security-problem/260/comment-page-1#comment-26</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Fri, 26 Jun 2009 21:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailprotector.net/blog/?p=260#comment-26</guid>
		<description>David, you bring up a number of good points, particularly about the inherently insecure nature of email. As you say, there&#039;s a lot to learn in the Governor Sanford story.

Unfortunately, the security tips you recommend simply don&#039;t apply in this case. Don&#039;t get me wrong, they&#039;re certainly good advice. However, users must understand that SSL/TLS is not a panacea. It only protects the emails while in transit and does nothing to secure it while at rest -- either at an ISP or within your mail client.

A rogue administrator at an ISP could still read and divulge the information, even if TLS had been used. Email at the ISP would be stored in the clear, then (perhaps) re-transmitted over a secure wire...where it would be delivered to the destination, again in the clear.

Which means that if the second scenario occurred, a user with access to Sanford&#039;s email inbox could still have accessed the information. Even if the inbox was protected with a username/password, innumerable utilities can be found online to bypass this protection on most mail clients.

The only solution that truly addresses the problem is email encryption -- that is, encrypt the data, not just the pipe that carries it. This would protect against both scenarios you mention: neither the rogue admin, nor the &quot;trusted&quot; friend would be able to open the email.

Today, email encryption is very easy to use. The company I work for, PGP Corporation, specializes in making the process easier than ever (am I passionate on the topic because I work there, or do I work there because I&#039;m passionate about it? Hard to say).  But even without extra software, most mail clients offer message encryption built right in.

Given the pervasiveness  of email interception and inspection, combined with the increasing value (personal and commercial) of the information contained in email, isn&#039;t it time email encryption became the rule, instead of the exception? 

And, as more services move into the cloud, or hosted environments, these issues will only increase. As the industry evolves, security needs to be baked into the data, not added on to the pipe.</description>
		<content:encoded><![CDATA[<p>David, you bring up a number of good points, particularly about the inherently insecure nature of email. As you say, there&#8217;s a lot to learn in the Governor Sanford story.</p>
<p>Unfortunately, the security tips you recommend simply don&#8217;t apply in this case. Don&#8217;t get me wrong, they&#8217;re certainly good advice. However, users must understand that SSL/TLS is not a panacea. It only protects the emails while in transit and does nothing to secure it while at rest &#8212; either at an ISP or within your mail client.</p>
<p>A rogue administrator at an ISP could still read and divulge the information, even if TLS had been used. Email at the ISP would be stored in the clear, then (perhaps) re-transmitted over a secure wire&#8230;where it would be delivered to the destination, again in the clear.</p>
<p>Which means that if the second scenario occurred, a user with access to Sanford&#8217;s email inbox could still have accessed the information. Even if the inbox was protected with a username/password, innumerable utilities can be found online to bypass this protection on most mail clients.</p>
<p>The only solution that truly addresses the problem is email encryption &#8212; that is, encrypt the data, not just the pipe that carries it. This would protect against both scenarios you mention: neither the rogue admin, nor the &#8220;trusted&#8221; friend would be able to open the email.</p>
<p>Today, email encryption is very easy to use. The company I work for, PGP Corporation, specializes in making the process easier than ever (am I passionate on the topic because I work there, or do I work there because I&#8217;m passionate about it? Hard to say).  But even without extra software, most mail clients offer message encryption built right in.</p>
<p>Given the pervasiveness  of email interception and inspection, combined with the increasing value (personal and commercial) of the information contained in email, isn&#8217;t it time email encryption became the rule, instead of the exception? </p>
<p>And, as more services move into the cloud, or hosted environments, these issues will only increase. As the industry evolves, security needs to be baked into the data, not added on to the pipe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Means</title>
		<link>http://www.mailprotector.com/blog/2009/06/announcements/does-governor-sanford-have-an-email-security-problem/260/comment-page-1#comment-25</link>
		<dc:creator>Scott Means</dc:creator>
		<pubDate>Fri, 26 Jun 2009 17:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailprotector.net/blog/?p=260#comment-25</guid>
		<description>Great points, David! It&#039;s amazing how complex something &quot;simple&quot; like email can be. I&#039;m glad I have you guys to worry about issues like this for me so I can focus on things that I actually _know_ something about.</description>
		<content:encoded><![CDATA[<p>Great points, David! It&#8217;s amazing how complex something &#8220;simple&#8221; like email can be. I&#8217;m glad I have you guys to worry about issues like this for me so I can focus on things that I actually _know_ something about.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->