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

1/29/2012
10:40 AM
Taher Elgamal
Taher Elgamal
Commentary
50%
50%

The Value Of Device Authentication

'Fingerprinting' evolving to protect device IDs

Since the beginning of e-commerce in the mid-1990s, businesses noticed that transactions conducted online can be strengthened in assurance if we can “remember” that a particular device is the same that was used before to conduct successful transactions. A known device provides knowledge about the history of the device and can mitigate against fraudulent transactions that use stolen cards.

Later on, similar techniques now referred to as device fingerprinting are quite popular in detecting devices that have been used to conduct fraud online. Several businesses have started up that provide knowledge about connected devices.

Fraudsters have since responded with techniques to continuously change the device ID in order to deceive these systems. Furthermore, the use of botnets has increased in the fraud rings since these devices are likely to only appear one time and are impossible to detect in this regard.

Having said all that, it is useful to remember devices that users have used to conduct online transactions, and to tie these to the fraud history of the devices. Many different techniques are used today to fingerprint devices, mostly using browser environment fingerprinting, but some actually use techniques that detect certain characteristics about the machine hardware itself.

Several industry efforts are working on improved and perhaps cryptographically strong versions of a device ID. These techniques will become available soon and will help prevent fraudsters from making their machines “look different” every time they use them. I will discuss this a bit more in my next blog.

Dr. Taher Elgamal is the inventor of the Elgamal Digital Signature scheme, which is the basis for Digital Signature Algorithm (DSA). While serving as chief scientist of Netscape Communications, he was the driving force behind SSL. He is the founder of IdentityMind.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
JJ1819
50%
50%
JJ1819,
User Rank: Apprentice
1/31/2012 | 5:31:47 AM
re: The Value Of Device Authentication
A single solution for authentication is fingerprinting, it is the unique id which is highly impossible to misuse.
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.