<?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: Will mobile payments usher in a new era of crime?</title>
	<atom:link href="http://blogs.parc.com/blog/2009/10/will-mobile-payments-usher-in-a-new-era-of-crime/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.parc.com/blog/2009/10/will-mobile-payments-usher-in-a-new-era-of-crime/</link>
	<description>perspectives, trends, discussions</description>
	<lastBuildDate>Sun, 20 Nov 2011 06:03:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Markus Jakobsson</title>
		<link>http://blogs.parc.com/blog/2009/10/will-mobile-payments-usher-in-a-new-era-of-crime/comment-page-1/#comment-967</link>
		<dc:creator>Markus Jakobsson</dc:creator>
		<pubDate>Thu, 15 Oct 2009 22:52:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.parc.com/?p=1633#comment-967</guid>
		<description>Andy, that is an excellent point: A common risk reducer is certainly to block shipping to new locations. This is not always practical (e.g., sites where a large portion of merchandise are gifts) and does not apply to any electronic or virtual goods. However, these pose other constrains in terms of criminal monetization. 

My main point is, though, that with heuristic protection (which is what we rely on), any new vulnerability is the reason for concern. And with the likely future development in m-commerce, there is reason for concern. It has been estimated that there will be more smartphones than PCs in 2-3 years, and that Symbian will have close to 40% of the market. Will malware authors move from Windows to Symbian? Many people fear that they will.</description>
		<content:encoded><![CDATA[<p>Andy, that is an excellent point: A common risk reducer is certainly to block shipping to new locations. This is not always practical (e.g., sites where a large portion of merchandise are gifts) and does not apply to any electronic or virtual goods. However, these pose other constrains in terms of criminal monetization. </p>
<p>My main point is, though, that with heuristic protection (which is what we rely on), any new vulnerability is the reason for concern. And with the likely future development in m-commerce, there is reason for concern. It has been estimated that there will be more smartphones than PCs in 2-3 years, and that Symbian will have close to 40% of the market. Will malware authors move from Windows to Symbian? Many people fear that they will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Steingruebl</title>
		<link>http://blogs.parc.com/blog/2009/10/will-mobile-payments-usher-in-a-new-era-of-crime/comment-page-1/#comment-965</link>
		<dc:creator>Andy Steingruebl</dc:creator>
		<pubDate>Thu, 15 Oct 2009 15:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.parc.com/?p=1633#comment-965</guid>
		<description>Worth noting, Markus, is that with many of these payment/checkout methods extra authentication is required if you want to do things like change the shipping address. This reduces the risk as the attacker can make a bunch of purchases, but they can&#039;t monetize them because the goods are shipped to the account holder, not the criminal. 

Now, saved passwords etc. make this risk bigger of course, and there are of course ways to address that.</description>
		<content:encoded><![CDATA[<p>Worth noting, Markus, is that with many of these payment/checkout methods extra authentication is required if you want to do things like change the shipping address. This reduces the risk as the attacker can make a bunch of purchases, but they can&#8217;t monetize them because the goods are shipped to the account holder, not the criminal. </p>
<p>Now, saved passwords etc. make this risk bigger of course, and there are of course ways to address that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

