<?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: Guide to Becoming PCI Compliant: A Historical Perspective and Introduction</title>
	<atom:link href="http://resource.onlinetech.com/guide-to-becoming-pci-compliant-a-historical-perspective-and-introduction/feed/" rel="self" type="application/rss+xml" />
	<link>http://resource.onlinetech.com/guide-to-becoming-pci-compliant-a-historical-perspective-and-introduction/</link>
	<description>A Guide to Managed Hosting</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:27:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The Six Principles of PCI Compliance</title>
		<link>http://resource.onlinetech.com/guide-to-becoming-pci-compliant-a-historical-perspective-and-introduction/comment-page-1/#comment-170</link>
		<dc:creator>The Six Principles of PCI Compliance</dc:creator>
		<pubDate>Wed, 21 Jul 2010 18:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://resource.onlinetech.com/?p=1247#comment-170</guid>
		<description>[...] first blog in this series provided a historical overview and introduction to PCI compliance.  This blog provides an overview of PCI DSS, which is aligned into 6 principles of PCI compliance [...]</description>
		<content:encoded><![CDATA[<p>[...] first blog in this series provided a historical overview and introduction to PCI compliance.  This blog provides an overview of PCI DSS, which is aligned into 6 principles of PCI compliance [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Della Lowe</title>
		<link>http://resource.onlinetech.com/guide-to-becoming-pci-compliant-a-historical-perspective-and-introduction/comment-page-1/#comment-160</link>
		<dc:creator>Della Lowe</dc:creator>
		<pubDate>Wed, 31 Mar 2010 13:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://resource.onlinetech.com/?p=1247#comment-160</guid>
		<description>This article was very interesting IMHO in that Adam emphasized the security aspect of the PCI DSS. While it is not all that hard to get a checkmark in various areas, that often comes at the cost of real, ongoing security. If you take care of the security, especially in an automated 24x7 way, the compliance becomes just about free. If, however, you just want that checkmark, you may achieve PCI compliance on paper but you will not maintain it, as Adam suggests you should, or be safe from attack.

My company helps our customers meet and exceed the PCI requirements for wireless scanning by concentrating on security and I was glad to see Adam focusing that way as well. I liken the checkmark to putting an ADT sign in the front of your house and hoping that the burglars won&#039;t find out that you don;t have a security system or that you leave the door unlocked most of the time.</description>
		<content:encoded><![CDATA[<p>This article was very interesting IMHO in that Adam emphasized the security aspect of the PCI DSS. While it is not all that hard to get a checkmark in various areas, that often comes at the cost of real, ongoing security. If you take care of the security, especially in an automated 24&#215;7 way, the compliance becomes just about free. If, however, you just want that checkmark, you may achieve PCI compliance on paper but you will not maintain it, as Adam suggests you should, or be safe from attack.</p>
<p>My company helps our customers meet and exceed the PCI requirements for wireless scanning by concentrating on security and I was glad to see Adam focusing that way as well. I liken the checkmark to putting an ADT sign in the front of your house and hoping that the burglars won&#8217;t find out that you don;t have a security system or that you leave the door unlocked most of the time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
