<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Admin Blog &#187; dss</title>
	<atom:link href="http://www.webadminblog.com/index.php/tag/dss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webadminblog.com</link>
	<description>Real Web Admins.  Real World Experience.</description>
	<lastBuildDate>Thu, 22 Jul 2010 16:18:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>PCI Compliance &#8211; Convert Drudgery Into a Powerful Security Framework</title>
		<link>http://www.webadminblog.com/index.php/2009/03/24/pci-compliance-convert-drudgery-into-a-powerful-security-framework/</link>
		<comments>http://www.webadminblog.com/index.php/2009/03/24/pci-compliance-convert-drudgery-into-a-powerful-security-framework/#comments</comments>
		<pubDate>Tue, 24 Mar 2009 22:00:26 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[TRISC 2009]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[dss]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.webadminblog.com/?p=213</guid>
		<description><![CDATA[For my last session of the day at TRISC 2009, I decided to attend Joseph Krull's presentation on PCI Compliance.  Joe works as a consultant for Accenture and has performed 60+ PCI engagements for various companies.  If your organization does any processing of credit card information, my notes from that session below should be useful: [...]]]></description>
			<content:encoded><![CDATA[<p>For my last session of the day at TRISC 2009, I decided to attend Joseph Krull's presentation on PCI Compliance.  Joe works as a consultant for Accenture and has performed 60+ PCI engagements for various companies.  If your organization does any processing of credit card information, my notes from that session below should be useful:</p>
<ul>
<li>As many as 65% of merchants are still not PCI compliant</li>
<li>Fines can be just the beginning; service charges and market share price dilution for non-compliant merchants have already had substantial repercussions in the US and may soon reach other regions·</li>
<li>Many retailers still don’t have a clear view of compliance, and cannot effectively identify gaps</li>
<li>The first steps to PCI compliance are a thorough internal assessment and gap analysis – many merchants skip these steps and launch multiple costly projects</li>
<li>PCI provides a regulatory and compliance framework to help prevent credit card fraud for organizations that process card payments</li>
<li>The framework is comprehensive and effective but adherence to the specific standards is often challenging – primarily due to the complexities involved in both program design and implementation</li>
<li>Any merchant that accepts or processes credit cards must maintain compliance with the PCI DSS.  Specific obligations vary based on transaction volumes.</li>
<li>Focus right now is on the Level 4’s.</li>
<li> TJX subject to 20 years of mandatory computer systems audits after massive breach</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Challenges</strong></span></p>
<ul>
<li>Providing adequate and clear program management for all of the entire spectrum of PCI remediation activities (60-70% give to “Compliance guy” and typically fail.  Should go to senior security guy)</li>
<li>Accurately scoping requirements throughout the organization, including remote sites and international operations</li>
<li>Evaluating and then implementing a wide variety of complex technologies – including encryption</li>
<li>Redesigning or replacing internal applications and payment systems to adequately protect cardholder data</li>
<li>Developing, implementing and enforcing new or revised policies and procedures across the entire organization</li>
<li>Differing opinions with auditors regarding PCI compliance requirements, especially related to the concept of “Compensating Controls”</li>
<li>Verifying PCI compliance for 3rd party partners that process data on behalf of the merchant</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Differences from PCI DSS 1.1 to 1.2</strong></span></p>
<ul>
<li>Active monitoring plans for all 3rd party PCI Service Providers (Requirement 12.8)</li>
<li>Visits to offsite data storage locations at least annually</li>
<li>Mandatory phase out of weak encryption for wireless networks</li>
<li>Additional requirements for the use of “Compensating Controls” for specific PCI security requirements</li>
<li>Assessor testing procedures changed from “Observe the use of…” to “Verify the use of”</li>
<li>Quality assurance program for PCI assessors</li>
<li>Process restricts or eliminates assessors from performing PCI work due to poor quality assessments</li>
<li>Assessors must now go beyond cursory observation of security controls and provide statistical samples</li>
<li>Assessors now going much deeper to include verifying individual system settings, requesting and analyzing configuration files, studying data flows, …</li>
</ul>
<p><span style="text-decoration: underline;"><strong>The Cost of Compliance and Non-Compliance</strong></span></p>
<ul>
<li>According to a comprehensive Forrester Research report on PCI compliance, companies spend between 2%-10% of their IT budget on PCI compliance</li>
<li>Credit card companies are levying fines on non-compliant merchants
<ul>
<li>Up to $25,000 per month for each month of non-compliance for L1’s ($5,000 for L4’s)</li>
<li>$10,000-$100,000 per month for prohibited storage of magnetic stripe data</li>
<li>Up to $500,000 per incident if a confirmed compromise occurs</li>
<li>Continued non-compliance may result in revocation of CC processing privileges</li>
</ul>
</li>
<li>Banks and acquirers may increase processing fees for non-complinat merchants.  In 2008, one retailer estimated an annual increase in operational costs of $18 million due to this increase in processing fees on VISA card transactions alone.</li>
<li>Banks and acquirers can often pass on damages they incur to merchants</li>
<li>Repeat or additional PCI assessments &amp; internal audits</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Corporate Compliance Framework</strong></span></p>
<ul>
<li>Although PCI provides compliance requirements in most areas, it’s only a subset</li>
<li>ISO 27002:2005 is what they used for PCI</li>
<li>Good general requirements, but no explanation on how to do it</li>
<li>PCI sets best practices</li>
<li>For example, ISO 5.1.1 maps to PCI 12.1, 12.4, and 12.6.2</li>
</ul>
<p><span style="text-decoration: underline;"><strong>How to “Sell” PCI Compliance to Senior Management</strong></span></p>
<ul>
<li>Gloom and Doom
<ul>
<li>Fines and sanctions will sink us</li>
<li>Probability of success 40-50%</li>
</ul>
</li>
<li>The PCI Umbrella
<ul>
<li>We need these 15 projects and ten new security products to be PCI compliant</li>
<li>Probability of success 40-50%</li>
<li>Who has done the gap assessment</li>
</ul>
</li>
<li>The Long Term Approach
<ul>
<li>If we achieve PCI compliance we will also be well on our way to other requirements</li>
</ul>
</li>
<li>PCI compliance is not a project or technology based solution – it is being able to demonstrate that an organization has the means in place to protect sensitive information</li>
<li>Use as a building block to sell to senior management</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2009/03/24/pci-compliance-convert-drudgery-into-a-powerful-security-framework/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
