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-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

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?