OATH: One Token To Rule Them All

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Channel: Other, Networking & Mgmt, Servers & Storage, Data Protection, Wireless, UC & VoIP

We've long known that multifactor authentication provides stronger security over simple passwords, but a limited number of options, cost, interoperability issues, and the dread that IT pros feel at the idea of issuing users multiple tokens have put a damper on deployment. With its recently released Reference Architecture 2.0, the Initiative for Open Authentication, or OATH, hopes to allay these misgivings with an open standard to bring strong authentication to applications and services.

The operative word here is "standard." Systems based on OATH's architecture allow for interoperability among user tokens and a variety of services requiring authentication. The ultimate goal: a single token compatible with any number of services from different providers. This is a fantastic idea, but it's currently possible only in a limited way. Because the current token implementation is event-triggered, if a token is used with unconnected services, the event count for those services will not match the state of the token, causing authentication to fail. The only way to make the system work is for all services to use the same validation back end, thereby keeping token state consistent. One such service is VeriSign's Verified Identity Protection, or VIP. Charles Schwab and eBay are two high-profile users; customers need only a single token to authenticate to these and other VIP-managed online services.

THE LOWDOWN

THE PROMISE
A standard for interoperable, strong authentication focusing initially on one-time passwords, with the goal to make secure authentication less expensive and ultimately pervasive.
THE PLAYERS
Most industry notables--AOL, Entrust, IBM, and VeriSign--and many lesser-known authentication specialists. Conspicuously absent is market leader EMC/RSA, which favors its proprietary SecurID.
THE PROSPECTS
Online service providers, especially financial services firms, are eager to beef up security in light of federal guidelines that encourage use of two-factor authentication. A standards-based approach that lowers costs and speeds implementation is attractive, and OATH seems to fit the bill. But the big question is whether tokens can really solve the problem of online fraud.

For every open standard there are proprietary alternatives, and strong authentication is no exception. While RSA has been the closed-system market leader for quite a while, the multifactor authentication space is getting crowded. Entries include WiKID, which uses a mobile phone-based software token, and PhoneFactor, which sends an authentication code to users' phones. Still, this is one area where the open alternative has a real shot. OATH's membership list is large and varied. Besides VeriSign, the latest spec is integrated into products from AOL, BMC, Citrix, Entrust, Hewlett-Packard, IBM/Tivoli, Imprivata, SanDisk, and many more.

A BETTER WAY


Page:  1 | 2 |3 |Next Page »

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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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/SPAM. Network Computing 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.
 

Research and Reports

Storage Virtualization Guide
May 2012

Network Computing: May 2012

TechWeb Careers