<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Compliance Software &#187; mastercard</title>
	<atom:link href="http://compliancesoftware.org/tag/mastercard/feed/" rel="self" type="application/rss+xml" />
	<link>http://compliancesoftware.org</link>
	<description>Regulatory Compliance Software - News Information and Links</description>
	<lastBuildDate>Thu, 09 Sep 2010 14:40:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Roundup of largest data breaches / incidents</title>
		<link>http://compliancesoftware.org/2010/09/07/roundup-of-largest-data-breaches-incidents/</link>
		<comments>http://compliancesoftware.org/2010/09/07/roundup-of-largest-data-breaches-incidents/#comments</comments>
		<pubDate>Tue, 07 Sep 2010 14:31:31 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[Data Security]]></category>
		<category><![CDATA[american express]]></category>
		<category><![CDATA[breach]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[pan]]></category>
		<category><![CDATA[payment]]></category>
		<category><![CDATA[visa]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=1126</guid>
		<description><![CDATA[records date organizations 130,000,000 2009-01-20 Heartland Payment Systems, Tower Federal Credit Union, Beverly National Bank 94,000,000 2007-01-17 TJX Companies Inc. 90,000,000 1984-06-01 TRW, Sears Roebuck 76,000,000 2009-10-05 National Archives and Records Administration 40,000,000 2005-06-19 CardSystems, Visa, MasterCard, American Express 26,500,000 2006-05-22 U.S. Department of Veterans Affairs 25,000,000 2007-11-20 HM Revenue and Customs, TNT 17,000,000 2008-10-06 [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2010/09/07/roundup-of-largest-data-breaches-incidents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>3-D Secure (3DS) &#8211; Verified by Visa insecure</title>
		<link>http://compliancesoftware.org/2010/02/04/3-d-secure-3ds-verified-by-visa-insecure/</link>
		<comments>http://compliancesoftware.org/2010/02/04/3-d-secure-3ds-verified-by-visa-insecure/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 17:16:35 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[payment]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[visa]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=860</guid>
		<description><![CDATA[Security Researchers in the UK say that the 3-D Secure (3DS) system for credit card authorization, a protocol that was &#8220;developed by Visa to improve the security of Internet payments,&#8221; has significant security weaknesses. It is used by both of the ginormous card brands, known as &#8220;Verified by Visa&#8221; and &#8220;MasterCard SecureCode.&#8221; via The Forrester Blog [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2010/02/04/3-d-secure-3ds-verified-by-visa-insecure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI DSS Names New Chair</title>
		<link>http://compliancesoftware.org/2010/01/27/pci-dss-names-new-chair/</link>
		<comments>http://compliancesoftware.org/2010/01/27/pci-dss-names-new-chair/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 00:07:16 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[announce]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[industry]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[payment]]></category>
		<category><![CDATA[payment card industry]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=840</guid>
		<description><![CDATA[On Jan 25th, the PCI Security Standards Council, a global, open industry standards body providing management of the Payment Card Industry Data Security Standard (PCI DSS), PIN Transaction Security (PTS) Security Requirements and the Payment Application Data Security Standard (PA-DSS), announced that Bruce Rutherford, group head, fraud management solutions, payment system integrity, MasterCard, has been [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2010/01/27/pci-dss-names-new-chair/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard: December PCI Deadline Change Not For Holiday Conflict</title>
		<link>http://compliancesoftware.org/2010/01/07/mastercard-december-pci-deadline-change-not-for-holiday-conflict/</link>
		<comments>http://compliancesoftware.org/2010/01/07/mastercard-december-pci-deadline-change-not-for-holiday-conflict/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 13:52:20 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[manager]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=816</guid>
		<description><![CDATA[MasterCard’s decision to reverse itself on its end of year 2010 deadline for new Level 2 PCI requirements was not based on retail complaints or on avoiding the hectic holiday period for merchants, according to a key MasterCard manager heading up the effort. Instead, the change was based on giving retailers more time to work [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2010/01/07/mastercard-december-pci-deadline-change-not-for-holiday-conflict/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard Blinks, Drops Dec. 31 Level 2 PCI Deadline</title>
		<link>http://compliancesoftware.org/2009/12/18/mastercard-blinks-drops-dec-31-level-2-pci-deadline/</link>
		<comments>http://compliancesoftware.org/2009/12/18/mastercard-blinks-drops-dec-31-level-2-pci-deadline/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 03:13:32 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[visa]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=804</guid>
		<description><![CDATA[The first MasterCard change made this month was pushing the Dec. 31, 2010, deadline back six months, to June 30, 2011. But MasterCard has also made two other key PCI changes. It has redefined what Level a retailer is (Level 1, 2, 3 or 4) to explicitly mirror whatever level Visa has determined. (The language [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/12/18/mastercard-blinks-drops-dec-31-level-2-pci-deadline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Human Train Wreck Coming Next Year For Level 2s</title>
		<link>http://compliancesoftware.org/2009/11/30/pci-human-train-wreck-coming-next-year-for-level-2s/</link>
		<comments>http://compliancesoftware.org/2009/11/30/pci-human-train-wreck-coming-next-year-for-level-2s/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 02:01:43 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[announce]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=768</guid>
		<description><![CDATA[Many Level 2 merchants are just now realizing that their PCI world has changed. Under rules announced this summer, Level 2 MasterCard merchants—like their Level 1 brethren—will require an onsite assessment by a QSA starting in 2010. via StorefrontBacktalk » Blog Archive » PCI Human Train Wreck Coming Next Year For Level 2s.]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/11/30/pci-human-train-wreck-coming-next-year-for-level-2s/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard Vs. Visa: Dueling Compliance Philosophies</title>
		<link>http://compliancesoftware.org/2009/08/19/mastercard-vs-visa-dueling-compliance-philosophies/</link>
		<comments>http://compliancesoftware.org/2009/08/19/mastercard-vs-visa-dueling-compliance-philosophies/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 12:27:56 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[visa]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=619</guid>
		<description><![CDATA[People don’t seem to “get” MasterCard. For most of the last 4 years, MasterCard has been criticized for their apparent willingness to let Visa play the “bad guy” who issues fines to acquiring banks (and, through them, to merchants), who extends the PCI standards to application vendors (through PABP, now PA-DSS) and who generally takes [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/08/19/mastercard-vs-visa-dueling-compliance-philosophies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard Becomes The First Card Brand To Publish PCI Fines</title>
		<link>http://compliancesoftware.org/2009/08/06/mastercard-becomes-the-first-card-brand-to-publish-pci-fines/</link>
		<comments>http://compliancesoftware.org/2009/08/06/mastercard-becomes-the-first-card-brand-to-publish-pci-fines/#comments</comments>
		<pubDate>Thu, 06 Aug 2009 13:39:04 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=603</guid>
		<description><![CDATA[The noncompliance assessment structure now contains escalating assessments per violation within a calendar year,” said the document sent to members earlier this summer. “Maximum assessments for initial noncompliance for Level 2 and Level 3 merchants have increased to $25,000 and $10,000, respectively. Furthermore, the $500,000 annual aggregate maximum for acquirer noncompliance assessments related to program [...]]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/08/06/mastercard-becomes-the-first-card-brand-to-publish-pci-fines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard seeks to clarify remote POS security upgrades policy #PCI</title>
		<link>http://compliancesoftware.org/2009/07/10/mastercard-seeks-to-clarify-remote-pos-security-upgrades-policy-pci/</link>
		<comments>http://compliancesoftware.org/2009/07/10/mastercard-seeks-to-clarify-remote-pos-security-upgrades-policy-pci/#comments</comments>
		<pubDate>Sat, 11 Jul 2009 03:13:36 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=556</guid>
		<description><![CDATA[MasterCard today clarified a June 15 bulletin about the use of remote key injection (RKI) services for upgrading encryption protocols on merchants&#8217; point of sale (POS) terminals, saying it was not an edict. via MasterCard seeks to clarify remote POS security upgrades policy.]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/07/10/mastercard-seeks-to-clarify-remote-pos-security-upgrades-policy-pci/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MasterCard halts remote POS security upgrades #PCI</title>
		<link>http://compliancesoftware.org/2009/07/09/mastercard-halts-remote-pos-security-upgrades-pci/</link>
		<comments>http://compliancesoftware.org/2009/07/09/mastercard-halts-remote-pos-security-upgrades-pci/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 12:02:10 +0000</pubDate>
		<dc:creator>compliancesoftware</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[mastercard]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://compliancesoftware.org/?p=550</guid>
		<description><![CDATA[In a purported second major security change in recent weeks, MasterCard has decided to disallow merchants&#8217; use of remote key injection (RKI) services to install new encryption keys on point-of-sale (POS) systems, says a Gartner analyst. via MasterCard halts remote POS security upgrades.]]></description>
		<wfw:commentRss>http://compliancesoftware.org/2009/07/09/mastercard-halts-remote-pos-security-upgrades-pci/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
