what you are looking for
play

What You Are Looking for? Simon Oya, Carmela Troncoso, Fernando - PowerPoint PPT Presentation

Dec 17, 2023 •113 likes •216 views

Is Geo-Indistinguishability What You Are Looking for? Simon Oya, Carmela Troncoso, Fernando Prez-Gonzlez 1 Motivation. Obfuscation-Based Location Privacy. Location information is sensitive. I want to use location services Solution:

  1. Is Geo-Indistinguishability What You Are Looking for? Simon Oya, Carmela Troncoso, Fernando Pérez-González 1

  2. Motivation. Obfuscation-Based Location Privacy. • Location information is sensitive. I want to use location services • Solution: obfuscation mechanisms without disclosing my location Service I’m at the fake location provider , closest ? Here you go! • We get some privacy. In this work • We lose some quality of service. We study the privacy implications of • There are many metrics to assess the privacy of geo-indistinguishability, revealing • A popular notion is geo-indistinguishability . some of its issues. 2

  3. Geo-Indistinguishability [1] • GeoInd means ensuring that and are “indistinguishable” given . • Mathematically: Real Another real location location Obfuscation mechanism Obfuscated location Privacy parameter Distance metric (e.g., Euclidean) Less privacy Less privacy (easier to distinguish) More privacy More privacy (harder to distinguish) 3 [1] Andrés, Miguel E., et al. "Geo-indistinguishability: Differential privacy for location-based systems." CCS’13 .

  4. Choosing the GeoInd Privacy Parameter • How do we choose ? • Typical approach: • How do we choose ? • From log(1.4) to log(10). Privacy radius • Normally, log(2). • Example: Privacy level • Inside the region, we get: Hard to interpret 4

  5. GeoInd as an Adversary Error • Decision Adversary: Assume , so the adv. decides . gives GeoInd if and only if, : • Previous example: Easier to interpret 5

  6. GeoInd in Numbers • Two GeoInd mechanisms: Laplace [1] and Laplace with remapping [2]. • Example. • Privacy goal: for locations in • Laplace: Reported location here on average Reported location 95% of the time is here [1] Andrés, Miguel E., et al. "Geo-indistinguishability: Differential privacy for location-based systems." CCS’13 . 6 [2] Chatzikokolakis, Konstantinos, Ehab ElSalamouny, and Catuscia Palamidessi. "Efficient Utility Improvement for Location Privacy." PoPETS’17. 308-328.

  7. GeoInd in Numbers • Two GeoInd mechanisms: Laplace [1] and Laplace with remapping [2]. • Example. • Privacy goal: for locations in • Laplace: • Laplace + RM: (Gowalla dataset) Reported location here on average Reported location 95% of the time is here [1] Andrés, Miguel E., et al. "Geo-indistinguishability: Differential privacy for location-based systems." CCS’13 . 6 [2] Chatzikokolakis, Konstantinos, Ehab ElSalamouny, and Catuscia Palamidessi. "Efficient Utility Improvement for Location Privacy." PoPETS’17. 308-328.

  8. The price we pay is too high GeoInd in Numbers for the privacy we get!! Bad privacy-utility trade-off • Two GeoInd mechanisms: Laplace [1] and Laplace with remapping [2]. • Example. • Privacy goal: for locations in • Laplace: • Laplace + RM: (Gowalla dataset) Reported location here on average • In terms of average error , other mechanisms perform better than Reported location 95% Laplace. of the time is here [1] Andrés, Miguel E., et al. "Geo-indistinguishability: Differential privacy for location-based systems." CCS’13 . 6 [2] Chatzikokolakis, Konstantinos, Ehab ElSalamouny, and Catuscia Palamidessi. "Efficient Utility Improvement for Location Privacy." PoPETS’17. 308-328.

  9. Where is the problem? • GeoInd comes from differential privacy. • Differential Privacy scenarios: low sensitivity queries. • It is possible to achieve with high privacy • User-centric Location Privacy: high sensitivity queries ! Solutions? • Re-design location queries to have low sensitivity [1]. • Use bandwidth as a resource to improve utility [1] . • Use less ambitious privacy metrics… 9 [1] Andrés, Miguel E., et al. "Geo-indistinguishability: Differential privacy for location-based systems." CCS’13 .

  10. Conclusions • Evaluate privacy and quality loss ALL ABOARD numerically . • GeoInd as an adversary error can THE GEOIND help in this regard. TRAIN!!! • Understand what GeoInd means: • If you want average protection, use something else! • If you really want GeoInd, re- design queries, use bandwidth as a resource, etc. Thank you!! simonoya@gts.uvigo.es 10

Recommend

More recommend