<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Call Center FAQ Significantly Changes</title>
	<atom:link href="http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/</link>
	<description>A common sense approach to achieving PCI compliance and retaining your sanity</description>
	<lastBuildDate>Tue, 18 Jun 2013 10:50:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Taking Credit Cards in Your Call Center? Better Read This...</title>
		<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/#comment-3535</link>
		<dc:creator><![CDATA[Taking Credit Cards in Your Call Center? Better Read This...]]></dc:creator>
		<pubDate>Tue, 10 Jul 2012 21:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=342#comment-3535</guid>
		<description><![CDATA[[...] Call Center FAQ Significantly Changes [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Call Center FAQ Significantly Changes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Call Center FAQ Changes &#8211; AGAIN &#171; PCI Guru</title>
		<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/#comment-218</link>
		<dc:creator><![CDATA[Call Center FAQ Changes &#8211; AGAIN &#171; PCI Guru]]></dc:creator>
		<pubDate>Thu, 18 Feb 2010 13:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=342#comment-218</guid>
		<description><![CDATA[[...] can be queried&#8221; language has returned as a qualifier regarding digital recordings.  See my post on this for additional [...]]]></description>
		<content:encoded><![CDATA[<p>[...] can be queried&#8221; language has returned as a qualifier regarding digital recordings.  See my post on this for additional [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john</title>
		<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/#comment-198</link>
		<dc:creator><![CDATA[john]]></dc:creator>
		<pubDate>Sun, 07 Feb 2010 05:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=342#comment-198</guid>
		<description><![CDATA[I have to agree, this is getting ridiculous. My real concern is the continuous use of the FAQ on the SSC&#039;s website to change PCI requirements. Just as recently last month they had a posting that said call centers have an exception to the storage of prohibited data if its not stored in a manner that is searchable. Not only have they taken that down, but have called out mp3s and wav files as being prohibited. 

They should wait till the new revisions of the DSS to make changes that impacting, not the FAQ.]]></description>
		<content:encoded><![CDATA[<p>I have to agree, this is getting ridiculous. My real concern is the continuous use of the FAQ on the SSC&#8217;s website to change PCI requirements. Just as recently last month they had a posting that said call centers have an exception to the storage of prohibited data if its not stored in a manner that is searchable. Not only have they taken that down, but have called out mp3s and wav files as being prohibited. </p>
<p>They should wait till the new revisions of the DSS to make changes that impacting, not the FAQ.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Call Center FAQ Significantly Changes « PCI Guru -- Topsy.com</title>
		<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/#comment-180</link>
		<dc:creator><![CDATA[Tweets that mention Call Center FAQ Significantly Changes « PCI Guru -- Topsy.com]]></dc:creator>
		<pubDate>Tue, 26 Jan 2010 19:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=342#comment-180</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by Veritape Ltd and Veritape Ltd, Howard Fuhs. Howard Fuhs said: PCI DSS - Call Center FAQ Significantly Changes - http://fuhs.eu/ah [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Veritape Ltd and Veritape Ltd, Howard Fuhs. Howard Fuhs said: PCI DSS &#8211; Call Center FAQ Significantly Changes &#8211; <a href="http://fuhs.eu/ah" rel="nofollow">http://fuhs.eu/ah</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott</title>
		<link>http://pciguru.wordpress.com/2010/01/25/call-center-faq-significantly-changes/#comment-178</link>
		<dc:creator><![CDATA[scott]]></dc:creator>
		<pubDate>Tue, 26 Jan 2010 14:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=342#comment-178</guid>
		<description><![CDATA[Now this is getting ridicules, I will be impressed when the PCI SCC finally adds rules that state the storage of clear text magnetic stripe data, CVV and other sensitive cardholder information is no longer allowed to be stored on card itself, since this seems to be the source of all the problems.]]></description>
		<content:encoded><![CDATA[<p>Now this is getting ridicules, I will be impressed when the PCI SCC finally adds rules that state the storage of clear text magnetic stripe data, CVV and other sensitive cardholder information is no longer allowed to be stored on card itself, since this seems to be the source of all the problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
