Welcome Guest. | Log In| Register | Membership Benefits
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

Visa Tests Credit Card With Random Number Generator

Built-in second factor of authentication could slow online card fraud

Nov 11, 2008 | 05:37 PM

By Tim Wilson
DarkReading

Visa is testing a new credit card that can generate a random-number passcode to help ensure it won't be used by unauthorized individuals.

In trials starting this week at four banks -- Bank of America UK, Corner Bank in Switzerland, Cal in Israel, and IW Bank in Italy -- Visa and EMUE Technologies are testing a Visa PIN card, an alternative to the "CCV" code currently printed on the back of most cards to help ensure that the individual is actually in possession of the card. The technology was first introduced in June.

An alphanumeric display and keypad is built directly into the card. When making a transaction online, customers type their PIN into the card, which creates a one-time security code. That code can be entered into a Website or given to a phone operator to help reduce "card-not-present" (CNP) fraud, the companies said. The card features a battery that lasts three years.

A number of banks have expressed interest in the card since its introduction this past summer, according to Visa. "The interest in this solution in the industry has been overwhelming," said Sandra Alzetta, head of innovation and new products at Visa Europe. "We look forward to working with the banks involved in the pilots to gain greater insights into how effective this solution can be in the longer term."

Visa has experimented with other CCV replacement schemes, including Verified by Visa, an ill-fated process that was found to be flawed -- hackers were sometimes able to reset the password by stealing the card's details and the user's birth date.

Security experts pointed out that the new card is still vulnerable to man-in-the-middle attacks, in which the attacker sets up a false site and fools the user into giving away a valid PIN. But officials at EMUE say that the cards could be loaded with digital signature technology, which would make attacks much more difficult.

The trials will go for six to 12 months, raising the possibility that the technology might be more widely available late next year.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message


Subscribe to RSS










Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:suse linux
Published:2010-01-22
Severity:High
Description:SUSE Linux Enterprise 10 SP3 (SLE10-SP3) configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:The URL validation functionality in Microsoft Internet Explorer 7 and 8 does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
Vulnerability:bind
Published:2010-01-22
Severity:Medium
Description:ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-2530 and CVE-2009-2531.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-3671, CVE-2009-3674, and CVE-2010-0246.


Briefing Centers
POWERFUL INFORMATION
AT YOUR FINGERTIPS
(SPONSORED LINKS)