<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: More thoughts on &#8220;After the Breach&#8221;</title>
	<atom:link href="http://blog.eiqnetworks.com/2009/10/29/more-thoughts-on-after-the-breach/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.eiqnetworks.com/2009/10/29/more-thoughts-on-after-the-breach/</link>
	<description>Perspectives on Security and Compliance Management from eIQnetworks</description>
	<lastBuildDate>Thu, 29 Oct 2009 15:57:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Twitter Trackbacks for More thoughts on “After the Breach” « eIQviews [eiqnetworks.com] on Topsy.com</title>
		<link>http://blog.eiqnetworks.com/2009/10/29/more-thoughts-on-after-the-breach/#comment-224</link>
		<dc:creator>Twitter Trackbacks for More thoughts on “After the Breach” « eIQviews [eiqnetworks.com] on Topsy.com</dc:creator>
		<pubDate>Thu, 29 Oct 2009 15:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eiqnetworks.com/?p=302#comment-224</guid>
		<description>[...] More thoughts on “After the Breach” « eIQviews  blog.eiqnetworks.com/2009/10/29/more-thoughts-on-after-the-breach &#8211; view page &#8211; cached  A couple of days ago, the folks at McAfee put up a very good blog post really delving into the specifics of what to do when you find a data breach. &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<p>[...] More thoughts on “After the Breach” « eIQviews  blog.eiqnetworks.com/2009/10/29/more-thoughts-on-after-the-breach &ndash; view page &ndash; cached  A couple of days ago, the folks at McAfee put up a very good blog post really delving into the specifics of what to do when you find a data breach. &mdash; From the page [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
