Vulnerabilities / Threats
2/10/2011
06:27 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%
Repost This

Google Enables Two-Factor Authentication For All

You can now protect your Google Account with security techniques employed by online banks.

Having recently made two-factor authentication available for Google Apps customers, Google on Thursday extended its more secure sign-on mechanism to all Google Accounts.

Google calls the process two-step verification. It is intended to reassure those who believe they need more than a mere password standing between their online data and the cyber-thieves of the world.

"Two-step verification requires two independent factors for authentication, much like you might see on your banking Web site: your password, plus a code obtained using your phone," explains Google product manager Nishit Shah in a blog post.

The set-up process isn't ridiculously onerous, but it isn't drop-dead easy either. Google suggests setting everything up may take 15 minutes. Thoughtfully, users aren't entirely on their own: Google provides a set-up wizard to guide people through the necessary steps.

Turning two-step verification on is done through the "Using 2-step verification" link on the Google Account Settings page. Users who don't see any such link can expect it to be available within the next few days.

Once enabled, a user who signs in with the Account password will be presented with an extra Web page asking for a code. Google will either generate an automated call with the code, send the code to a mobile phone via SMS, or allow the user to generate the code using an app on an Android, BlackBerry or iPhone device.

A particularly convenient feature is the ability to register a backup phone to receive codes, in case one's primary phone get stolen or is lost.

Additional security, however, should not be confused with foolproof security. In late 2009, Gartner issued a research note recommending further defenses beyond two-factor authentication. It seems cyber-thieves have had some success bypassing two-factor security schemes at some banks using man-in-the-middle attack techniques. The fraudsters managed to have verification phone calls associated with compromised accounts forwarded to their own phones.

But Google's decision to offer extra security to those who want it represents a step in the right direction.

Matt Cutts, who runs Google's Web spam team, notes that two of his relatives have had their Gmail accounts hijacked because someone guessed their passwords.

"If someone hacked your Gmail account, think of all the other passwords they could get access to, including your domain name or Web host accounts," he wrote in a blog post.

While conceding that the extra security of two-step verification may be an inconvenience, he insists it's worth the trouble. "I use it on my personal Gmail account, and you should too," he said.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web