<?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 6: Roles and Responsibilities</title>
	<atom:link href="http://www.pcidssguru.com/policy/roles-and-responsibilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pcidssguru.com/policy/roles-and-responsibilities/</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: Chuck</title>
		<link>http://www.pcidssguru.com/policy/roles-and-responsibilities/comment-page-1/#comment-15346</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Tue, 24 Jan 2012 15:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=103#comment-15346</guid>
		<description>I subscribed to the newsletter. can you please send the policy template to me?</description>
		<content:encoded><![CDATA[<p>I subscribed to the newsletter. can you please send the policy template to me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.pcidssguru.com/policy/roles-and-responsibilities/comment-page-1/#comment-2425</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 05 Apr 2011 10:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=103#comment-2425</guid>
		<description>Please remember the PCI standard is there to protect your data. Just re-writing existing peoples work isn&#039;t ideal. You will tend to skip other the actual point of the standard in favour of the &quot;just tick the box&quot; method.

You (depending on your merchant level) need to prove what you say in the policies. I had to write up something like 26 new policies. And document how, why and when certain procedures are performed. All employee&#039;s had to re-sign a acceptable use policy etc etc etc....it is alot of work but worth it.</description>
		<content:encoded><![CDATA[<p>Please remember the PCI standard is there to protect your data. Just re-writing existing peoples work isn&#8217;t ideal. You will tend to skip other the actual point of the standard in favour of the &#8220;just tick the box&#8221; method.</p>
<p>You (depending on your merchant level) need to prove what you say in the policies. I had to write up something like 26 new policies. And document how, why and when certain procedures are performed. All employee&#8217;s had to re-sign a acceptable use policy etc etc etc&#8230;.it is alot of work but worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.pcidssguru.com/policy/roles-and-responsibilities/comment-page-1/#comment-1355</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 28 Sep 2010 20:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.pcidssguru.com/?p=103#comment-1355</guid>
		<description>Is just rewriting all of this enough for the security policy. Do we have to create a whole incident response policy that goes in detail through the questions of 12.9.1?</description>
		<content:encoded><![CDATA[<p>Is just rewriting all of this enough for the security policy. Do we have to create a whole incident response policy that goes in detail through the questions of 12.9.1?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

