Managing your Private and Public Data: Bringing down Inference Attacks against your Privacy
Salman Salamatian, Amy Zhang, Flavio du Pin Calmon, Sandilya, Bhamidipati, Nadia Fawaz, Branislav Kveton, Pedro Oliveira, Nina Taft

TL;DR
This paper introduces a practical framework for protecting private data during public release by minimizing inference attacks through optimized data distortion, addressing real-world challenges like prior knowledge and scalability.
Contribution
It presents a convex optimization-based method for privacy-preserving data release, including bounds on prior mismatch impact, quantization techniques, and empirical validation on real datasets.
Findings
Effective privacy-utility tradeoff achieved with limited distortion
Quantization reduces optimization complexity for large datasets
Correlations between political views and TV habits demonstrated
Abstract
We propose a practical methodology to protect a user's private data, when he wishes to publicly release data that is correlated with his private data, in the hope of getting some utility. Our approach relies on a general statistical inference framework that captures the privacy threat under inference attacks, given utility constraints. Under this framework, data is distorted before it is released, according to a privacy-preserving probabilistic mapping. This mapping is obtained by solving a convex optimization problem, which minimizes information leakage under a distortion constraint. We address practical challenges encountered when applying this theoretical framework to real world data. On one hand, the design of optimal privacy-preserving mechanisms requires knowledge of the prior distribution linking private data and data to be released, which is often unavailable in practice. On the…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
