Risk

4/10/2019
02:00 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Android Phones Now Double as Physical Security Keys

Google debuted a series of security updates at Next 2019, giving users the option to use their phone as a second authentication factor.

Android smartphones running version 7.0 (Nougat) or later now work as physical security keys for two-factor authentication when logging into personal Google accounts and G Suite, Google Cloud Platform, and other Google apps used in and out of the office, Google announced today.

This means security-savvy Android phone users don't have to purchase a physical key to strengthen their account protection. Google already offers the Titan Security Key, a FIDO-standard device typically used for high-value users or content, which works as a second factor for Google logins. A secure hardware chip is designed to protect against firmware attacks.

Of course, Google already offers several methods of two-factor authentication: SMS verification codes, the Google Authenticator app, and Google Prompts. But two-factor verification options vary in their security, and each has its holes. For example, an attacker could target a specific user and intercept a code sent via text message, granting them access to someone's account.

Hardware keys are considered the strongest option of two-factor authentication, with protocols based on standard public key cryptography to block account takeover attempts. Most everyday users don't go out of their way to buy them. However, if the key is built into a device they already have, it could stand a chance at overcoming the convenience hurdle impeding growth.

The Android-based security key, which also uses the FIDO protocol, requires a user to sign in on a Bluetooth-enabled Chrome OS, macOS X, or Windows 10 device with a Chrome browser.

How to set it up: Once you have an updated Android phone and Bluetooth-enabled computer with an updated Chrome browser and OS, add the key to your Google account. Turn on 2-Step verification and add a method like Google Prompts (if you don't use it already). Go to myaccount.google.com/security. Under "Signing in to Google" select "2-Step Verification." Scroll to choose a second step and click Add Security Key > Your Android phone > Turn on.

Once that's complete, make sure your computer has Bluetooth turned on and go to sign into your Google Account. Your phone should alert you with a notification to confirm it's you.

The hardware security key is currently in beta mode and only works for Google applications.

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

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
niajax
50%
50%
niajax,
User Rank: Apprentice
4/19/2019 | 1:42:49 AM
Wait is over for Physical Security Keys
Hi Kelly,

It's great to know about Androdi Phones with Physical Security Keys. Google keeps updating the latest features to make Android more user-friendly & especially for Security.

This Physical Security Keys update with Android Security Keys will be one of the best updates for security. Many Android users will be happy with this update.

I will update my Android and will use this Physical Security Keys feature as the set it up instruction is already shared by you, Kelly.
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-18643
PUBLISHED: 2019-04-25
GitLab CE & EE 11.2 and later and before 11.5.0-rc12, 11.4.6, and 11.3.10 have Persistent XSS.
CVE-2018-19359
PUBLISHED: 2019-04-25
GitLab Community and Enterprise Edition 8.9 and later and before 11.5.0-rc12, 11.4.6, and 11.3.10 has Incorrect Access Control.
CVE-2019-11488
PUBLISHED: 2019-04-25
Incorrect Access Control in the Account Access / Password Reset Link in SimplyBook.me Enterprise before 2019-04-23 allows Unauthorized Attackers to READ/WRITE Customer or Administrator data via a persistent HTTP GET Request Hash Link Replay, as demonstrated by a login-link from the browser history.
CVE-2019-11489
PUBLISHED: 2019-04-25
Incorrect Access Control in the Administrative Management Interface in SimplyBook.me Enterprise before 2019-04-23 allows Authenticated Low-Priv Users to Elevate Privileges to Full Admin Rights via a crafted HTTP PUT Request, as demonstrated by modified JSON data to a /v2/rest/ URI.
CVE-2019-3720
PUBLISHED: 2019-04-25
Dell EMC Open Manage System Administrator (OMSA) versions prior to 9.3.0 contain a Directory Traversal Vulnerability. A remote authenticated malicious user with admin privileges could potentially exploit this vulnerability to gain unauthorized access to the file system by exploiting insufficient san...