Risk
5/8/2012
01:40 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Myspace Settles FTC Privacy Complaint

Now faded social network must tell the truth about how it handles personal information and undergo privacy audits for the next two decades.

Use Facebook Apps To Woo Customers: 6 Examples
Facebook Apps In Action
(click image for larger view and for slideshow)
Myspace on Tuesday settled charges brought by the Federal Trade Commission that it made false promises about protecting user data.

In its privacy policy and public statements, the faded social network promised not to share users' personally identifiable information with third parties without first asking permission and promised not to use personally identifiable information to customize ads.

Myspace violated those promises, according to the FTC. The company provided third-party advertisers with users' Friend IDs, which are account numbers linked to basic personal information. In so doing, the company enabled advertisers to create profiles linked to individual identities.

The FTC is not claiming that any ad company has made such a profile and the agency declined to discuss whether it might investigate whether any advertising network has compiled personal profiles using data gathered from Myspace. The settlement addresses the gap between Myspace's words--its privacy policy--and its actions.

[ Read Google+ Hangouts On Air: Broadcasting For All. ]

Regardless, advertisers didn't need to create Myspace user profiles because Myspace provided assistance with the delivery of personally targeted ads.

From January 2009 through June 2010--a year before the social network was sold for $35 million to Specific Media and celebrity Justin Timberlake--most of the ads displayed on Myspace were delivered via the Fox Audience Network (FAN), an ad network affiliated with Myspace.

To enable FAN to target ads, Myspace included the Friend ID, age, and gender of Myspace users in ad requests from Myspace Web pages, the FTC complaint says. And it did so in unprotected plain text. When FAN's ad inventory had no ad to place, the ad request was handed off to a third-party ad network to be filled, and the same personal information was provided. None of this was permissible under the terms of the Myspace privacy policy.

The settlement requires that Myspace cease misrepresenting its privacy promises. It also requires that Myspace set up a privacy program to protect users' information and to submit to independent third-party privacy audits every two years for the next 20 years.

Myspace might want to work on scheduling a site visit immediately: With Facebook, Google, and Twitter, among others, already under FTC orders to submit to biennial privacy audits, finding an available privacy inspector could be something of a challenge.

The Enterprise 2.0 Conference brings together industry thought leaders to explore the latest innovations in enterprise social software, analytics, and big data tools and technologies. Learn how your business can harness these tools to improve internal business processes and create operational efficiencies. It happens in Boston, June 18-21. Register today!

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-7392
Published: 2014-07-22
Gitlist allows remote attackers to execute arbitrary commands via shell metacharacters in a file name to Source/.

CVE-2014-2385
Published: 2014-07-22
Multiple cross-site scripting (XSS) vulnerabilities in the web UI in Sophos Anti-Virus for Linux before 9.6.1 allow local users to inject arbitrary web script or HTML via the (1) newListList:ExcludeFileOnExpression, (2) newListList:ExcludeFilesystems, or (3) newListList:ExcludeMountPaths parameter t...

CVE-2014-3518
Published: 2014-07-22
jmx-remoting.sar in JBoss Remoting, as used in Red Hat JBoss Enterprise Application Platform (JEAP) 5.2.0, Red Hat JBoss BRMS 5.3.1, Red Hat JBoss Portal Platform 5.2.2, and Red Hat JBoss SOA Platform 5.3.1, does not properly implement the JSR 160 specification, which allows remote attackers to exec...

CVE-2014-3530
Published: 2014-07-22
The org.picketlink.common.util.DocumentUtil.getDocumentBuilderFactory method in PicketLink, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 5.2.0 and 6.2.4, expands entity references, which allows remote attackers to read arbitrary code and possibly have other unspecified impact via...

CVE-2014-4326
Published: 2014-07-22
Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.