Endpoint
2/19/2013
05:28 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Good News From Google: Account Hijacking Down

How Google is verifying logins, getting results

Now for some good news: During a week when Facebook and then Apple -- yes, Apple -- admitted getting hacked and a report tied the Chinese military to a major cyberspy gang targeting U.S. businesses and organizations, Google's security team said it has seen the number of compromised Gmail accounts drop 99.7 percent since 2011.

Mike Hearn, a Google security engineer, today blogged that Google's efforts to determine the legitimacy of log-ins has cut those email account hijackings since their peak in 2011. The secret sauce: using more of a risk analysis process and Google's multifactor authentication steps for Google user accounts. "Every time you sign in to Google, whether via your web browser once a month or an email program that checks for new mail every five minutes, our system performs a complex risk analysis to determine how likely it is that the sign-in really comes from you. In fact, there are more than 120 variables that can factor into how a decision is made," Hearn said in his post.

If a login attempt appears suspicious -- originating from a different country since a user's last login, for example -- Google prompts the user with a few questions. "For example, we may ask for the phone number associated with your account, or for the answer to your security question. These questions are normally hard for a hijacker to solve, but are easy for the real owner. Using security measures like these, we've dramatically reduced the number of compromised accounts by 99.7 percent since the peak of these hijacking attempts in 2011," Hearn says.

Google has witnessed some hefty account-hijacking attempts. In one case, a single user used stolen passwords to try to break into 1 million Google accounts a day for weeks at a time, according to Hearn. "A different gang attempted sign-ins at a rate of more than 100 accounts per second," he said, noting that Google's security system doesn't just check the password's validity in order to thwart these types of attacks.

Google recommends strong passwords for Google accounts, its two-step authentication option, and updating account recovery options.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3586
Published: 2015-04-21
The default configuration for the Command Line Interface in Red Hat Enterprise Application Platform before 6.4.0 and WildFly (formerly JBoss Application Server) uses weak permissions for .jboss-cli-history, which allows local users to obtain sensitive information via unspecified vectors.

CVE-2014-5361
Published: 2015-04-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Landesk Management Suite 9.6 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) start, (2) stop, or (3) restart services via a request to remote/serverServices.aspx.

CVE-2014-5370
Published: 2015-04-21
Directory traversal vulnerability in the CFChart servlet (com.naryx.tagfusion.cfm.cfchartServlet) in New Atlanta BlueDragon before 7.1.1.18527 allows remote attackers to read or possibly delete arbitrary files via a .. (dot dot) in the QUERY_STRING to cfchart.cfchart.

CVE-2014-8111
Published: 2015-04-21
Apache Tomcat Connectors (mod_jk) before 1.2.41 ignores JkUnmount rules for subtrees of previous JkMount rules, which allows remote attackers to access otherwise restricted artifacts via unspecified vectors.

CVE-2014-8125
Published: 2015-04-21
XML external entity (XXE) vulnerability in Drools and jBPM before 6.2.0 allows remote attackers to read arbitrary files or possibly have other unspecified impact via a crafted BPMN2 file.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.