<?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: Heartland and RBS De-listed From PCI List</title>
	<atom:link href="http://blog.nikolaidis.com/2009/03/17/heartland-and-rbs-de-listed-from-pci-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nikolaidis.com/2009/03/17/heartland-and-rbs-de-listed-from-pci-list/</link>
	<description>Aikido, comics, eating well, information security, open source, mountain biking, and caffeine - this blog has everything!</description>
	<lastBuildDate>Mon, 14 Jun 2010 01:57:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: bill_mcgonigle</title>
		<link>http://blog.nikolaidis.com/2009/03/17/heartland-and-rbs-de-listed-from-pci-list/comment-page-1/#comment-41062</link>
		<dc:creator>bill_mcgonigle</dc:creator>
		<pubDate>Tue, 17 Mar 2009 20:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nikolaidis.com/?p=454#comment-41062</guid>
		<description>&lt;blockquote&gt;By taking the payment processors off its list of certified providers, Visa is &quot;offering a passive opinion of the PCI standard, which is that it doesn&#039;t amount to much in the end,&quot; Schneier said.&lt;/blockquote&gt;

I bet if Visa started charging them 1% more on every transaction until they got into compliance it&#039;d never happen again.  PCI, from the audits I&#039;ve been through, looks like a list put together by a college intern reading C&#124;Net news articles about break-ins and doesn&#039;t come close to ensuring a secure environment.  Unfortunately several of the more baroque requirements, especially in the first versions, lead to high merchant costs and lowered security (e.g. hashed passwords were forbidden, only crypt()&#039;ed was allowed; line-printers required for system logs, etc.).  All so Visa doesn&#039;t have to spend money on post-1960&#039;s security!

I wonder if they&#039;ll release details.  &#039;Malware&#039; makes it sound like some n00b was using unsecured Windows on a secure network.</description>
		<content:encoded><![CDATA[<blockquote><p>By taking the payment processors off its list of certified providers, Visa is &#8220;offering a passive opinion of the PCI standard, which is that it doesn&#8217;t amount to much in the end,&#8221; Schneier said.</p></blockquote>
<p>I bet if Visa started charging them 1% more on every transaction until they got into compliance it&#8217;d never happen again.  PCI, from the audits I&#8217;ve been through, looks like a list put together by a college intern reading C|Net news articles about break-ins and doesn&#8217;t come close to ensuring a secure environment.  Unfortunately several of the more baroque requirements, especially in the first versions, lead to high merchant costs and lowered security (e.g. hashed passwords were forbidden, only crypt()&#8217;ed was allowed; line-printers required for system logs, etc.).  All so Visa doesn&#8217;t have to spend money on post-1960&#8242;s security!</p>
<p>I wonder if they&#8217;ll release details.  &#8216;Malware&#8217; makes it sound like some n00b was using unsecured Windows on a secure network.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
