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.

Cloud

Google Adds Two-Factor Authentication for Its Apps on iOS

Android-based two-factor authentication now works for Google applications on iPad and iPhone.

Google now has extended its Android-based two-factor authentication to Google applications on iOS devices like iPads and iPhones.

The authentication app uses a certificate built into Android that responds to a challenge issued by a specific, enterprise-enabled website for authenticating both the user and website during login. Google apps or an account on the Google cloud presents a challenge screen to the user on their Android phone, asking them to verify it's really them logging into the account.

The company in May first introduced the Android-based 2FA mechanism for log-in to Google and Google Cloud services from ChromeOS, Windows 10, and MacOS devices. Now, it can also be used to protect login attempts from iPads and iPhones. 

Google's authentication is based on FIDO (Fast ID Online) security keys, which leverage public-key cryptography to verify both the user and login page URL, making it more difficult for an attacker who has stolen user credentials to abuse them.

Among the differences between the desktop environments and iOS systems is in the way the authentication appears to the user. To authenticate from a desktop, the user must launch a Chrome browser window to begin the login and initiate the 2FA process. In the iOS implementation, the Google Smart Lock app provides authentication for Google and Google Cloud applications.

Related Content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Christineh2019
50%
50%
Christineh2019,
User Rank: Apprentice
6/18/2019 | 5:00:17 AM
Changes regarding the new update
Do anyone know whether the update will change my original settings or not? 
The Security of Cloud Applications
Hillel Solow, CTO and Co-founder, Protego,  7/11/2019
Where Businesses Waste Endpoint Security Budgets
Kelly Sheridan, Staff Editor, Dark Reading,  7/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-13643
PUBLISHED: 2019-07-18
Stored XSS in EspoCRM before 5.6.4 allows remote attackers to execute malicious JavaScript and inject arbitrary source code into the target pages. The attack begins by storing a new stream message containing an XSS payload. The stored payload can then be triggered by clicking a malicious link on the...
CVE-2019-13644
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in a budget name. The JavaScript code is contained in a transaction, and is executed on the tags/show/$tag_number$ tag summary page.
CVE-2019-13645
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file names. The JavaScript code is executed during attachments/edit/$file_id$ attachment editing.
CVE-2019-13646
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to reflected XSS due to lack of filtration of user-supplied data in a search query.
CVE-2019-13647
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file content. The JavaScript code is executed during attachments/view/$file_id$ attachment viewing.