<?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: Risk and PCI-DSS</title>
	<atom:link href="http://risktical.com/2008/12/17/risk-and-pci-dss/feed/" rel="self" type="application/rss+xml" />
	<link>http://risktical.com/2008/12/17/risk-and-pci-dss/</link>
	<description>Assessing, Articulating &#38; Quantifying Information Security Risk</description>
	<lastBuildDate>Fri, 04 Jun 2010 19:07:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jack</title>
		<link>http://risktical.com/2008/12/17/risk-and-pci-dss/#comment-161</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Tue, 23 Dec 2008 12:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=132#comment-161</guid>
		<description>Chris,

You mention &quot;showing due care&quot; to customers, etc., but I would submit that PCI as &quot;due care&quot; is a bit of a Potemkin Village -- i.e., the appearance of due care, but without substance.  This isn&#039;t completely true, of course, as PCI compliance does reflect an attempt at due diligence.  Actual due care would be better reflected in being able to prioritize risk issues effectively (which PCI absolutely fails on) and cost-effective control selection (which PCI doesn&#039;t address).  

Thanks,
Jack</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>You mention &#8220;showing due care&#8221; to customers, etc., but I would submit that PCI as &#8220;due care&#8221; is a bit of a Potemkin Village &#8212; i.e., the appearance of due care, but without substance.  This isn&#8217;t completely true, of course, as PCI compliance does reflect an attempt at due diligence.  Actual due care would be better reflected in being able to prioritize risk issues effectively (which PCI absolutely fails on) and cost-effective control selection (which PCI doesn&#8217;t address).  </p>
<p>Thanks,<br />
Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2008/12/17/risk-and-pci-dss/#comment-160</link>
		<dc:creator>Chris Hayes</dc:creator>
		<pubDate>Sun, 21 Dec 2008 20:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=132#comment-160</guid>
		<description>@Travis – Right, wrong or indifferent – PCI-DSS is quickly - or already is in certain circles - becoming the &quot;standard”. There is no reason not to presume that other regulatory/oversight bodies - whether government or private – will not adopt PCI-DSS or the like. I have found this to be a great “contributing factor” in regards to explaining the exposure of not being complaint over the long run to business decision makers. To be honest - a lot of the standards are common sense and overlap with with what FRC auditors are looking for, as well as Internal Audit groups for organizations that are large enough to have them.

Thanks for commenting as well as reading my blog! Happy Holidays!</description>
		<content:encoded><![CDATA[<p>@Travis – Right, wrong or indifferent – PCI-DSS is quickly &#8211; or already is in certain circles &#8211; becoming the &#8220;standard”. There is no reason not to presume that other regulatory/oversight bodies &#8211; whether government or private – will not adopt PCI-DSS or the like. I have found this to be a great “contributing factor” in regards to explaining the exposure of not being complaint over the long run to business decision makers. To be honest &#8211; a lot of the standards are common sense and overlap with with what FRC auditors are looking for, as well as Internal Audit groups for organizations that are large enough to have them.</p>
<p>Thanks for commenting as well as reading my blog! Happy Holidays!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://risktical.com/2008/12/17/risk-and-pci-dss/#comment-159</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Fri, 19 Dec 2008 22:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=132#comment-159</guid>
		<description>The problem with comparing risk to compliance in dollar values is taking into account the fact of a data breach.  If a company&#039;s data is lost, there is the cost of damaging the company&#039;s public image.   Which in the long run can be much more harmful, especially in today&#039;s economy where consumers are wanting to stretch their dollars further.  What a company needs is a solution which is more cost effective to them and can do more then just get them PCI complaint, but get them closer to being compliant with other regulations.</description>
		<content:encoded><![CDATA[<p>The problem with comparing risk to compliance in dollar values is taking into account the fact of a data breach.  If a company&#8217;s data is lost, there is the cost of damaging the company&#8217;s public image.   Which in the long run can be much more harmful, especially in today&#8217;s economy where consumers are wanting to stretch their dollars further.  What a company needs is a solution which is more cost effective to them and can do more then just get them PCI complaint, but get them closer to being compliant with other regulations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
