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

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
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.