Show simple item record

dc.contributor.advisorGouda, Mohamed G., 1947-
dc.contributor.advisorShmatikov, Vitaly
dc.contributor.committeeMemberAlvisi, Lorenzo
dc.contributor.committeeMemberWitchel, Emmett
dc.creatorMcPherson, Richard, III Fontaine
dc.date.accessioned2017-02-06T16:10:00Z
dc.date.accessioned2018-01-22T22:31:35Z
dc.date.available2017-02-06T16:10:00Z
dc.date.available2018-01-22T22:31:35Z
dc.date.issued2016-12
dc.date.submittedDecember 2016
dc.identifierdoi:10.15781/T21N7XS1J
dc.identifier.urihttp://hdl.handle.net/2152/45559
dc.description.abstractConventional systems store data unencrypted. This allows them to easily access and manipulate their data. However, by not protecting their data, these systems are at a greater risk if they are compromised by a malicious hacker. More advanced systems add encryption to their data, but this causes other issues. Normal encryption often ruins the ability to run computations on data, negating many of the reasons to store the data in the first place. More recently, some systems have attempted to strike a compromise between security and functionality by using encryption that partially protects their data while still allowing certain operations to be performed. Examples of these systems include general purpose frameworks like Mylar for Web applications, as well as domain- and application-specific systems like P3 for photo storage. This dissertation examines the privacy concerns that arise when using these systems with realistic datasets and real-world usage scenarios. The first system we explore is Mylar, an extension to the popular Meteor framework. Meteor is a JavaScript-based framework for concurrently developing the client and server parts of Web apps. Mylar allows users to share and search over data while protecting against a compromised or malicious server. We expand Mylar's vague definitions of passive and active adversaries into three threat models and show that Mylar is insecure against all three models. Mylar's metadata leaks sensitive information to an adversary with one-time access to Mylar's encrypted database. Mylar provides no protection against adversaries which can monitor user access patterns, allowing them to watch for data dependent behavior corresponding to sensitive information. Finally, Mylar fails to protect against active attackers who, by nature of the system, have been given the ability to modify the database and run search over the encrypted data. We next look at set of systems designed to protect sensitive images by selectively obfuscating them. We examine a system called P3 which splits an image into two images: a secret image that contains most of the identifying information and a public image that can be distributed with less risk of leaking information. We also investigate mosaicing (often called pixelation) and blurring, two commonly used image obfuscation techniques. Examining the obfuscated images, it's obvious that all three of these systems leak information. However, it's not clear how to exploit this leakage or if doing so is even possible. The authors of P3 specifically examined P3 using a number of techniques that mimic human image recognition. We bypass the need for human recognition by making use of modern machine learning techniques. Using neural networks, we are able to classify the obfuscated image content automatically without needing human assistance or having to define image features. Finally, we conclude by proposing a number of guidelines for creating modern privacy-preserving systems. We look at problems that arise when creating a scheme on paper as well as issues that come up when implementing the system. These guidelines were created by examining the mistakes of BoPET and image obfuscation researchers and developers. We present them in the hope that they will be used to insure the effectiveness of future privacy systems.
dc.format.mimetypeapplication/pdf
dc.language.isoen
dc.subjectSecurity
dc.subjectPrivacy
dc.titleExploiting leakage in privacy-protecting systems
dc.typeThesis
dc.description.departmentComputer Sciences
dc.type.materialtext
dc.date.updated2017-02-06T16:10:00Z
dc.creator.orcid0000-0002-6848-2988


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record