<?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: Saturday morning reading 01/24/09</title>
	<atom:link href="http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention.  The views expressed on this blog do not reflect the views of my employer or anyone other than myself.</description>
	<lastBuildDate>Thu, 02 Feb 2012 21:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Mike</title>
		<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/comment-page-1/#comment-4150</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 28 Jan 2009 05:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/#comment-4150</guid>
		<description>Being through the entire PCI DSS compliance with my company for the last 3 to 4 years I got the impression that one QSA could go into a site and determine something is an appropiate compensating control where another QSA would disagree. 

Grant it I don&#039;t find it as bad as HIPPA in trying to get compliant but as was stated above no matter how much money and time you throw at being or trying to be complaint you can almost always digg deep enough and find something that is not complaint. 

A QSA friend of mine put it best one time in a talk we was giving about securing a network. If a bear is chasing you, you don&#039;t have to run faster than the bear you just have to run faster than the person with you. You don&#039;t and probably won&#039;t have the most secure network but striving to be more secure than the next person will deter your average person attempting to breach your network.

Mike</description>
		<content:encoded><![CDATA[<p>Being through the entire PCI DSS compliance with my company for the last 3 to 4 years I got the impression that one QSA could go into a site and determine something is an appropiate compensating control where another QSA would disagree. </p>
<p>Grant it I don&#8217;t find it as bad as HIPPA in trying to get compliant but as was stated above no matter how much money and time you throw at being or trying to be complaint you can almost always digg deep enough and find something that is not complaint. </p>
<p>A QSA friend of mine put it best one time in a talk we was giving about securing a network. If a bear is chasing you, you don&#8217;t have to run faster than the bear you just have to run faster than the person with you. You don&#8217;t and probably won&#8217;t have the most secure network but striving to be more secure than the next person will deter your average person attempting to breach your network.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/comment-page-1/#comment-4148</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 28 Jan 2009 02:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/#comment-4148</guid>
		<description>I officially have no comment.  I unofficially have no comment.  As a Trustwave QSA, I can&#039;t make any comment on this.</description>
		<content:encoded><![CDATA[<p>I officially have no comment.  I unofficially have no comment.  As a Trustwave QSA, I can&#8217;t make any comment on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SecurityNinja</title>
		<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/comment-page-1/#comment-4147</link>
		<dc:creator>SecurityNinja</dc:creator>
		<pubDate>Wed, 28 Jan 2009 01:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/#comment-4147</guid>
		<description>Tough times for Trustwave and PCI DSS

Compliance management service provider and PCI QSA Trustwave appear to be having tough time recently. A colleague of mine pointed out today that Trustwave had been the QSA who certified RBS Worldpay as being compliant just 4 days before their data breach.

Fair enough, every one can get caught out now and then but I have also found out that Trustwave (all complaint companies and their assessors can be found here http://www.mastercard.com/us/sdp/assets/pdf/Compliant%20Service%20Providers%20-%20January%2015%202009.pdf) had also certified Heartlands as being compliant with PCI. If you have ignored the security news for a few days you would have missed the fact that Heartlands have also had breach of data which could top TJX as the largest breach ever. Heartlands process in excess of 100m transactions per month so I would imagine the amount of records lost could be immense.

Trustwave, I think the PCI Council should think about something George Bush once said: fool me once, shame on — shame on you. Fool me — you can’t get fooled again.

Dave

http://securityninja.co.uk/blog/?p=145</description>
		<content:encoded><![CDATA[<p>Tough times for Trustwave and PCI DSS</p>
<p>Compliance management service provider and PCI QSA Trustwave appear to be having tough time recently. A colleague of mine pointed out today that Trustwave had been the QSA who certified RBS Worldpay as being compliant just 4 days before their data breach.</p>
<p>Fair enough, every one can get caught out now and then but I have also found out that Trustwave (all complaint companies and their assessors can be found here <a href="http://www.mastercard.com/us/sdp/assets/pdf/Compliant%20Service%20Providers%20-%20January%2015%202009.pdf" rel="nofollow">http://www.mastercard.com/us/sdp/assets/pdf/Compliant%20Service%20Providers%20-%20January%2015%202009.pdf</a>) had also certified Heartlands as being compliant with PCI. If you have ignored the security news for a few days you would have missed the fact that Heartlands have also had breach of data which could top TJX as the largest breach ever. Heartlands process in excess of 100m transactions per month so I would imagine the amount of records lost could be immense.</p>
<p>Trustwave, I think the PCI Council should think about something George Bush once said: fool me once, shame on — shame on you. Fool me — you can’t get fooled again.</p>
<p>Dave</p>
<p><a href="http://securityninja.co.uk/blog/?p=145" rel="nofollow">http://securityninja.co.uk/blog/?p=145</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/comment-page-1/#comment-4140</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Mon, 26 Jan 2009 13:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/#comment-4140</guid>
		<description>Or two months after, when the QSA has come in and told them they&#039;re not going to pass the assessment.  

Martin</description>
		<content:encoded><![CDATA[<p>Or two months after, when the QSA has come in and told them they&#8217;re not going to pass the assessment.  </p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Branden Williams</title>
		<link>http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/comment-page-1/#comment-4129</link>
		<dc:creator>Branden Williams</dc:creator>
		<pubDate>Sat, 24 Jan 2009 16:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/24/saturday-morning-reading-012409/#comment-4129</guid>
		<description>I agree with your statements, however, that&#039;s why we created a service around managing compliance.  If a company takes it seriously, they will be able to hit those high-risk areas and avoid the breach by maintaining their compliance.

The problem is, most companies don&#039;t take it seriously until two months before their deadline.</description>
		<content:encoded><![CDATA[<p>I agree with your statements, however, that&#8217;s why we created a service around managing compliance.  If a company takes it seriously, they will be able to hit those high-risk areas and avoid the breach by maintaining their compliance.</p>
<p>The problem is, most companies don&#8217;t take it seriously until two months before their deadline.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

