1 / 11

Privacy Engineering for Digital Rights Management Systems

Privacy Engineering for Digital Rights Management Systems. By XiaoYu Chen. Introduction. The goal of Digital Rights Management Systems --- to protect rights of all parties involved in distribution DRM Systems may affect user privacy --- by “legitimately” collecting user information

kgarrett
Download Presentation

Privacy Engineering for Digital Rights Management Systems

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. Privacy Engineering for Digital Rights Management Systems By XiaoYu Chen

  2. Introduction The goal of Digital Rights Management Systems --- to protect rights of all parties involved in distribution DRM Systems may affect user privacy --- by “legitimately” collecting user information --- by “possibly” distributing user information Any guidelines when designing DRM? --- Fair Information Principle Any technological solutions which may help? --- Trusted Proxy, P3P,……

  3. Outline . Some typical technologies that play a role in DRM . The Fair Information Principle . Some high-tech solutions . Difference between privacy protection and control

  4. Several technologies that play a role in DRM systems • Security and integrity features of operating systems • Rights-management language and its related application • Encryption • Digital signatures • Fingerprinting and other “marking” techniques • Others ? DRM development should put these pieces together into an end-to-end system that serves all parties involved. Many other technologies are expected to participate

  5. Approaches to privacy engineering The Fair Information Principle: . Customizable Privacy . Collection Limitation . Database architecture and management . Purpose Disclosure . Choice . Client-side data aggregation . Transfer processed data . Competition of service . Keeping business interests in mind

  6. Fair Information Principle (continued) (1) Customizable Privacy --- Participants should be able to easily configure the system to set their preferred information-collection and handling mechanism Problem: make design complicated? Increase cost? (2) Collection Limitation --- A business should only collect information that it really needs and should disclose how such information will be used Problem: the definition of “information that it really needs”?

  7. Fair Information Principle (continued) (3) Database architecture and management ---A DRM system should provide easy pseudonymization that can be used to key database --- Data split and separation Problem: central or distributed management? (4) Purpose Disclosure (Notice) --- Notices should be easily understandable and thoroughly disclosed Problem: difficult to make all users clearly understand (5) Choice ---Give users choices for information collection

  8. Fair Information Principle (continued) 6) Client-side data aggregation and transfer processed data ---Aggregate data according to categories ---Don’t transfer data that is not to be used Problem: again, the definition of “data not to be used”? clear criteria for aggregating data? (7) Competition ofservice ---Can offer better service to customers Problem: Business entities like monopoly (8) Keeping business interests in mind ---understand business interests of different entities Problem: hard to achieve

  9. Enforcement of privacy solutions • Audit of privacy policies Problem: frequency? • Trusted proxies Problem: bottleneck? • P3P (Platform for Privacy Preferences) Problem: not an entire industrial standard yet

  10. Privacy protection and control • Most times difference is very slight • Protection involves more user’s willings (give or not) • Control may need more cooperation among parties and users to prevent abuse • Most times reasonable privacy control is enough, with very few exceptions

  11. Conclusion • Need to properly design,implement, deploy and use DRM in order to ---- Provide reasonable user privacy control ---- Supply business with necessary information ---- Run at a fair cost (2) FIP are only useful guidelines,not a technical standard Question: (1) What can be added to FIP to make it stronger? (2) What should users do in privacy control?

More Related