1 / 6

Privacy in Distributed Database Systems

Privacy in Distributed Database Systems. Adam J. Lee , Panos K. Chrysanthis , Nicholas L. Farnan adamlee@ cs.pitt.edu. Distributed Query Processing.

leal
Télécharger la présentation

Privacy in Distributed Database 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 in Distributed Database Systems Adam J. Lee, Panos K. Chrysanthis, Nicholas L. Farnan adamlee@cs.pitt.edu

  2. Distributed Query Processing SELECT * FROM Plants, Supplies, Polluted_WatersWHERE Supplies.type = "solvent", AND Supplies.name = Polluted_Waters.pollutant, AND Polluted_Waters.location = Plants.location, AND Plant.id = Supplies.plant_id; Alice Querier Inventory Facilities Pollution Watch Trusted Untrusted

  3. How Does Optimization Affect Querier Privacy? SELECT * FROM Plants, Supplies, Polluted_WatersWHERE Supplies.type = "solvent", AND Supplies.name = Polluted_Waters.pollutant, AND Polluted_Waters.location = Plants.location, AND Plant.id = Supplies.plant_id; Reveals sensitive information to ManuCo Reveals sensitive information to Pollution Watch Results in a large amount of network traffic Strikes a balance between privacy and performance

  4. SELECT * FROM Plants, Supplies, Polluted_WatersWHERE Supplies.type = "solvent", AND Supplies.name = Polluted_Waters.pollutant, AND Polluted_Waters.location = Plants.location, AND Plant.id = Supplies.plant_id; The 10,000 Mile View… Make sure all operations involving these conditions are evaluated by a trusted server! Empower users to… • Identify sensitive intensional regions within their queries • Specify constraints/preferences over how these regions are handled Enable the system to… • Consider privacy as an optimization criterion • Construct query plans respecting these constraints and preferences

  5. So where are we? PROOFS … Implementation within PostgreSQL

  6. What would you do? 3. Generate constraint/preference data structures needed for optimization 1. Learn flex and bison 2. Develop a parser for extracting privacy constraints from SQL queriers 4. Integrate with our modified version of PostgreSQL

More Related