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.

Operations //

Identity & Access Management

11/19/2014
11:25 AM
Dave Kearns
Dave Kearns
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

Killing Passwords: Don’t Get A-Twitter Over ‘Digits’

Twitter's new service that eliminates passwords for authentication actually makes your mobile device less secure.

At Twitter’s recently concluded first annual developer’s conference, the social networking company trumpeted what it claims is a major step on the path to killing off passwords for authentication. Called “Digits,” this is a system that mobile app developers can incorporate in their software to supposedly ease the pain of verification/authentication for newly installed apps on a user’s mobile device.

On installing a new app, a user would no longer need to establish a username/password combination nor provide an email address (which, I’m told, many younger users no longer have) in order to register the app. After downloading an app, the user simply has to enter his or her phone number, and the app will verify it by sending a text message to that number and reading it automatically. No muss, no fuss.

Of course, anyone using that mobile device would also have access to the app as if that were his phone number, unless access to the device is password/PIN protected. But, then, we haven’t exactly killed off passwords, have we? Very few apps require you to authenticate every time they’re launched -- a major security hole, in my estimation -- so the amount of time Digits saves over the life of the app (i.e., it’s used once at installation) is, essentially, none.

This should not be confused with Twitter’s (or others’) two-factor authentication (2FA) systems that use SMS messages. In those systems you need a username (or email address), a password, and a one-time-use PIN code that’s been sent to your registered phone number in order to successfully log in. That phone number is not given to the system at run-time (as it is with the Digits system) but must be entered into your user account at some point when you are already authenticated to it. Someone stealing your phone needs to know your username and password in order to even see the SMS message -- not so with Digits.

Security boffins are divided on the new service, with some arguing that it neither moves security forward nor backward. Others, though, feel it tips the usability/security scale too far towards the usability side. While passwords are considered a weak system, they do, at least, rely on a user’s personal knowledge of the choice of password/phrase. The Digits system provides no certainty that the person using the app is actually the person she claims to be.

More worrying, though, is the rise of malware that could compromise this solution. The APWG (Anti-Phishing Work Group, an industry consortium) published last year a paper (“Mobile Fraud Supplement: Mobile Crimeware and Criminal Services Market”) which noted an emerging threat called “SMS Stealer apps.” These apps, which the miscreants try to get you to download onto your mobile device, can intercept SMS texts from specific sources and send them to the attackers. So far, these malicious apps have mostly been used to allow cyber criminals to circumvent SMS-based authentication for online banking. But I’d wager we’ll soon be seeing versions that target Twitter, Google, and Facebook SMSs as well.

Digits is an “ease of use” service, which does nothing to improve security, and -- by lulling users into a false sense of security -- it makes your mobile device less secure. If security of your device is of any interest to you then strengthen the authentication you use to unlock the device. That’s your best protection.

Dave Kearns is a senior analyst for Kuppinger-Cole, Europe's leading analyst company for identity-focused information security and networking. His columns and books have provided a thorough grounding in the basic philosophies of directory technology, networking, and identity ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
11/21/2014 | 8:15:51 AM
Re: Twitter should be ashamed.
Totally agree, Dave.  Consumers are still focused on card theft and need to become aware of the dangers they face from the growing amont of stolen personal information from social media, healthcare apps, etc., that is making criminals rich in the black market for that data. 
HAnatomi
50%
50%
HAnatomi,
User Rank: Apprentice
11/21/2014 | 1:18:37 AM
"Interference of Memory" can be easily overcome
Generally speaking, hard-to-break passwords are hard-to-remember.  But it is not the fate. 

At the root of the password headache is the cognitive phenomena called "interference of memory", by which we cannot firmly remember more than 5 text passwords on average.  What worries us is not the password, but the textual password.  The textual memory is only a small part of what we remember.  We could think of making use of the larger part of our memory that is less subject to interference of memory.  More attention could be paid to the efforts of expanding the password system to include images, particularly KNOWN images, as well as conventional texts.
dak3
100%
0%
dak3,
User Rank: Moderator
11/20/2014 | 11:23:43 AM
Re: Twitter should be ashamed.
One problem, though, is that most people aren't aware of the value of their data when it isn't a specifically monetary transaction (bank, retail, etc.). There's lots of money to be made (by hackers) in PII (Personnally Identifiable Information).
Bprince
50%
50%
Bprince,
User Rank: Ninja
11/20/2014 | 11:18:20 AM
Re: Twitter should be ashamed.
I agree. Really, I think when it comes to passwords, people just need to decide what they care about most (online banking, Facebook, Twitter etc) and try to come up with individual pass phrases or things that they can remember but other people won't realistically be able to guess. The rest of the accounts without meaningful info at stake don't really have to be as complex. 
Robert McDougal
50%
50%
Robert McDougal,
User Rank: Ninja
11/20/2014 | 10:39:29 AM
Twitter should be ashamed.
I don't see Digits as a step backwards in security, considering most apps don't prompt for a password once installed. However, for Twitter to claim this is a major step forward is misguided at best.
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/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
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.