<?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: 100% Followup</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=420" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=420</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: Michael R. Farnum</title>
		<link>http://spiresecurity.com/?p=420&#038;cpage=1#comment-682</link>
		<dc:creator>Michael R. Farnum</dc:creator>
		<pubDate>Sun, 04 Jun 2006 17:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=420#comment-682</guid>
		<description><![CDATA[I really don&#039;t want to get into a tit for tat here, but I have to say that I never said fixing the issue was going to be easy (if that comment was directed at me).  I am a security practitioner, so I am well aware of the difficulties of securing a network and stopping stupid people from doing stupid things, magic wand or not.

However, none of that has any bearing on the original point.  We do NOT need to down play this issue, and stating that this is not posing much of a danger to vet&#039;s may have that exact effect.  The point that SSN&#039;s are easily accessible is not news to security professionals.  So by pointing that out to a reading audience of (I suspect) security professionals, you are not giving us anything earth-shattering.  It is not that the SSN&#039;s are out there.  The issue is that IT HAPPENED.  If that data can get out, so can some stuff that is really dangerous (in fact, the VA has admitted that other data besides SSN&#039;s, etc was on the laptop).  The pressure on the VA needs to be kept high.

I sincerely thank you for your service from a brother-in-arms.
]]></description>
		<content:encoded><![CDATA[<p>I really don&#8217;t want to get into a tit for tat here, but I have to say that I never said fixing the issue was going to be easy (if that comment was directed at me).  I am a security practitioner, so I am well aware of the difficulties of securing a network and stopping stupid people from doing stupid things, magic wand or not.</p>
<p>However, none of that has any bearing on the original point.  We do NOT need to down play this issue, and stating that this is not posing much of a danger to vet&#8217;s may have that exact effect.  The point that SSN&#8217;s are easily accessible is not news to security professionals.  So by pointing that out to a reading audience of (I suspect) security professionals, you are not giving us anything earth-shattering.  It is not that the SSN&#8217;s are out there.  The issue is that IT HAPPENED.  If that data can get out, so can some stuff that is really dangerous (in fact, the VA has admitted that other data besides SSN&#8217;s, etc was on the laptop).  The pressure on the VA needs to be kept high.</p>
<p>I sincerely thank you for your service from a brother-in-arms.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
