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.

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.
Firms Improve Threat Detection but Face Increasingly Disruptive Attacks
Robert Lemos, Contributing Writer,  2/20/2020
Ransomware Damage Hit $11.5B in 2019
Dark Reading Staff 2/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19668
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-17963. Reason: This candidate is a reservation duplicate of CVE-2018-17963. Notes: All CVE users should reference CVE-2018-17963 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2019-12882
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2017-6363
PUBLISHED: 2020-02-27
** DISPUTED ** In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for...
CVE-2017-6371
PUBLISHED: 2020-02-27
Synchronet BBS 3.16c for Windows allows remote attackers to cause a denial of service (service crash) via a long string in the HTTP Referer header.
CVE-2017-5861
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000020. Reason: This candidate is a reservation duplicate of CVE-2017-1000020. Notes: All CVE users should reference CVE-2017-1000020 instead of this candidate. All references and descriptions in this candidate have been removed to...