Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Security

Ensuring Strong Security for Mobile Transactions


Not too far into the future, it will seem quaint and probably slightly bizarre that there was ever a time when phones could not take and send pictures, download text messages, browse the Internet, play music, and be toted around conveniently in a purse or pocket. Given the most recent trends in phone functionality, children born today may also find it strange that people ever carried bank cards, or credit cards, or wallets. This is because mobile handsets are being looked to increasingly act as transactional mechanisms: devices that can be used effortlessly as forms of personal identification or as tools for buying goods and services. Yet before we quite reach that point of complete convergence, there is the tricky business of security to contend with.

It's tricky for two reasons. One, because the requirement for security—and the stringency of that security—is going to intensify as devices are used to store and exchange ever-more sensitive information. And two, because the whole promise of wireless transactions is convenience. Even as expectations of functionality and security reach new heights, users will expect their devices to operate faster and more effortlessly than ever before.

These two seemingly contrary sets of demands pose a major challenge to device manufacturers whose products are already constrained in terms of bandwidth, power and processing capability. Yet with security-minded designs based on efficient, well-established methods and using compact algorithms like ECC (elliptic curve cryptography), the challenge can be met.

At the point of purchase
Pilot tests in Japan and Europe have shown that the transactional possibilities of mobile devices are virtually unrestricted. Contactless payment, public transportation ticketing and event ticketing have been singled out as key areas for what are sometimes referred to as "mobile proximity transactions". The recent LocPay project led jointly by Visa, Nokia and financial-services company Nordea provides a straightforward example. Over several months in 2003 and 2004, the companies and a number of Finnish retail partners experimented with a contactless point-of-sale payment system. Merchants ranging from restaurants and sporting-goods vendors to travel agencies, video stores and hair salons were outfitted with point-of-sale RFID readers. These were configured to interact with RFID transceiver-equipped Nokia phones given out to 150 Nordea Visa Electron cardholders. Rather than swipe their magnetic-stripe Visa cards, users passed their phones over the reader to trigger payment processing. The Mobile electronic Transactions Forum, aka MeT, has identified a number of requirements for the successful implementation of mobile-transaction systems, from usability and low power consumption to clear definition of the payment architecture. But topping the list, not surprisingly, are security and privacy.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.