anonymity privacy
play

Anonymity & Privacy Alice Privacy EU directives (e.g. - PowerPoint PPT Presentation

Anonymity & Privacy Alice Privacy EU directives (e.g. 95/46/EC) to protect privacy. College Bescherming Persoonsgegevens (CBP) What is privacy? Users must be able to determine for themselves when, how, to what extent and


  1. Anonymity & Privacy

  2. Alice Privacy  EU directives (e.g. 95/46/EC) to protect privacy.  College Bescherming Persoonsgegevens (CBP)  What is privacy?  Users “ must be able to determine for themselves when, how, to what extent and for what purpose information about them is communicated to others ” (Definition PRIME, European project on privacy & ID management.) 2

  3. EU Data Protection Directive Personal data usage requirements:  Notice of data being collected  Purpose for data use  Consent for disclosure  Informed who is collecting their data  Kept secure  Right to access & correct data  Accountability of data collectors 3

  4. Security Attributes Privacy Recall Privacy Online Peter Steiner 1993 Nik Scott 2008 A lot of information revealed just by browsing see e.g. http://whatismyipaddress.com/

  5. Protecting Privacy  Hard privacy: data minimization  Subject provides as little data as possible  Reduce as much as possible the need to trust other entities  Example: anonymity  Issues; some information (needs to be) released.  Soft privacy: trusted controller  Data subject provides her data  Data controller responsible for its protection  Example: hospital database medical information  Issues; external parties, errors, malicious insider 5

  6. Anonymity & Privacy on the Net

  7. Example: Google  ``organize the world's information and make it universally accessible...’’  Clear risk for privacy; includes personal information  Multiple services; becoming `omnipresent’  Most searches (>90% in NL 2006) but also:  Searching books, (satellite) maps, images, usenet, news, scholarly papers, video’s, toolbar, account, email, calendar, photo program, instant messenger  Google & Doubleclick adds; used by many websites  All linked to IP address user (+os+browser+etc.). 7

  8. Info collected by Google service  Data mining to support services, custom ads  (old) Privacy policy  Allows sharing with third party with user consent  Provide data when `reasonably believes’ its legally required  Allows new policy in case of e.g. merger only notification needed (no consent) 8

  9. Google’s new privacy policy  Combine information different services  >60: search, YouTube, Gmail, Blogger, ...  Could already do for some, now extended We are confident that our new simple, clear and transparent privacy policy respects all European data protection laws and principle (Quote Google on BBC) Europe to investigate new Google privacy policy (reuters) Google privacy changes are in breach of EU law the EU's justice commissioner has said (BBC) 9

  10. Anonymous remailers Hide sender Clean header Forward to Destination (Temporary) Pseudonym Receiving a Reply 10

  11. Anonymous proxies  Hide (IP) requester from destination  Traffic analysis  Typically no protection against e.g. your ISP  Could encrypt connection proxy - client  No protection against the proxy itself  Performance Proxy: port y Service: port z Port x <=> Port y 11

  12. Tor  Union router for anonymity on the network  Hide requestor from destination & third parties  Traffic analysis  Timing attacks  Weaknesses in protocol  Malicious nodes  Performance  Also anonymous services Figures from Tor website 12

  13. Pseudonyms  On website do you enter correct info (name, address, etc.) when data not needed for service?  Some services support pseudonyms.  No direct link to user  Profiles possible if pseudonyms persistent  Privacy issue ?  Are pseudonym & group profiles personal data? 13

  14. Direct Anonymous Attestation Anonymity Revocation Authority 1. Register Prover (TPM) DAA Issuer 2. Certificate id i 3. Proof have certificate without revealing Cannot link 2,3 4. Provide service even if working together. DAA verifier  Revocation  of anonymous credentials  of anonymity 14

  15. The magical cave  Cave with a fork  Two passage ways  Ends of passages not visible from fork 15

  16. The magical Cave (2)  Cave with fork, two passage ways  Ends of passages not visible from fork  Ends of passages connected by secret passage way.  Only findable if you know the secret. 16

  17. The magical Cave (3)  I know the secret !  But I won’t tell you...  Can I still convince you I know the secret? 17

  18. Zero-Knowledge proof  Peggy and Victor meet at cave  Peggy hides in a passage  Victor goes to the fork Right!  calls out either left or right  Peggy comes out this passage  Uses secret passage if needed  Is Victor convinced ?  If repeated many times? From: Quisquater et al;How to explain Zero-Knowlege Protocols to Your Children 18

  19. Zero Knowledge proof  Peggy convinces Victor she know secret  Proof is zero knowledge Consider Victor tapes game Shows tape to you; will you be convinced?  Proof can be simulated by cheating verifier  Without a proofer who has secret 19

  20. Example protocol The Cave:  Secret S, p, q (large primes)  public n = p*q, I = S 2 mod n  P proof knowledge of S to V  P makes random R sends X = R 2 mod n Peggy hides  V makes & sends random bit E Left/Right  P sends Y = R * S E (mod n) Peggy comes out  V checks Y 2 = X * I E (mod n) Victor Sees Peggy 20

  21. Example protocol analysis  Completeness  With secret S can always correctly provide Y  Zero-knowledge; simulation by cheating verifier  Simulate run (X, E, Y): X = R 2 mod n  choose random Y , E Y = R or Y = R * S if E=1 take: X = Y 2 / I  if E=0 take: X = Y 2  Indistinguishable from real runs. No SQRT( X * S 2 ) and SQRT ( X ) at same time  Soundness  Without S: Has to choose X before knowing E:  Choose X so know R = SQRT( X ): No answer if E=1  Choose X so know Y = SQRT( X * S 2 ): No answer if E=0  Thus fails with probability 1/2 21

  22. Use of Zero knowledge proves  Example protocol show  Know secret for given public info  For applications e.g. DAA  Know values with special relation  ID along with a CA signature on this ID  E.g. know integers α , β , γ with properties: ZKP{( α , β , γ ): y = g α h β ^ y’ = g’ α h’ γ ^ (u ≤ α ≤ v)}  α , β , γ secrets, y,g,h,etc. known parameters  g,h generators group G, g’,h’ for G’ 22

  23. Direct Anonymous Attestation 1. Register; authenticate Prover (TPM) masked value f Prover (TPM) DAA Issuer {f} sg(DAA) ,f, id i f, id i 2. Certificate; signature on masked f 3. Proof have signature on f without revealing f, signature 4. Provide service DAA verifier 23

  24. Direct Anonymous Attestation  Peggy chooses secret f  Gets anonymous signature on f  Does not reveal f to issuer  Recall blind signatures e.g. with RSA E(mr e ) = (mr e ) d mod n = m d r mod n = E(m)r  Zero knowledge proof  knows an f together with a signature on f 24

  25. Direct Anonymous Attestation  Rogue member detection / revocation  Secret of Peggy = f, g generator of group  Peggy sends g f  Victor  Has list revoked f’  compares g f with g f’ for each on list  g not random: not seen to often 25

  26. `Soft’ Privacy Sometimes PII must be used. Privacy ~ use for correct purpose only

  27. Privacy Policy Statements  When entering a form on web pages  privacy policy: what may be done with data  Issues  To long and complex  No guarantees if policy is actually followed  No user preferences  Accept existing policy / do not use service 27

  28. P3P  Standardized XML based format for privacy policies  enables automated tool support  e.g. to decide accept cookie  Issues  Policies can be ambiguous  No definition how policy should be interpreted  Also no enforcement 28

  29. Enterprise Privacy: E-P3P / EPAL  Mechanisms for enforcement  within an enterprise  law often requires some for of enforcement  No External Check  For company; ensure employees follow policies  User still needs to trust company  Sticky Policies (policies stay with data)  Local to company  No guarantees outside administrative domain  Issue: No industry adoption 29

  30. Anonymizing data E.g. use db of health records for research

  31. Anonymized databases Medical Attacker Records Knowledge (“Public” attributes) 31

  32. Re-identify data by linking attributes k -anonymity: a model for protecting privacy, L. Sweeney in 32 International Journal on Uncertainty, Fuzziness and Knowledge-based Systems, 2002

  33. K-Anonymity (K=3) Alice Eve Alice Attacker Knowledge on Alice Mallory 33

  34. Restrict Quasi-ids to achieve l-Diversity: Privacy Beyond k-Anonymity by A. Machanavajjhala et al. in 34 ACM Transactions on Knowledge Discovery from Data 2007

  35. Attribute Disclosure Heart Disease Alice Heart Eve Disease Alice Attacker Knowledge on Heart Alice Disease Mallory 35

  36. Probabilistic disclosure Very rare Disease Alice Heart Eve Disease Alice Attacker Knowledge on Very rare Alice Disease Mallory 36

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend