1 / 26

Web Privacy Topics

Web Privacy Topics. Andy Zeigler Senior Program Manager, Internet Explorer Microsoft. Overview. Web Standards and Privacy CSS 2.1 Geolocation User Tracking Previous Approaches P3P Tracking Protection, “Do Not Track”. Web Standards and Privacy. CSS. CSS (Cascading Style Sheets)

knoton
Download Presentation

Web Privacy Topics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Privacy Topics Andy Zeigler Senior Program Manager, Internet Explorer Microsoft

  2. Overview • Web Standards and Privacy • CSS 2.1 • Geolocation • User Tracking • Previous Approaches • P3P • Tracking Protection, “Do Not Track”

  3. Web Standards and Privacy

  4. CSS • CSS (Cascading Style Sheets) • Core Web technology used for visually styling HTML markup • Develops use CSS to select HTML elements and apply a variety of styles (fonts, colors, sizes, etc.) • 1998: CSS 2.0 (W3C Recommendation) • Defines :visited selector

  5. :visited • Selects elements in a page that have previously been visited by a user: • :visited { color: red } • Changes all visited links to red • :visited { font-size: 200%} • Changes the font size of visited links to be 200% of what they normally would be • Causes changes in layout of the page • getComputedStyle() • Returns the actual style of any element in a page

  6. :visited -- Attack • Create a bunch of links in a page (like – 10000) • Style them with :visited • Detect that they have been visited either by detecting changes in layout, or by calling getComputedStyle() • Combine with XHR to send back to server

  7. CSS 2.0 If the following link: <A class="external" href="http://out.side/">external link</A> has been visited, this rule: A.external:visited { color: blue } will cause it to be blue.

  8. CSS 2.1 If the following link: <A class="external" href="http://out.side/">external link</A> has been visited, this rule: A.external:visited { color: blue } will cause it to be blue. • Note. It is possible for style sheet authors to abuse the :link and :visited pseudo-classes to determine which sites a user has visited without the user's consent. • UAs may therefore treat all links as unvisited links, or implement other measures to preserve the user's privacy while rendering visited and unvisited links differently. See [P3P] for more information about handling privacy.

  9. Geolocation • Allows a website to obtain the physical location of the user • Javascript API, supports • Latitude • Longitude • Accuracy • Elevation • …

  10. Geolocation Privacy Considerations • Considerations for browser vendors • “User agents must not send location information to Web sites without the express permission of the user. User agents must acquire permission through a user interface, unless they have prearranged trust relationships with users…” • Considerations for Websites • “Recipients must only request location information when necessary. Recipients must only use the location information for the task for which it was provided to them. Recipients must dispose of location information once that task is completed…” • Many other great examples in the spec

  11. Takeaways • Take privacy into consideration when authoring specifications • Privacy risks exist in most technologies – even ones that might appear to have little risk • Privacy issues can be very difficult to fix after a spec is implemented – privacy risk, compatibility, interoperability, etc. all must be balanced

  12. User Tracking

  13. User Tracking • Today, users are surreptitiously tracked as they browse the web for a variety of purposes: • Behavioral Profiling • Conversion Tracking • Site metrics • …

  14. User Tracking

  15. Further Reading • http://www.wsj.com/wtk

  16. Previous Approaches • P3P – “Platform for Privacy Preferences” • Websites express their privacy policies in a computer-readable format (XML) • Web Browsers download these preferences and compare them with the user’s preferences • Action is taken if the preferences are not compatible (cookies can be blocked, etc.)

  17. P3P Challenges • Too complex for users • Too simple for nuanced business relationships • Not a lot of incentive for websites to implement

  18. Tracking Protection • Tracking Protection Lists (TPLs) block tracking content • Users can add TPLs to protect their privacy • As the user browses the web, TPLs filter out tracking content

  19. Tracking Protection

  20. “Do Not Track” Header • HTTP header (“DNT: 1”) • Signals to Websites that the user prefers not to be tracked (exact definition TBD) • Requires that Websites “respect” the header by modifying their tracking behavior

  21. Takeaways • Lots of activity in W3C and IETF in Web Privacy • New W3C Working Group being formed • IE9 supports Tracking Protection and Do Not Track

  22. Thank you!

  23. Appendix: Tracking Protection Resources • Get a Tracking Protection List: http://www.iegallery.com/us/trackingprotectionlists/default.aspx • Documentation: http://msdn.microsoft.com/en-us/library/hh273399(v=VS.85).aspx • W3C Member Submission: http://www.w3.org/Submission/2011/SUBM-web-tracking-protection-20110224/

  24. Example List

More Related