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
Comments
Oldest First  |  Newest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.