Dark Reading 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.

Perimeter

3/3/2011
02:29 PM
Taher Elgamal
Taher Elgamal
Commentary
50%
50%

A New Spin On Fraud Prevention

Most online fraud stems from electronic transactions not associating the identity of the user with the card or account

There has been plenty of opinion over the years regarding the relationship among fraud, SSL, and online e-commerce transactions. Certainly, a lot more fraud exists in online e-commerce transactions versus real-world transactions, and researchers continue to investigate and identify behaviors and processes that make accounts vulnerable.

In my mind, however, the main culprit -- the most obvious one -- is the fact that most transactions are not associating the identity of the user with the card or account being presented.

In reality, when you present a card to make a purchase in the physical world, the vendor taking the card is supposed to validate your identity and ensure you are the real owner of that particular account.

But online, we've basically skipped over that user/client authentication part. We no longer have a way to authenticate the card holder as the real owner of the card, and much of the online fraud is a result of that simple fact.

This issue was something SSL tried to address early on, but SSL's approach to the issue didn't get implemented the way it was intended.

Later on, the credit card associations started an effort called 3D Secure in an attempt to occasionally authenticate the user while they performed a transaction. (If you've ever been asked to type a password after you present a card during a transaction, you've experienced this yourself.) Successfully providing the password assures that, at one point, you actually registered the card. There are at least a few good companies that still support this concept today.

Unfortunately, the implementation of this concept (i.e., interrupting the user's purchase by forwarding them to a separate site and asking them to provide a password that they've very likely forgotten) has resulted in a lot of lost revenue.

My feeling is that it's going to be difficult, now that we're 15 or 16 years into the history of e-commerce, to actually rebuild the original authentication ideas.

Perhaps the correct implementation is to try to infer the identity of the card presenter through the environment where this transaction is coming from, to make sure that this is the correct card holder, and to not bother the user at the same time. If you can validate that the environment of the user presenting the card looks like the environment inhabited by the card before, it's reasonable to assume that this is very likely the same user. We can complement that with a protocol for registering the cards for e-commerce, similar to how we register a new credit card on the phone today when we get one in the mail.

Because the incidence of fraud is so high and we're losing revenue due to people escaping from this secondary authentication step, I expect the industry to actually take a new angle on this. We are probably not going to go back and try to build the original SSL dream of authenticating everybody in the world and having everybody known to any merchant that they try to go to, but I expect that we will, somehow, create an equally effective authentication scheme in the future.

Recognized in the industry as the "inventor of SSL," Dr. Taher Elgamal led the SSL efforts at Netscape. He also wrote the SSL patent and promoted SSL as the Internet security standard within standard committees and the industry. Dr. Elgamal invented several industry and government standards in data security and digital signatures area, including the DSS government standard for digital signatures. In addition to serving on numerous corporate advisory boards, Dr. Elgamal is the Chief Security Officer at Axway, a global provider of multi-enterprise solutions and infrastructure. He holds a Ph.D. and M.S. in Computer Science from Stanford University. View more of his blog posts here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31769
PUBLISHED: 2021-06-21
MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require autho...
CVE-2020-20469
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the log_edit.php files failing to filter the csa_to_user parameter, remote attackers can exploit the vulnerability to obtain database sensitive information.
CVE-2020-20470
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has web site physical path leakage vulnerability.
CVE-2020-20471
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has an unauthorized access vulnerability in default_user_edit.php, remote attackers can exploit this vulnerability to escalate to admin privileges.
CVE-2020-20472
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a sensitive information disclosure vulnerability. The if_get_addbook.php file does not have an authentication operation. Remote attackers can obtain username information for all users of the current site.