Endpoint

11/8/2016
10:00 AM
Mickey Boodaei
Mickey Boodaei
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Is Fingerprint Authentication Making The Password Problem Worse?

Problems emerge when users switch to a new phone.

Fingerprint scanning is an easy and fast way to unlock mobile phones and authenticate identity to supported applications. Many banks have already added support for this capability and are allowing their customers to log in to mobile banking apps by scanning a finger instead of entering a password.

The initial impact was immediate. Millions of users enrolled in fingerprint authentication and started logging in without using passwords. The user experience improved, and security seemed to be better, because, unlike passwords, fingerprint data is locked on the device and can't be easily stolen or phished.

Over time, however, security and usability issues started to emerge. The first problem occurs when users switch to a new phone. When users download a bank's app to their new phone, they are required to enter their password again during the first login. There is a technical explanation for this requirement, which I'll describe shortly.

First, let's consider the usability and security impact of re-entering a password on the new device. Many users who have become accustomed to logging in with their fingers are less likely to remember their password. Therefore, when the app forces them to enter a password, many will have to initiate a "forgot my password" process. This often involves contacting the bank's call center, which affects the user experience. There is also a security implication attached to this process. Even if they're not being used to log in, passwords still exist in the background. Therefore, they can still be stolen or phished by fraudsters to take over an account, even if the user is using fingerprint authentication.

Dark Reading's all-day virtual event Nov. 15 offers an in-depth look at myths surrounding data defense and how to put business on a more effective security path. 

Now for the technical explanation. Fingerprint information is managed by the mobile device's operating system. It's stored on the device and never leaves it. When a user enrolls in fingerprint authentication for a specific app, such as the banking app in our example, the app links the user's identity with the fingerprint information stored on the device. Therefore, when a user replaces his or her device and downloads the app to the new one, the app has no way of verifying the owner's fingerprint because that data was stored on the old device. To validate the user's identity and link a fingerprint to the new device, the app falls back to password authentication.

This problem isn't limited to new devices. There are other scenarios in which the link between a user's fingerprint and the mobile app can break (for example, if the user adds fingerprints to the device or removes them). As a security measure, the operating system breaks the link in this scenario and the user is forced to re-enter a password. This is a security function that many sensitive applications, such as banking applications, have implemented. Other scenarios include when a user resets the device to its factory settings or reinstalls the app.

Fingerprint authentication is a good first step for avoiding passwords, but it doesn't eliminate them. This partial measure, as described above, can create a bigger password problem. In order to truly get rid of passwords, we need to address and remove the scenarios (and others like them) described earlier. This involves implementing processes and technologies to bridge these gaps. Some alternatives include the use of challenge questions, one-time-passwords, voice biometrics, touch biometrics, and other technologies that need to be constantly orchestrated to create a password-free experience.

Related Content:

 

Mickey Boodaei is a serial cybersecurity entrepreneur. Currently, he is CEO of Transmit Security, which helps organizations add omni-channel authentication capabilities to their applications. He previously founded Trusteer, an online fraud prevention company which was ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Windows 10 Security Questions Prove Easy for Attackers to Exploit
Kelly Sheridan, Staff Editor, Dark Reading,  12/5/2018
Starwood Breach Reaction Focuses on 4-Year Dwell
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/5/2018
Symantec Intros USB Scanning Tool for ICS Operators
Jai Vijayan, Freelance writer,  12/5/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I guess this answers the question: who's watching the watchers?
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-3988
PUBLISHED: 2018-12-10
Signal Messenger for Android 4.24.8 may expose private information when using "disappearing messages." If a user uses the photo feature available in the "attach file" menu, then Signal will leave the picture in its own cache directory, which is available to any application on the...
CVE-2018-10008
PUBLISHED: 2018-12-10
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java that allows attackers to invoke some methods on Java objects by accessing crafted URLs that were not intended...
CVE-2018-10008
PUBLISHED: 2018-12-10
An information exposure vulnerability exists in Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in DirectoryBrowserSupport.java that allows attackers with the ability to control build output to browse the file system on agents running builds beyond the duration of the build using the workspace br...
CVE-2018-10008
PUBLISHED: 2018-12-10
A data modification vulnerability exists in Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in User.java, IdStrategy.java that allows attackers to submit crafted user names that can cause an improper migration of user record storage formats, potentially preventing the victim from logging into Jen...
CVE-2018-10008
PUBLISHED: 2018-12-10
A denial of service vulnerability exists in Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in CronTab.java that allows attackers with Overall/Read permission to have a request handling thread enter an infinite loop.