<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Compliance != Security &#8211; the Titanic illustration</title>
	<atom:link href="http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/</link>
	<description>David D. Bergert</description>
	<lastBuildDate>Sat, 19 Nov 2011 16:52:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Two of my 2009 Predictions came true 2 weeks later &#124; Payment Systems Blog</title>
		<link>http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/comment-page-1/#comment-855</link>
		<dc:creator>Two of my 2009 Predictions came true 2 weeks later &#124; Payment Systems Blog</dc:creator>
		<pubDate>Thu, 22 Jan 2009 14:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/#comment-855</guid>
		<description>[...] before PCI compliance was a wide spread.&#160; Even organizations that are validated &quot;PCI Compliant&quot; will not be exempt. We will see attacks that adapt and change around current PCI [...]</description>
		<content:encoded><![CDATA[<p>[...] before PCI compliance was a wide spread.&#160; Even organizations that are validated &quot;PCI Compliant&quot; will not be exempt. We will see attacks that adapt and change around current PCI [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heartland Payment Systems Breach - My Thoughts &#124; Payment Systems Blog</title>
		<link>http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/comment-page-1/#comment-845</link>
		<dc:creator>Heartland Payment Systems Breach - My Thoughts &#124; Payment Systems Blog</dc:creator>
		<pubDate>Wed, 21 Jan 2009 14:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/#comment-845</guid>
		<description>[...] April 30th, 2008) If they were PCI compliant how did a breach occur ? It is important to note (again, and again) that Compliance != Security. Compliance is a snapshot in time, PCI is not based on an [...]</description>
		<content:encoded><![CDATA[<p>[...] April 30th, 2008) If they were PCI compliant how did a breach occur ? It is important to note (again, and again) that Compliance != Security. Compliance is a snapshot in time, PCI is not based on an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Payment Systems Blog : Predictions for 2009 &#124; Payment Systems Blog</title>
		<link>http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/comment-page-1/#comment-773</link>
		<dc:creator>Payment Systems Blog : Predictions for 2009 &#124; Payment Systems Blog</dc:creator>
		<pubDate>Thu, 08 Jan 2009 20:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/06/compliance-security-the-titanic-illustration/#comment-773</guid>
		<description>[...] before PCI compliance was a wide spread.&#160; Even organizations that are validated &quot;PCI Compliant&quot; will not be exempt. We will see attacks that adapt and change around current PCI [...]</description>
		<content:encoded><![CDATA[<p>[...] before PCI compliance was a wide spread.&#160; Even organizations that are validated &quot;PCI Compliant&quot; will not be exempt. We will see attacks that adapt and change around current PCI [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

