Risk
5/8/2012
01:40 PM
Connect Directly
LinkedIn
Twitter
Google+
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
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
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.