Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

6/25/2009
01:57 PM
Sara Peters
Sara Peters
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

EU Group: Social Networks, Thirty-Party App Developers Subject To EU Privacy Laws

I just took a close look at the Article 29 Data Protection Working Party's opinion report on online social networking. While some of its recommendations are what you'd expect, others came as a surprise.

I just took a close look at the Article 29 Data Protection Working Party's opinion report on online social networking. While some of its recommendations are what you'd expect, others came as a surprise.The report (PDF) "principally is intended to provide guidance to SNS [social network service] providers on the measures that need to be in place to ensure compliance with EU law." Social network providers, both inside and outside of the EU, ought to pay heed to this report -- but they're not the only ones. The app developers who use the social networks' APIs to build apps for those platforms should also give it a close read. So should users, whether you use the service for personal reasons or use it for professional reasons -- particularly if your organization is using social networks for marketing purposes.

The Working Party is an independent European advisory board on data protection and privacy. Some of the Party's recommendations are not out of the blue: making users very aware of how their data is being used; more secure default settings; deleting all a user's account data immediately after they cancel their account, etc.

Others, however, are less expected.

For example, the Party recommends that SNS should allow users to adopt a pseudonym. Although rarely enforced, one of Facebook's terms of service is that user's must use their real name. (I'll give Facebook this: Last year I found users named "Fake Name," "Faketh Nameth," and "Betsy Faken Namer," to name a few. I did not, however, find any such people in my Facebook people search today.)

The Party's rationale for the "allow pseudonyms" recommendation is "Article 6 para 1 letter c) of the [EU] Data Protection Directive requires the data to be 'adequate, relevant and not excessive in relation to the purposes for which they are collected and/or further processed.' In this context, it can be observed that SNS may need to register some identifying data about members but does not need to publish the real name of members on the Internet."

The strong privacy rules also apply to those miscreants whose dirty deeds get them banned from these SNS. The recommendations say "Some SNS also retain identification data of users who were banned from the service, to ensure that they cannot register again. In that case, these users must be informed that such processing is taking place. In addition, the only information that may be retained is identification information, and not the reasons why these persons were banned. This information should not be retained for more than one year." It is not clear to me whether by "this information" they mean only the "reasons why these persons were banned" or the identification information as well. I've contacted the Working Party to get some clarification.

The Party also says that third-party application developers may in some cases be considered "data controllers" which means they may also be subject to these privacy mandates. For example, the app developers are advised not to perform any operations on imported user contacts' data other than personal usage.

Further, they advise the social network services and marketers that any "behavioral marketing"--which selects which ads to serve up to users based on observation and analysis of those users' activity over time--is rather naughty as well.

Note well, these are recommendations, not official mandates. They're not made to get in trouble; rather they're made to keep you out of trouble.

Now ain't that neighborly? Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.