Vulnerabilities / Threats

2/10/2011
06:27 PM
Connect Directly
Google+
LinkedIn
Twitter
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
Comments
Threaded  |  Newest First  |  Oldest First
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.