<?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: If Everyone in the U.S. has their SSN stolen&#8230;</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=216" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=216</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=216&#038;cpage=1#comment-310</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 11 Jan 2008 14:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=216#comment-310</guid>
		<description><![CDATA[@Matthijs -

I agree wholeheartedly, though perhaps more vehemently. ;-)

Pete
]]></description>
		<content:encoded><![CDATA[<p>@Matthijs -</p>
<p>I agree wholeheartedly, though perhaps more vehemently. <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthijs Koot</title>
		<link>http://spiresecurity.com/?p=216&#038;cpage=1#comment-309</link>
		<dc:creator>Matthijs Koot</dc:creator>
		<pubDate>Fri, 11 Jan 2008 14:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=216#comment-309</guid>
		<description><![CDATA[This idea occured to me too (after the recent data loss/theft incidents in the UK), and here is how I was looking at it. The SSN has historically been regarded to be a personal secret and was (understandably) used as a means of authentication, has it not? Assuming that this still is somewhat the case: if everyone loses their SSN (or its newly born Dutch cousin &#039;Burger Service Nummer&#039; when taking a view from the Netherlands where I live), the remaining value of it as a means of authentication (finally) drops to zero.

If everyone&#039;s SSN is publicly known, governmental, financial and commercial institutions are forced to (finally) move away from accepting mere knowledge of some personal information as sufficient way of authentication to buy some service. This, then, mitigates each individual&#039;s risk of having their personal data be abused throughout such practices. Ofcourse this is all very speculative.

Unfortunately, disclosing everyone&#039;s SSN, intentionally or not, might ring in the first phase of a privacy disaster. Then again, the latter is perhaps a dying and cliché way of looking at things.
]]></description>
		<content:encoded><![CDATA[<p>This idea occured to me too (after the recent data loss/theft incidents in the UK), and here is how I was looking at it. The SSN has historically been regarded to be a personal secret and was (understandably) used as a means of authentication, has it not? Assuming that this still is somewhat the case: if everyone loses their SSN (or its newly born Dutch cousin &#8216;Burger Service Nummer&#8217; when taking a view from the Netherlands where I live), the remaining value of it as a means of authentication (finally) drops to zero.</p>
<p>If everyone&#8217;s SSN is publicly known, governmental, financial and commercial institutions are forced to (finally) move away from accepting mere knowledge of some personal information as sufficient way of authentication to buy some service. This, then, mitigates each individual&#8217;s risk of having their personal data be abused throughout such practices. Ofcourse this is all very speculative.</p>
<p>Unfortunately, disclosing everyone&#8217;s SSN, intentionally or not, might ring in the first phase of a privacy disaster. Then again, the latter is perhaps a dying and cliché way of looking at things.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
