<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/css" href="http://commons.oreilly.com/wiki/skins/common/feed.css?97"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>Beautiful Trade/Analyzing the Security Context - Revision history</title>
		<link>http://commons.oreilly.com/wiki/index.php?title=Beautiful_Trade/Analyzing_the_Security_Context&amp;action=history</link>
		<description>Revision history for this page on the wiki</description>
		<language>en</language>
		<generator>MediaWiki 1.11.0</generator>
		<lastBuildDate>Fri, 24 May 2013 12:19:26 GMT</lastBuildDate>
		<item>
			<title>Ebellis: New page: '''Analyzing the Security Context'''   The fundamental problem is that cardholder data becomes a shared secret. As we’ve seen, this  secret often needs to be shared amongst a lot of part...</title>
			<link>http://commons.oreilly.com/wiki/index.php?title=Beautiful_Trade/Analyzing_the_Security_Context&amp;diff=24533&amp;oldid=prev</link>
			<description>&lt;p&gt;New page: '''Analyzing the Security Context'''   The fundamental problem is that cardholder data becomes a shared secret. As we’ve seen, this  secret often needs to be shared amongst a lot of part...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;'''Analyzing the Security Context''' &lt;br /&gt;
&lt;br /&gt;
The fundamental problem is that cardholder data becomes a shared secret. As we’ve seen, this &lt;br /&gt;
secret often needs to be shared amongst a lot of parties in order to fulfill even a single &lt;br /&gt;
transaction. Because security relies on the least common denominator of security controls &lt;br /&gt;
amongst these parties, a leak is almost inevitable during the life of an account. &lt;br /&gt;
Visa, Inc. stated, in its earnings report for the third quarter of 2008, that the total transactions &lt;br /&gt;
on Visa’s brands—Visa, Interlink, Plus, and Electron—grew 11% from $8.65 billion a year to &lt;br /&gt;
$9.59 billion. This gives us some perspective when analyzing breach data. Visa is the largest of &lt;br /&gt;
the card brands, but it is only one of many. And each transaction probably passed through &lt;br /&gt;
multiple merchant systems, payment gateways, service providers, fulfillment systems, bank &lt;br /&gt;
networks, and card networks. That’s an awful lot of shared secrets! &lt;br /&gt;
&lt;br /&gt;
To compound the issues and complexities of these shared secrets, a merchant or service &lt;br /&gt;
provider has several reasons to store information such as account numbers after finishing the &lt;br /&gt;
initial transaction: &lt;br /&gt;
&lt;br /&gt;
'''Recurring charges''' &lt;br /&gt;
&lt;br /&gt;
Many merchants offer services that require regular payments on a weekly, monthly, &lt;br /&gt;
quarterly, or annual basis. In order to continue to charge the same account on a regular &lt;br /&gt;
basis, the merchant needs to store sensitive payment information as long as the consumer &lt;br /&gt;
remains a customer. &lt;br /&gt;
&lt;br /&gt;
'''Chargebacks''' &lt;br /&gt;
&lt;br /&gt;
To issue a refund, the merchant must store the account number that its service or &lt;br /&gt;
merchandise was charged to. As a measure of fraud prevention, many acquiring banks &lt;br /&gt;
require the merchants and service providers to refund the exact card account that was &lt;br /&gt;
originally charged. &lt;br /&gt;
&lt;br /&gt;
'''Consumer convenience''' &lt;br /&gt;
&lt;br /&gt;
Consumers often elect to store their account information with a merchant where they &lt;br /&gt;
make frequent purchases. This aligns with our discussion later around consumer &lt;br /&gt;
incentives. For many people, convenience outweighs the risks.&lt;/div&gt;</description>
			<pubDate>Tue, 30 Jun 2009 02:14:33 GMT</pubDate>			<dc:creator>Ebellis</dc:creator>			<comments>http://commons.oreilly.com/wiki/index.php/Talk:Beautiful_Trade/Analyzing_the_Security_Context</comments>		</item>
	</channel>
</rss>