This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Talk:Summit 2011 Working Sessions/Session073"

Jump to: navigation, search
Line 42: Line 42:
***[ Dlgs 196/03]
***[ Dlgs 196/03]
***[ Garante Privacy]
***[ Garante Privacy]
** Spain
***[ LeyOrganica 15/99]
***[ Real Decreto 1720/2007]
* US:
* US:
Line 61: Line 64:
** Italy
** Italy
***[ Garante Privacy]
***[ Garante Privacy]
** Spain
***[ Agencia Española de Protección de datos]
=== Issues ===
=== Issues ===

Revision as of 15:37, 17 February 2011

Thank you for attending! This page is for the session participants to add their ideas and comments.

Please also take a look at the draft FTC response - your input would be very welcome!

Thank you



I was asked to provide the top 3 accomplishments from our session to the summit team. I have suggested:

1) A recognition that OWASP MUST (not should) be active in this space

2) Direct input into OWASP's response to the FTC staff report on consumer privacy

3) A consensus to try to document the drivers, issues, resources and relevant technical approaches


Some suggested headings, but please feel free to add more:

Government legislation & policies


Primary data protection authorities:

  • US:
    • FTC
    •  ???


  • Fair processing
  • Acceptable use/specified purpose
  • Avoid collecting excessive information
  • Data accuracy
  • Data retention period enforcement (& disposal)
  • Protection of data
  • Transfers (inter department, company, country)
  • Tracking consent and withdrawal of consent
  • Provision of consent
  • Collection and storage of PII (personally identifiable information)
  • User tracking
  • User profiling

Privacy vulnerabilities

  • Build up user profiles used e.g. for retargetted / behavioral advertising
  • Identify users based on e.g. IP address, browser type and version, add-ons,... based on fingerprinting

Technical approaches

  • Privacy vulnerability detection on server side
  • Privacy vulnerability detection on client side
    • Client side patterns implying privacy vulnerability e.g.
      • 3rd party links (typically trackers)
      • 3rd party cookies
      • invisible images / web bugs
      • behavioral tracking patterns

Tools, Add-ons, Projects to Detect & Protect Privacy

1. Ghostery plug-in Available for Firefox, Chrome, Safari, Internet Explorer Scans the page for scripts, pixels, and other elements and notifies the user of the companies whose code is present on the page. These page elements aren't otherwise visible to the user, and often not detailed in the page source code. Ghostery allows users to learn more about these companies and their practices, and block the page elements from loading if the user chooses.


Ghostery is owned by Evidon (formerly "Better Advertising":

"Selected by the Digital Advertising Alliance (DAA) to power its online behavioral advertising Self-Regulatory Program"

2. Mozilla Firefox 4 Beta: "Do Not Track" Option - Privacy Feature You can check a “Do Not Track” box in the “Advanced” screen of Firefox’s Options. When this option is selected, a header will be sent signaling to websites that you wish to opt-out of online behavioral tracking. You will not notice any difference in your browsing experience until sites and advertisers start responding to the header.


Note: Also available for Google Chrome:

3. PrimeLife

Research project funded by the European Commission’s 7th Framework Programme Bringing sustainable privacy and identity management to future networks and services


Firefox extension Dashboard

This is a PrimeLife alpha release that helps you track what information is collected by the websites you visit, together with a means to set your preferences on a site by site basis.

The extension logs your http traffic to a local database on your computer, and provides a variety of queries for analyzing them. You can see whether the current website you are visiting uses third party content, invisible images and much more. You can set per site preferences, e.g. to block 3rd party cookies or content, to disable scripting and so forth. Note that some of these preferences only take effect when the page is reloaded or as you move to other pages within the same website. The extension adds an smiley icon to the browser's navigation toolbar. This changes to reflect a measure of the privacy friendliness of the current web page. Click on the face to view details for the current site. The first time you visit a less than perfect site, the Firefox notification bar appears and invites you to load the page this time, to always load the page or to view more options.


Micro survey

I created a micro survey on paper called A Few Questions, to try to gather a few views from other quarters in OWASP, as to the relevance of "personal data protection" within OWASP's mission. The questions are:

Q1: Can OWASP contribute to PCI-DSS compliance initiatives?


Q2: Can OWASP contribute to fraud detection and prevention?


Q3: Are there application vulnerabilities that can contribute to successful fraud?


Q4: Can OWASP contribute to the protection of personal data?

A4: (if 'no', skip Q5 and Q6 to end)

Q5: Are there application security vulnerabilities that can contribute to attacks against personal data?

A5: (if 'no', skip to end)

Q6: Are there vulnerabilities in the realms of personal data protection - consent, accuracy, fair use & retention (ie not just protection of data in use/at rest) - that OWASP can help with?


End: Pleasse supply any other comments here, or overleaf