Attacks/Breaches
3/15/2011
04:05 PM
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 December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-6477
Published: 2014-11-23
Unspecified vulnerability in the JPublisher component in Oracle Database Server 11.1.0.7, 11.2.0.3, 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality via unknown vectors, a different vulnerability than CVE-2014-4290, CVE-2014-4291, CVE-2014-4292, CVE-2014-4...

CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-8626
Published: 2014-11-22
Stack-based buffer overflow in the date_from_ISO8601 function in ext/xmlrpc/libxmlrpc/xmlrpc.c in PHP before 5.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code by including a timezone field in a date, leading to improper XML-RPC encoding...

CVE-2014-8710
Published: 2014-11-22
The decompress_sigcomp_message function in epan/sigcomp-udvm.c in the SigComp UDVM dissector in Wireshark 1.10.x before 1.10.11 allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?