Twitter Hack Tars Google's Cloud

The distribution of internal Twitter documents by a hacker has revived doubts about the security of cloud computing. But Google wants everyone to know that security tools are available for those who want to use them.

In a blog post on Wednesday about the distribution of internal Twitter documents by a hacker, company co-founder and creative director of Biz Stone traced the origin of the online break-in to a compromised personal e-mail account of an administrative employee.

And then Stone brought Google into the picture: "From the personal account, we believe the hacker was able to gain information which allowed access to this employee's Google Apps account which contained Docs, Calendars, and other Google Apps [that] Twitter relies on for sharing notes, spreadsheets, ideas, financial details and more within the company," he explained.


More Internet Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The hacker claims to have guessed the answer to the Twitter employee's security question and reset the password of the account in question.

Though Stone made clear that the attack was not the result of any vulnerability in Google Apps, the incident nonetheless prompted yet another round of doubt about cloud-based services.

Albert Wenger, a partner at venture capital firm Union Square Ventures, an investor in Twitter, said on his blog that the break-in demonstrates the inadequacy of usernames and passwords as a means of authentication. He urged online services like Google and Microsoft to adopt a two-factor authentication scheme, possibly involving SMS messages or a dedicated mobile authentication app.

Google, having witnesses the brand damage security issues have inflicted upon Microsoft, is keen to seen as more secure than the competition and moved quickly to quell the disparagement of cloud computing.

Acknowledging only that "there's been some discussion today about the security of online accounts," Google engineer Macduff Hughes said in a blog post that the company wanted to share its perspective.

Apparently reacting to the hacker's claim to have breached Twitter by answering a security question to reset an online password, Hughes explained that Gmail's password setting and recovery process is more involved than many other services. For instance, Google recently added the ability to enter a mobile phone number for receiving password recovery authorization notices. The company also provides the opportunity to enter a secondary e-mail address for password change confirmations.

"[I]f you want to initiate a password reset, we'll only send that information to the secondary address or the mobile phone number you provide," said Hughes.

In addition, Gmail also allows users to see the IP address and time of their last login, which may help users recognize unauthorized access.

Google doesn't allow Google Apps users to reset their passwords; all such requests must be authorized by Google Apps administrators. And since 2006, Google Apps has supported SAML Single Sign On, for two factor authentication.

For such tools to be effective, however, people need to use them.

Andrew Storms, director of security operations for nCircle, a network security company, said that we need to recognize that the personal and work lives of today's information workers have become intertwined. "Just putting a pet's name on a Facebook page could allow hackers to obtain your password," he said.

Storms urges employers to pay more attention to educating workers about safe computing practices. And he said that companies need to do their due diligence to determine how data is stored at online services.

Janz Yaneza, site research manager for Trend Micro, said the Twitter hack really comes down to proper account management. He recommended that companies have a data leakage prevention system in place and that individuals think carefully before publishing any information to social networking sites.

InformationWeek has published an in-depth report on managing risk. Download the report here (registration required).


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links