Endpoint

3/6/2018
04:54 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Identity Management: Where It Stands, Where It's Going

How companies are changing the approach to identity management as people become increasingly digital.

Digital identity plays a role in everything you do, inside the enterprise and out. The growth of applications and services has demanded companies and consumers change their approach to how they manage their identities and authenticate to the apps they use.

"Being able to move through the world, to do everything from managing healthcare to banking to entertainment to leisure time … all revolve, at least for most people, around various forms of online interaction," says Joan Pepin, CISO at Auth0. "Who you are, and being able to authenticate who you are, is really core to all of that."

As the number of devices we interact with continues to increase, and online services increase, the issue of identity management will continue to grow. There are several methodologies to solve any identity problem: banks, entertainment providers, cable companies, media services, and social networks may all employ different forms of verification.

"This gets confusing not only for consumers, but for the technologists implementing [identity management] as well," she notes. "It's a really big topic and a really big space."

Changing Mindsets - and Passwords

"There's an often-touted nature that security and convenience are natural enemies, and in order to make something more secure you need to make it less convenient," says Pepin. "The fact we've allowed that to be the dominant paradigm has put us in some bad spots."

Making security easier for end users will make them more secure, she continues. Companies that consider themselves secure often require long, complicated passwords to be changed every 30, 60, or 90 days. The intention to improve security ultimately backfires when employees start to keep track of passwords by writing them down on their monitors.

The average American internet user has 150 online accounts requiring a password, according to Dashlane, and this number is expected to hit 300 by 2022. Keeping today's authentication practices would mean creating - and remembering - a complex password for each one.

Password managers seem like a strong answer but aren't catching on. A 2017 Pew Research Center study found only 12% of Americans use a password management tool; 86% keep track of passwords by memorizing them. It seems many would prefer not to use passwords at all.

As part of its 2017 "Future of Identity Study," IBM researchers polled nearly 4,000 adults around the world to learn about their authentication preferences. They found 75% of Millennials (ages 20-36) are comfortable using biometrics, less than half use complex passwords, and 41% reuse passwords across services - a sign the identity landscape is shifting.

New User Expectations, New Approaches

Alex Simons, director of program management for Microsoft's Identity Division, says "every major organization in the world" is going through a transition from on-prem only environments to "individual nodes of compute." Each business will have an on-prem node but still work in Salesforce, Amazon, and Microsoft, juggling their identities across each service.

"You're going to have this whole web of interconnected nodes of compute," he says. A similar shift is happening among consumers, who use more devices and services from more locations.

"There's a consumer-driven move to using lots of different devices to get things done," Simons continues. "It's not just about 'my PC' and 'my office.'" We've evolved into a world where people expect to use any of their chosen devices to work no matter where they are.

The primary way businesses get compromised is through poorly managed usernames and passwords, says Simons, and cybercriminals can use stolen credentials to compromise a VPN and move throughout a network. Many companies address the problem with multi-factor authentication, and most people choose to confirm their identity with a phone call or text.

He points to FIDO2, a new Web authentication protocol, as an example of a transformational change in the IAM space. The newest standard from the FIDO Alliance was developed with tech companies including Google, Microsoft, Mozilla, and PayPal, to change authentication.

FIDO authenticates using asymmetric challenge-response. Each user has a private key and a public key. The former is stored securely; the latter is given to websites for authentication. A website with your public key sends you a challenge, which you sign with your private key. The site verifies your signature and if it's correct, logs you in.

Simons explains how the FIDO2 set of specifications lets users securely log in with biometrics. Smartphones, watches, badges, buttons, and other "smart" objects will be able to authenticate in a way that doesn't require a username and password. Microsoft is bringing this type of login to Windows 10 in the spring; companies like Google and Mozilla have similar initiatives.

"The philosophy is biometric data should never be centrally managed," he says, adding how companies are adverse to large stores of biometric data. "FIDO standards assume biometric data is locally managed on whatever the hardware device is."

More websites let users authenticate with multiple identities; for example, using your Facebook identity to authenticate into an Airbnb account.

"Increasingly, you have the ability to go to a website or app and log in using whatever identity you want," says Simons. "Those standards now are at the place where it's becoming increasingly easy to integrate those into your applications."

However, Pepin notes, it's imperative to trust providers before adopting social media logins. "The flipside is now we rely on whatever controls those social companies have put in place," she says. "If you can trust them to have good processes, that's a fantastic option … if you can't trust them, it's not a fantastic option."

Related Content:

 

 

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
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
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-8023
PUBLISHED: 2018-09-21
Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timin...
CVE-2018-14643
PUBLISHED: 2018-09-21
An authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman. A malicious attacker can use this flaw to remotely execute arbitrary commands on machines managed by vulnerable Foreman instances, in a highly privileged context.
CVE-2018-14645
PUBLISHED: 2018-09-21
A flaw was discovered in the HPACK decoder of HAProxy, before 1.8.14, that is used for HTTP/2. An out-of-bounds read access in hpack_valid_idx() resulted in a remote crash and denial of service.
CVE-2018-1685
PUBLISHED: 2018-09-21
IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, and 11.1 contains a vulnerability in db2cacpy that could allow a local user to read any file on the system. IBM X-Force ID: 145502.
CVE-2018-1710
PUBLISHED: 2018-09-21
IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 10.1, 10.5, and 11.1 tool db2licm is affected by buffer overflow vulnerability that can potentially result in arbitrary code execution. IBM X-Force ID: 146364.