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.

Endpoint

12/7/2016
10:30 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Biometric Technology Is Not A Cure-All For Password Woes

No single authentication token is infallible. The only real solution is multifactor authentication.

Authentication is the cornerstone of information security. At the highest level, security is focused on providing access controls and protection to people or things you trust. If you can't reliably verify the identity of trusted users, access controls break down.

Our trust in authentication systems has eroded of late, largely because of the seemingly endless torrent of massive credential leaks from well-known Web service providers. For example, in mid-November we learned attackers accessed around 330 million AdultFriendFinder accounts, including plaintext and hashed passwords. Researchers have already cracked 99.3% of those passwords. This deluge of credential leaks has caused the security industry to re-examine our authentication systems, and especially our reliance on passwords.

At present, biometric tokens are the industry's solution to this problem. Whether it's a traditional fingerprint or face scan, or a more innovative option such as your heartbeat or brainwaves, the industry has turned to biometrics to solve two major password problems: convenience and difficulties creating a "strong" authentication token.

Image Source: Shutterstock by Chakrapong Zyn
Image Source: Shutterstock by Chakrapong Zyn

A strong authentication token is one that uniquely correlates to you, but others can't know, claim, guess, or replicate. That's why security experts recommend using long, almost random passwords. Unfortunately, it's difficult to remember strong and unique passwords. A biometric such as a fingerprint, on the other hand, is unique by definition.

The second issue is convenience. If you follow all the best practices, passwords are very strong. For example, if you use unique, 24-character, random passwords for every device and website you log on to, it would be very difficult for attackers to steal your credentials. As long as the organization storing your password hashed it, the length of your password would make it too time-consuming to crack. The problem is that no human will realistically do this without some sort of tool to help. Following security best practices results in passwords that are very difficult to memorize. Therefore, the idea that you could just pick up a device and look at it or touch it to log on with biometrics is very appealing to users.

So far, biometric technology sounds great! What's the problem?

First, I should note that biometrics will play an integral role in future authentication. However, we must realize the technology isn't a panacea. If implemented improperly, or without regard to some of the password problems that got us here in the first place, biometrics could just be the fresh coat of paint that hides the rot inside our walls.

Many of the issues with biometrics have been widely discussed, so I won't rehash them in detail. For instance, many researchers have proven it's not overly difficult to replicate certain biometrics. For instance, researchers have fooled fingerprint readers with Play-Doh and got past facial scanners with a special pair of glasses. Furthermore, early biometric solutions stored their "digital" biometric data on a server, rather than limiting it to the client. This could make those servers susceptible to the same types of data breaches that have leaked passwords. In fact, fingerprints of millions of government employees were stolen in a June 2015 data breach at the US Office of Personnel Management. Like passwords before them, biometrics aren't infallible.

The bigger issue here is that biometrics haven't replaced passwords; they've just hidden them. New operating systems such as Windows 10 with Hello and mobile devices with Touch ID are incorporating biometrics, but they still require you to set a password. This could be because biometrics aren't perfect yet and we need backup authentication options, or it could be that it takes time to phase out legacy technology before we can rely on biometrics alone. In either case, the password is still there, and it exposes the same risks it always did. Relying on biometric authentication could also lull users into following poor password practices, making them less secure overall.

What's the Solution?
I don't think passwords are the problem. Instead, I believe no authentication token is infallible. The only real solution to this problem is multifactor authentication (MFA). Right now, we use biometrics as a single token replacement for passwords. We need to use biometrics as one of at least two tokens.

Also, we can't forget the convenience problem. Users will bypass our security practices if they are too impractical, so we should remember that certain types of multifactor solutions could feel inconvenient. However, if we pair a biometric with, say, a proximity-based authentication token from a phone, then users get the benefit of MFA without the hassle.

In the end, biometric security methods are great, but not by themselves. If we simply replace one single-factor solution with another, we're dooming ourselves to relive past problems. If our devices retain backup authentication options, such as passwords, we still expose those legacy risks. The only solution in my opinion is to never accept any authentication token by itself. 

Related Content:

Corey Nachreiner regularly contributes to security publications and speaks internationally at leading industry trade shows like RSA. He has written thousands of security alerts and educational articles and is the primary contributor to the WatchGuard Security Center blog, ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/7/2020
The Coronavirus & Cybersecurity: 3 Areas of Exploitation
Robert R. Ackerman Jr., Founder & Managing Director, Allegis Capital,  4/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20637
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connecti...
CVE-2020-11650
PUBLISHED: 2020-04-08
An issue was discovered in iXsystems FreeNAS 11.2 and 11.3 before 11.3-U1. It allows a denial of service.
CVE-2020-11653
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.6 LTS, 6.1.x and 6.2.x before 6.2.3, and 6.3.x before 6.3.2. It occurs when communication with a TLS termination proxy uses PROXY version 2. There can be an assertion failure and daemon restart, which causes a performance loss.
CVE-2020-2732
PUBLISHED: 2020-04-08
A flaw was discovered in the way that the KVM hypervisor handled instruction emulation for an L2 guest when nested virtualisation is enabled. Under some circumstances, an L2 guest may trick the L0 guest into accessing sensitive L1 resources that should be inaccessible to the L2 guest.
CVE-2020-1627
PUBLISHED: 2020-04-08
A vulnerability in Juniper Networks Junos OS on vMX and MX150 devices may allow an attacker to cause a Denial of Service (DoS) by sending specific packets requiring special processing in microcode that the flow cache can't handle, causing the riot forwarding daemon to crash. By continuously sending ...