 




<?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>Regulatory Compliance, Governance and Security &#187; intrusion detection system</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/compliance-governance/tag/intrusion-detection-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/compliance-governance</link>
	<description></description>
	<lastBuildDate>Thu, 10 Mar 2011 15:04:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>PCI DSS Compliance &#124; Watch out for the &#8220;Road Blocks&#8221;</title>
		<link>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-compliance-watch-out-for-the-road-blocks/</link>
		<comments>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-compliance-watch-out-for-the-road-blocks/#comments</comments>
		<pubDate>Sat, 29 Aug 2009 13:31:41 +0000</pubDate>
		<dc:creator>Charles Denyer</dc:creator>
				<category><![CDATA[charles denyer]]></category>
		<category><![CDATA[intrusion detection system]]></category>
		<category><![CDATA[merchants]]></category>
		<category><![CDATA[pci dss compliance]]></category>
		<category><![CDATA[qsa]]></category>
		<category><![CDATA[qualified security assessor]]></category>
		<category><![CDATA[report on compliance]]></category>
		<category><![CDATA[ROC]]></category>
		<category><![CDATA[service providers]]></category>
		<category><![CDATA[software code review]]></category>
		<category><![CDATA[two factor authentication]]></category>
		<category><![CDATA[web application firewall]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-compliance-watch-out-for-the-road-blocks/</guid>
		<description><![CDATA[PCI DSS Compliance, especially on-site reviews conducted by a Qualified Security Assessor (QSA), can take an immense amount of time in completing and receiving one&#8217;s Report on Compliance (ROC). What most merchants and service providers fail to recognize is that there are numerous issues that could potentially cause &#8220;roadblocks&#8221; on the way to achieving PCI [...]]]></description>
				<content:encoded><![CDATA[<p>PCI DSS Compliance, especially on-site reviews conducted by a Qualified Security Assessor (QSA), can take an immense amount of time in completing and receiving one&#8217;s Report on Compliance (ROC).<br />
What most merchants and service providers fail to recognize is that there are numerous issues that could potentially cause &#8220;roadblocks&#8221; on the way to achieving PCI DSS compliance.</p>
<p>As a QSA, I&#8217;ve listed some examples of common items that require remediation prior to achieving compliance. These items are considered major &#8220;roadblocks&#8221; because of either the time, money and investment needed to incorporate them into the cardholder data environment:</p>
<p>1. Two-factor authentication<br />
2. Web application firewall and/or software code reviews.<br />
3. Intrusion Detection Systems (IDS)<br />
4. Documented Policies and Procedures specifically related to PCI DSS compliance.</p>
<p>These four items are typically what catch merchants and service organizations off-guard. Be prepared, be proactive; find a quality, competent <strong><a href="http://www.pciassessment.org">QSA</a> </strong>to help with all your PCI DSS compliance needs.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-compliance-watch-out-for-the-road-blocks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
