<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Payment Systems Blog &#187; Fraud</title>
	<atom:link href="http://www.paymentsystemsblog.com/topics/fraud/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paymentsystemsblog.com</link>
	<description>David D. Bergert</description>
	<lastBuildDate>Wed, 02 Nov 2011 11:24:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<copyright>2007-2008 </copyright>
	<managingEditor>podcast@paymentsystemsblog.com (Dave Bergert)</managingEditor>
	<webMaster>podcast@paymentsystemsblog.com (Dave Bergert)</webMaster>
	<ttl>1440</ttl>
	<image>
		<url>http://www.paymentsystemsblog.com/images/pspodcast.png</url>
		<title>Payment Systems Blog</title>
		<link>http://www.paymentsystemsblog.com</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>Payment Systems Podcast is a podcast that address the subject of Payments Systems, their operations, development, security and other experiences related to payment processing.</itunes:summary>
	<itunes:keywords>Payment Systems, ISO8583, PABP, PA-DSS, PCI, Security, Credit, Debit</itunes:keywords>
	<itunes:category text="Technology" />
	<itunes:category text="Business" />
	<itunes:category text="Technology">
		<itunes:category text="Software How-To" />
	</itunes:category>
	<itunes:author>Dave Bergert</itunes:author>
	<itunes:owner>
		<itunes:name>Dave Bergert</itunes:name>
		<itunes:email>podcast@paymentsystemsblog.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://www.paymentsystemsblog.com/images/pspodcast.png" />
		<item>
		<title>Detecting swapped PIN Pads at the Payment Switch</title>
		<link>http://www.paymentsystemsblog.com/2009/02/13/detecting-swapped-pin-pads-at-the-payment-switch/</link>
		<comments>http://www.paymentsystemsblog.com/2009/02/13/detecting-swapped-pin-pads-at-the-payment-switch/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 19:42:33 +0000</pubDate>
		<dc:creator>db</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PIN]]></category>
		<category><![CDATA[Point of Sale]]></category>

		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/02/13/detecting-swapped-pin-pads-at-the-payment-switch/</guid>
		<description><![CDATA[&#160; My colleague Andy Orrock writes an excellent post, &#34;Methodology for watching PIN Pad Switches&#34; which discusses a detective control that we put in place in OLS.Switch to detect when a PIN Pad has been changed at the point of sale, along with real time alerting of the event. &#160; Digital Transaction has an article [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.paymentsystemsblog.com/wp-content/uploads/2009/02/images.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; margin: 0px 20px 10px 0px; border-right-width: 0px" height="128" alt="images" src="http://www.paymentsystemsblog.com/wp-content/uploads/2009/02/images-thumb.jpg" width="119" align="left" border="0" /></a>
<p>&#160;</p>
<p>My colleague <a href="http://www.andyorrock.com">Andy Orrock</a> writes an excellent post, <a href="http://www.andyorrock.com/2009/02/methodology-for-watching-pin-pad-switches.html">&quot;Methodology for watching PIN Pad Switches&quot;</a> which discusses a <a href="http://www.audit-is.com/terminology/Detective%20control-termDefinition.htm">detective control</a> that we put in place in OLS.Switch to detect when a PIN Pad has been changed at the point of sale, along with real time alerting of the event. </p>
<p>&#160;</p>
<p>Digital Transaction has an article <a href="http://www.digitaltransactions.net/newsstory.cfm?newsid=1010">here</a>, that discuses this type of attack, another summary is <a href="http://www.abcmoney.co.uk/news/302007174857.htm">here</a> and quoted below:</p>
<blockquote><p>Investigators say the men would enter supermarkets late at night, distract the cashier and swap a PIN pad with an alternate machine that recorded each customer&#8217;s financial data. They could swap the equipment in as little as 12 seconds, prosecutors said.</p>
<p>After a while, the men would return, retrieve the machines and harvest the credit and debit card information. At least six supermarkets in Rhode Island and Massachusetts were targeted, and 238 people lost money.</p>
</blockquote>
<p> Another consideration to make, is the physical security of payment terminals and pin pads, such as bolting them down or using locking stands and regular inspections.&#160; See Verifones <a title="http://www.posdata.com/security_pinpad_best_practices.html" href="http://www.secureretailpayments.com/resources/PIN%C2%AD_Pad_Security_Best_Practices_V2.pdf">PIN Pad Security Best Practices</a> for more.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.paymentsystemsblog.com/2009/02/13/detecting-swapped-pin-pads-at-the-payment-switch/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Common Point of Purchase (CPP)</title>
		<link>http://www.paymentsystemsblog.com/2009/02/05/common-point-of-purchase-cpp/</link>
		<comments>http://www.paymentsystemsblog.com/2009/02/05/common-point-of-purchase-cpp/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 13:54:00 +0000</pubDate>
		<dc:creator>db</dc:creator>
				<category><![CDATA[Breach]]></category>
		<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Visa]]></category>

		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/02/05/common-point-of-purchase-cpp/</guid>
		<description><![CDATA[The Merchant Account Blog has a great post and great diagrams on what is called Common Point of Purchase or Point of Compromise (POC), this is one method of how a merchant or processor can be identified as the breach point in a payment card fraud / compromise scenario: (from Merchant Account Blog ) Visa [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud">Merchant Account Blog</a> has a great post and great diagrams on what is called Common Point of Purchase or Point of Compromise (POC), this is one method of how a merchant or processor can be identified as the breach point in a payment card fraud / compromise scenario:</p>
<table cellspacing="0" cellpadding="2" width="400" border="0">
<tbody>
<tr>
<td valign="top" width="400"><a href="http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud"><img alt="Fraud Detection" src="http://www.merchantaccountblog.com/images/fraud-detection.gif" /></a></td>
</tr>
</tbody>
</table>
<p><strong><em>(from </em></strong><a href="http://www.merchantaccountblog.com/667/spotting-large-scale-credit-card-fraud"><strong><em>Merchant Account Blog</em></strong></a><strong><em> )</em></strong></p>
<p>Visa also has a presentation on this <a href="http://usa.visa.com/download/merchants/cpp_fraud_overview.pdf">here</a>:</p>
]]></content:encoded>
			<wfw:commentRss>http://www.paymentsystemsblog.com/2009/02/05/common-point-of-purchase-cpp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

