Attacks/Breaches
3/15/2011
04:05 PM
Connect Directly
RSS
E-Mail
50%
50%

Twitter Finalizes FTC Security Settlement

The microblogging company agrees to a biennial external audit of its security posture for the next 10 years.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches

The FTC announced on Friday that it's closed its security investigation into Twitter, after the social networking giant accepted a settlement first fielded in June 2010. The settlement stems from the FTC's charge that "Twitter deceived consumers and put their privacy at risk by failing to safeguard their personal information."

According to the FTC's settlement, Twitter must now establish and maintain "a comprehensive information security program that is reasonably designed to protect the security, privacy, confidentiality, and integrity of nonpublic consumer information." For the next 10 years, Twitter's security program must also undergo an external audit every two years.

Meanwhile, for the next 20 years, Twitter is barred from making misleading statements about "the security, privacy, and confidentiality of nonpublic consumer information, including the measures it takes to prevent unauthorized access to nonpublic information and honor the privacy choices made by consumers," said the FTC.

The settlement is the end result of the FTC's investigation into security breaches that occurred at Twitter between January and March of 2009, when hackers twice gained administrative control of the site. Despite Twitter's previous privacy policy, which assured users that "we employ administrative, physical, and electronic measures designed to protect your information from unauthorized access," attackers hacked into the site the first time by using a brute-force password hacking tool, and the second by simply guessing an administrator's password.

The breaches gave attackers access to non-public user information, tweets that users had designated as "private," and enabled attackers to generate fake tweets. Owners of the compromised accounts included then-President-elect Barack Obama and Fox News.

Of course, those aren't the only security incidents to have involved Twitter and hijacked accounts. "Twitter has experienced numerous high-profile security incidents, including Britney Spears and U.K. members of parliament selling Viagra. And there have been many incidents that have hit users who aren't celebrities," said Rob Rachwald, director of security for Imperva, via email.

"Such incidents indicate that security was very low on Twitter's priority list," he said. "But this is nothing new. Given a choice between growth and security, companies typically skimp on security."

The FTC's settlement with Twitter, however, now requires specific security program enhancements, including designating one or more employees to coordinate and remain accountable for its information security program. Twitter must also conduct a data security risk assessment, implement "reasonable safeguards" to mitigate identified risks, and ensure that any service providers with which it works also maintain appropriate data security safeguards.

Under the settlement, Twitter faces up to a $16,000 fine for every violation of its agreement. The private company has a market value recently estimated to be $8 billion to $10 billion.

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.