Risk
5/12/2005
06:20 PM
Thomas Claburn
Thomas Claburn
Commentary
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Phones Fight Phonies

On Tuesday, VeriSign hosted a dinner for journalists at Le Colonial in San Francisco to help get its message out about strong authentication. Representatives from AOL, IBM, and Intuit also were in attendance. The idea is that journalists get good food and the hosts get good press. Of course, it's not officially quid pro quo, but it's hard to imagine companies sponsoring such events without some hope that what goes around comes around. Coincidentally, Bite public relations managed the affair.

On Tuesday, VeriSign hosted a dinner for journalists at Le Colonial in San Francisco to help get its message out about strong authentication. Representatives from AOL, IBM, and Intuit also were in attendance.

The idea is that journalists get good food and the hosts get good press. Of course, it's not officially quid pro quo, but it's hard to imagine companies sponsoring such events without some hope that what goes around comes around. Coincidentally, Bite public relations managed the affair.Anyway, VeriSign had come to town for a conference called Digital ID World 2005, where the company explained its plans to make two-factor (strong) authentication cheap and affordable.

Strong authentication involves using something one has-an ATM card, example-in conjunction with something one knows-a personal identification number or PIN. It generally provides better security than weak authentication, which utilizes just one of those two components, such as a password or a door key.

It's a potentially useful technology that could help reduce identity theft and fraud.

The challenge for VeriSign and other security companies is that authentication tokens are expensive and there's no established open standard. In the absence of such a standard, it's doubtful that consumers would be thrilled to carry different tokens for every commercial Web site they deal with.

The answer, it seems, is the cell phone. They're everywhere already. Using them as authentication tokens just makes sense, to me at least.

VASCO Data Security, an enterprise security company, is doing just that. The company said today that it's now offering its Digipass software security token for Java-enabled mobile phones.

Sounds promising.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.