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

5/28/2019
12:00 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail

8 Ways to Authenticate Without Passwords

Passwordless authentication has a shot at becoming more ubiquitous in the next few years. We take a look at where things stand at the moment.
8 of 9

Ping Identity

Ping Identity CISO Robb Reck says the promise of future continuous, risk-based authentication is better security and improved convenience. By using multifactor authentication, Ping Identity can use sensors in people's phones and laptops to continuously authenticate users and allow them to access their resources based on the quality of that ongoing trust. This process only calls for authentication when trust is lost, and then only requests the level of assurance required for the type of transaction the user wants to make.

'The key to a successful end-user experience is providing it regardless of the device the consumers are connecting from,' Reck says. 'A huge portion of consumer-facing businesses, such as online retail, have moved to the smartphone, so any customer experience initiative needs to consider that platform from the start.'

Ping plans to replace passwords with push notifications to mobile devices and offer scannable QR codes, which produce one-time passcodes for users, Reck says. With the PingID mobile SDK, enterprises can balance security and convenience for customers by embedding advanced MFA functionality directly into their own iOS or Android mobile apps. This lets organizations allow their customers to log in with easier methods than having to remember a password.

The same goes for laptops and PCs, Reck adds. Organizations are replacing passwords and supplementing them in the sign-on process to these devices.

'By adding multifactor authentication to processes like Windows login, organizations can either remove password requirements and instead have employees use a friendlier range of mobile push authentication methods, or use those in addition to passwords for a more secure logon process,' Reck says. 'We're also implementing Windows Hello as an authentication factor in PingID with the same intention.'

Image Source: Ping Identity

Ping Identity

Ping Identity CISO Robb Reck says the promise of future continuous, risk-based authentication is better security and improved convenience. By using multifactor authentication, Ping Identity can use sensors in people's phones and laptops to continuously authenticate users and allow them to access their resources based on the quality of that ongoing trust. This process only calls for authentication when trust is lost, and then only requests the level of assurance required for the type of transaction the user wants to make.

"The key to a successful end-user experience is providing it regardless of the device the consumers are connecting from," Reck says. "A huge portion of consumer-facing businesses, such as online retail, have moved to the smartphone, so any customer experience initiative needs to consider that platform from the start."

Ping plans to replace passwords with push notifications to mobile devices and offer scannable QR codes, which produce one-time passcodes for users, Reck says. With the PingID mobile SDK, enterprises can balance security and convenience for customers by embedding advanced MFA functionality directly into their own iOS or Android mobile apps. This lets organizations allow their customers to log in with easier methods than having to remember a password.

The same goes for laptops and PCs, Reck adds. Organizations are replacing passwords and supplementing them in the sign-on process to these devices.

"By adding multifactor authentication to processes like Windows login, organizations can either remove password requirements and instead have employees use a friendlier range of mobile push authentication methods, or use those in addition to passwords for a more secure logon process," Reck says. "We're also implementing Windows Hello as an authentication factor in PingID with the same intention."

Image Source: Ping Identity

8 of 9
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
ScottyTheMenace
50%
50%
ScottyTheMenace,
User Rank: Apprentice
6/6/2019 | 5:46:08 PM
Touch ID is not passwordless
Not sure if it was your intent to suggest that it was, but Apple's Touch ID is not passwordless.

In iOS, you still have to set a passcode, and it seems to be the passcode that actually unlocks your device. All Touch ID does is use your fingerprint to fill the passcode into the field. (I don't know the technical details to know that's the case, but it sure seems like that's what's happening.) You're also forced to use the passcode seemingly at random (though it's probably time delimited) and to activate Touch ID after a restart.

I love using Touch ID—it's quite convenient—but its dependence on a typed passcode actually encourages users to use weak passcodes that are easily remembered since they'll eventually need to type it in, and typing the passcode* 984ELBMYAq[[email protected]%t5sM+5{j=9AYH__4jqDr on a touch keyboard is not real fun.

 

* Generated just now. Not any of my passwords. C'mon now, do I look that dumb? DON'T ANSWER THAT!
wibblewibble
100%
0%
wibblewibble,
User Rank: Apprentice
5/30/2019 | 7:49:18 AM
SQRL
Don't forget SQRL! https://www.grc.com/sqrl/sqrl.htm
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Human Nature vs. AI: A False Dichotomy?
John McClurg, Sr. VP & CISO, BlackBerry,  11/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
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-2011-3350
PUBLISHED: 2019-11-19
masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper privilege dropping.
CVE-2011-3352
PUBLISHED: 2019-11-19
Zikula 1.3.0 build #3168 and probably prior has XSS flaw due to improper sanitization of the 'themename' parameter by setting default, modifying and deleting themes. A remote attacker with Zikula administrator privilege could use this flaw to execute arbitrary HTML or web script code in the context ...
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.