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 //

Authentication

Rethinking Identity Management

Secret identities are a good thing. Multiple identities? Not so much

Having spent some years in security, I've often been at odds with myself over the concept of "single sign-on," in which an individual can use a single method of authentication to log onto multiple systems and applications.

On one hand, single sign-on is a boon because it gives users quick access to lots of resources without having to remember dozens of different passwords. On the other hand, a bad guy who steals individual passwords gains access to one application; a bad guy who steals your single sign-on credentials gains the keys to the kingdom.

With this latter point in mind, I've generally avoided consolidating my online identity, preferring the "multiple personality" approach that allowed me to use different passwords, different security questions, and even different names and birth dates on different systems. Better to be Steve Austin on one site and Clark Kent on another, I felt, than to make myself vulnerable on both sites at the same time.

Recently, however, I've begun to rethink this strategy. For one thing, maintaining multiple personalities is a pain in the neck. Trying to remember your username, password, and security questions is hard enough when you're one person. When you're Sybil and have 13 different personalities, it's nigh unto impossible.

For another thing, the technology is getting better. Password management and consolidation tools such as KeePass and LastPass are becoming more reliable and secure, and many of them offer a form of second-factor authentication that actually improves security.

New initiatives, such as the FIDO Alliance discussed in our main story in today's newly published Dark Reading digital issue on Web authentication, offer the promise of using a single interface for many different systems and applications, and take advantage of the most secure authentication tools available for each system.

More important than either of these points, however, is the fact that so much of the world is becoming Web-connected. Increasingly, who we are is defined by what we do on the Web. Google knows that I'm a security person, so it offers me search results that are slanted in that direction. Facebook offers me security-related ads, and LinkedIn tells me about security people I might want to connect with. There are advantages to having a single online identity, and those advantages will increase as Web technology improves and the promise of "Internet personalization" becomes reality.

Then again, the security person in me resists this idea. Do I really want Google, Facebook, and other sites collecting information about my online background and surfing habits? I find that increasingly -- if it can be done securely -- my answer is often yes. While I don't want websites to have all of my information, and while I believe all users should have the option to opt out, I am increasingly opting in. Having a single identity enables me to meet more people and do more things on the Web, and faster, than I could as Clark Kent and Steve Austin.

It's still a trade-off, but the costs and benefits of that trade are shifting. If the technology continues to improve, then it might soon be safer for all of us to be one person on the Web, instead of many. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
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
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-18986
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 allow attackers to brute-force (guess) valid usernames by using the 'forgot password' functionality as it returns distinct messages for invalid password and non-existing users.
CVE-2019-18981
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks an Access Denied outcome for a certain scenario of an incorrect recipient ID of a notification.
CVE-2019-18982
PUBLISHED: 2019-11-15
bundles/AdminBundle/Controller/Admin/EmailController.php in Pimcore before 6.3.0 allows script execution in the Email Log preview window because of the lack of a Content-Security-Policy header.
CVE-2019-18985
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks brute force protection for the 2FA token.
CVE-2019-18928
PUBLISHED: 2019-11-15
Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpreted in the authentication context of an unrelated previous request that arrived over the same connection.