Risk
6/24/2010
10:09 PM
Connect Directly
RSS
E-Mail
50%
50%

Twitter, Feds Settle Security Charges

Twitter must establish and maintain a "comprehensive information security program" and allow third-party review of the program biannually for the 10 years.

Twitter has settled Federal Trade Commission charges that the social network put users' personal information at risk, while deceiving them about safeguards to protect data.

The settlement, announced Thursday, closed the FTC's first action against a social networking site for faulty security. Twitter's failings led to two well-publicized attacks, one of which resulted in a hacker gaining access to several high-profile accounts, including that of then President-elect Barack Obama.

The settlement requires Twitter to take a number of security steps to protect user data, steps the site said it has already taken. "Even before the agreement, we'd implemented many of the FTC's suggestions and the agreement formalizes our commitment to those security practices," Twitter said in response to the FTC's settlement announcement.

Nevertheless, the FTC said Twitter failed to provide the security it promised users.

"When a company promises consumers that their personal information is secure, it must live up to that promise," David Vladeck, director of the FTC's Bureau of Consumer Protection, said in a statement. "Likewise, a company that allows consumers to designate their information as private must use reasonable security to uphold such designations."

The first security breach occurred in January 2009 when a hacker used an automated password-generation tool to continuously try to log in to a person's account. In some cases, the hacker made thousands of attempts before striking pay dirt. Twitter's culpability was in failing to implement password rules that would have led to stronger passwords, the FTC said. In addition, Twitter should have had technology in place to lock out the hacker after several failed attempts.

The hacker accessed the accounts of 45 Twitter users, including Facebook, Fox News, The Huffington Post, Obama, Britney Spears and CNN host Rick Sanchez. In some cases, the hacker sent phony tweets under the accounts. Tweets are the short messages of 140 characters or less people broadcast to followers on the site.

A bogus tweet sent from Obama's account offered his more than 150,000 followers a chance to win $500 in free gasoline, according to the FTC.

The second breach occurred in April 2009 when a hacker broke into a Twitter employee's administrative account by first accessing the employee's Yahoo e-mail account, where the password was stored in plain text.

In gaining access to the administrative account, the hacker could access private information from any Twitter user, according to the FTC. The hacker did post more than a dozen screenshots of Twitter's administrative console on several Web sites.

To help prevent the second breach, Twitter should have prohibited employees from storing passwords within personal e-mail accounts, enforced periodic changes of administrative passwords, restricted access to administrative controls to employees whose jobs required it and imposed other reasonable restrictions on administrative access, the FTC said.

Under the terms of the settlement. Twitter is barred for 20 years from misleading users about the extent to which it protects their privacy and personal information. The company also must establish and maintain a "comprehensive information security program," the FTC said. A third party has to assess the program every other year for 10 years.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Listen Now The Best of the Rest of Black Hat: The Enterprise View
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.