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

4/22/2013
11:42 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Scan My Eyeball, Already

Could consumers be the catalyst for the password's ultimate demise?

Let's face it: Even with all of the publicity surrounding password breaches, email and Facebook hacks, and more and more everyday people experiencing compromised accounts -- you most likely have relatives and friends who've now been there -- most consumers still don't create complex passwords.

You can't blame them. They want to use something they can actually use (as in remember), and they want convenience when they log into a website, social network, or email account. They're hearing that they should have a strong password with a mix of upper- and lowercase characters, numbers, and symbols, but the reality is, they don't want to worry about forgetting it when they need it. Which, of course, is exactly what's happening.

According to a new Ponemon Institute study, around 70 percent of consumers in the U.S., U.K., and Germany have forgotten one of their passwords because it was too long or complex to remember, with 61 percent saying they were locked out of an online account due to some sort of authentication process failure. Sixty-three percent of U.S. consumers say that failure was due to a forgotten password, username, or response question.

Some 46 percent of U.S. consumers were unable to finish their online transactions due to an authentication failure with passwords, according to the survey.

The study, which was commissioned by Nok Nok Labs, shows that consumers (some 70 percent) are getting fed up with passwords and today's authentication processes. Meanwhile, the troubled password model remains the norm despite developments in stronger and more efficient authentication processes. Most organizations just can't seem to shake the password, even as the more aggressive ones, such as banks, add multiple factors of authentication.

Consumers are looking past passwords, though. And surprise, surprise: Biometrics, which not long ago left most consumers and corporate users uneasy and queasy about their fingerprints, irises, and faces being used to ID them, is now becoming more palatable. The majority of consumers from the Ponemon survey say they consider biometrics a viable option for authentication with banks, credit card companies, healthcare providers, email providers, government agencies, and other "trusted" organizations. As long as those organizations don't have direct access to biometric data, that is.

They favor voice recognition (83 to 91 percent), facial scans (65 to 72 percent), hand geometry (57 to 65 percent), and fingerprints (56 to 62 percent) the most, but eye scans are fine with half of the consumers in all three regions.

So maybe, just maybe, consumers could end up being the catalyst that finally kills off the password. If password problems increasingly interfere with their online transactions for products or services, then something's gotta give.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
blm-x
50%
50%
blm-x,
User Rank: Apprentice
4/25/2013 | 5:23:48 PM
re: Scan My Eyeball, Already
There are flaws and inconveniences with most biometrics. Fingerprint scanning is cumbersome and difficult. Retina scans are uncomfortable because of the time necessary to get a scan. Eye infections and other ocular conditions can cause false rejections. Facial scanning and thermal scanning also are dependent on changing physical conditions of the subject. Voice pattern matching will depend on health conditions as well. Palm vein scanning looks to be the most promising for consistent biometric identification since the veins under the skin do not alter significantly over time and age in late teens and adults. Until they can instantly pattern match DNA enough to remove false acceptance within reasonable statistical odds we are left with what is currently available. I think multi-factor authentication using a combination of the above methods will probably be a solution that is reasonable, secure, fast, and convenient.
WSCHEXNAIDER775
50%
50%
WSCHEXNAIDER775,
User Rank: Apprentice
4/25/2013 | 3:03:29 PM
re: Scan My Eyeball, Already
Sorry .... typo

"I need a distraction, and an eyeball" - Jeremy Renner as Clint "Hawkey" Barton in The Avengers movie.
WSCHEXNAIDER775
50%
50%
WSCHEXNAIDER775,
User Rank: Apprentice
4/25/2013 | 2:38:00 PM
re: Scan My Eyeball, Already
"I need is a distraction, and an eyeball" -- Jeremy Renner as Clint "Hawkeye" Barton in The Avengers movie.
macker490
50%
50%
macker490,
User Rank: Ninja
4/24/2013 | 11:33:32 AM
re: Scan My Eyeball, Already
the real "problem" with passwords,..... is that people share them to access pay for services. now these services want positive real identification to stop such sharing

this is a demand that must be rejected . -
macker490
50%
50%
macker490,
User Rank: Ninja
4/23/2013 | 12:05:33 PM
re: Scan My Eyeball, Already
the ultimate invasion of privacy.
it is important for EVERYONE to be anonymous on the net and I don't think this kind of scanning is compatible with that requirement.- The Internet is not a nice place everywhere which makes it critical for everyone to be anonymous .- There's nothing wrong with passwords -- properly implemented.

just as rainbow tables are used to attack password hash hackers will similarly attack any scan .- it is necessary to put a stop to SQL Injection -- so they can't get the password hash tables to work with in the first place.
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
TPM-Fail: What It Means & What to Do About It
Ari Singer, CTO at TrustPhi,  11/19/2019
Americans Fed Up with Lack of Data Privacy
Robert Lemos, Contributing Writer,  11/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10854
PUBLISHED: 2019-11-22
cloudforms version, cloudforms 5.8 and cloudforms 5.9, is vulnerable to a cross-site-scripting. A flaw was found in CloudForms's v2v infrastructure mapping delete feature. A stored cross-site scripting due to improper sanitization of user input in Name field.
CVE-2019-13157
PUBLISHED: 2019-11-22
nsGreen.dll in Naver Vaccine 2.1.4 allows remote attackers to overwrite arbitary files via directory traversal sequences in a filename within nsz archive.
CVE-2012-2079
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
CVE-2019-11325
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
CVE-2019-18887
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.