<?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: Sample PCI-DSS Policy Part 5: Critical Employee-Facing Technologies</title>
	<atom:link href="http://www.pcidssguru.com/policy/critical-employee-facing-technologies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pcidssguru.com/policy/critical-employee-facing-technologies/</link>
	<description>Practical Implementation Guidance on the Payment Card Industry Data Security Standard</description>
	<lastBuildDate>Tue, 31 Jan 2012 16:19:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Scotty Kazee</title>
		<link>http://www.pcidssguru.com/policy/critical-employee-facing-technologies/comment-page-1/#comment-4353</link>
		<dc:creator>Scotty Kazee</dc:creator>
		<pubDate>Sat, 16 Jul 2011 06:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=97#comment-4353</guid>
		<description>How is it that I by no means thought of this?</description>
		<content:encoded><![CDATA[<p>How is it that I by no means thought of this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schworak</title>
		<link>http://www.pcidssguru.com/policy/critical-employee-facing-technologies/comment-page-1/#comment-1328</link>
		<dc:creator>Schworak</dc:creator>
		<pubDate>Fri, 17 Sep 2010 15:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=97#comment-1328</guid>
		<description>Labeling doesn&#039;t need to be human readable nor does it need to contain the actual purpose of the device directly. The best way to do this is to place a CODE on each device and that code then in turn has a lookup on some other secured document. The logic is that you won&#039;t have a device sitting around wondering &quot;what is this for&quot;. It would be stupid to directly label any device as demonstrated by the previous comments which are totally correct and very entertaining at the same time.</description>
		<content:encoded><![CDATA[<p>Labeling doesn&#8217;t need to be human readable nor does it need to contain the actual purpose of the device directly. The best way to do this is to place a CODE on each device and that code then in turn has a lookup on some other secured document. The logic is that you won&#8217;t have a device sitting around wondering &#8220;what is this for&#8221;. It would be stupid to directly label any device as demonstrated by the previous comments which are totally correct and very entertaining at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph</title>
		<link>http://www.pcidssguru.com/policy/critical-employee-facing-technologies/comment-page-1/#comment-1200</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=97#comment-1200</guid>
		<description>I agree completely however I did put red stickers on my backups stating &#039;credit card info please steal and hack.&#039; It&#039;s important to be mindlessly compliant.</description>
		<content:encoded><![CDATA[<p>I agree completely however I did put red stickers on my backups stating &#8216;credit card info please steal and hack.&#8217; It&#8217;s important to be mindlessly compliant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Santa</title>
		<link>http://www.pcidssguru.com/policy/critical-employee-facing-technologies/comment-page-1/#comment-986</link>
		<dc:creator>Santa</dc:creator>
		<pubDate>Thu, 18 Mar 2010 13:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=97#comment-986</guid>
		<description>12.3.4 &quot;Purpose&quot;... Who with a security minded expertise would label their critical(eq sensitive!) systems with their purpose!?!?! Dont get this at all...</description>
		<content:encoded><![CDATA[<p>12.3.4 &#8220;Purpose&#8221;&#8230; Who with a security minded expertise would label their critical(eq sensitive!) systems with their purpose!?!?! Dont get this at all&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

