<?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: Taming THE PCI Beast &#8211; 7 Steps For Easier Compliance</title>
	<atom:link href="https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/</link>
	<description>All about e-Commerce, ShopSite, and Web Hosting</description>
	<lastBuildDate>Thu, 16 Dec 2021 19:59:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.2.1</generator>
	<item>
		<title>By: Joseph Jeffrey</title>
		<link>https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/#comment-17812</link>
		<dc:creator><![CDATA[Joseph Jeffrey]]></dc:creator>
		<pubDate>Mon, 26 Sep 2011 21:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.lexiconn.com/blog/?p=1432#comment-17812</guid>
		<description><![CDATA[PCI compliance &quot;requirements&quot; are a ridiculous and expensive burden on small business owners.  It&#039;s another example of banks ripping off the public and over-regulation.  I suspect many small business owners fudge the responses to make compliance easier or just pay the extra fees for non-compliance.  In the long run, the PCI process is doomed to failure and will be abandoned as unworkable. UGH]]></description>
		<content:encoded><![CDATA[<p>PCI compliance &#8220;requirements&#8221; are a ridiculous and expensive burden on small business owners.  It&#8217;s another example of banks ripping off the public and over-regulation.  I suspect many small business owners fudge the responses to make compliance easier or just pay the extra fees for non-compliance.  In the long run, the PCI process is doomed to failure and will be abandoned as unworkable. UGH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Mangiafico</title>
		<link>https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/#comment-1791</link>
		<dc:creator><![CDATA[Rob Mangiafico]]></dc:creator>
		<pubDate>Tue, 09 Mar 2010 01:45:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lexiconn.com/blog/?p=1432#comment-1791</guid>
		<description><![CDATA[Thanks for the comment. Yes, I agree, any third party vendor that handles card data must also be PCI compliant.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comment. Yes, I agree, any third party vendor that handles card data must also be PCI compliant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Contrarian View</title>
		<link>https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/#comment-1785</link>
		<dc:creator><![CDATA[Contrarian View]]></dc:creator>
		<pubDate>Mon, 08 Mar 2010 23:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.lexiconn.com/blog/?p=1432#comment-1785</guid>
		<description><![CDATA[Good article, but I seemed to read &quot;recommended&quot; rather than &quot;required.&quot; To be PCI Compliant, a merchant using a third party vendor with access to card information (such as an internet gateway) MUST be PCI Compliant. If the merchant has validated PCI Compliance for itself, but is then using a Noncompliant third party (with access to card info), then the merchant is defacto Noncompliant.

Did not notice that mentioned in the article.

Thanks.]]></description>
		<content:encoded><![CDATA[<p>Good article, but I seemed to read &#8220;recommended&#8221; rather than &#8220;required.&#8221; To be PCI Compliant, a merchant using a third party vendor with access to card information (such as an internet gateway) MUST be PCI Compliant. If the merchant has validated PCI Compliance for itself, but is then using a Noncompliant third party (with access to card info), then the merchant is defacto Noncompliant.</p>
<p>Did not notice that mentioned in the article.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>https://www.lexiconn.com/blog/2010/02/taming-the-pci-beast-7-steps-for-easier-compliance/#comment-1605</link>
		<dc:creator><![CDATA[uberVU - social comments]]></dc:creator>
		<pubDate>Tue, 16 Feb 2010 15:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.lexiconn.com/blog/?p=1432#comment-1605</guid>
		<description><![CDATA[&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by LexiConn_Inc: Taming THE PCI Beast - 7 Steps For Easier Compliance  http://bit.ly/bZdYTb #pci #ecommerce...]]></description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by LexiConn_Inc: Taming THE PCI Beast &#8211; 7 Steps For Easier Compliance  <a href="http://bit.ly/bZdYTb" rel="nofollow">http://bit.ly/bZdYTb</a> #pci #ecommerce&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
