PINPOINT: Efficient and Effective Resource Isolation for Mobile Security and Privacy
January 23, 2019 Β· Declared Dead Β· π arXiv.org
"No code URL or promise found in abstract"
Evidence collected by the PWNC Scanner
Authors
Paul Ratazzi, Ashok Bommisetti, Nian Ji, Wenliang Du
arXiv ID
1901.07732
Category
cs.OS: Operating Systems
Cross-listed
cs.CR
Citations
9
Venue
arXiv.org
Last Checked
1 month ago
Abstract
Virtualization is frequently used to isolate untrusted processes and control their access to sensitive resources. However, isolation usually carries a price in terms of less resource sharing and reduced inter-process communication. In an open architecture such as Android, this price and its impact on performance, usability, and transparency must be carefully considered. Although previous efforts in developing general-purpose isolation solutions have shown that some of these negative side effects can be mitigated, doing so involves overcoming significant design challenges by incorporating numerous additional platform complexities not directly related to improved security. Thus, the general purpose solutions become inefficient and burdensome if the end-user has only specific security goals. In this paper, we present PINPOINT, a resource isolation strategy that forgoes general-purpose solutions in favor of a "building block" approach that addresses specific end-user security goals. PINPOINT embodies the concept of Linux Namespace lightweight isolation, but does so in the Android Framework by guiding the security designer towards isolation points that are contextually close to the resource(s) that need to be isolated. This strategy allows the rest of the Framework to function fully as intended, transparently. We demonstrate our strategy with a case study on Android System Services, and show four applications of PINPOINTed system services functioning with unmodified market apps. Our evaluation results show that practical security and privacy advantages can be gained using our approach, without inducing the problematic side-effects that other general-purpose designs must address.
Community Contributions
Found the code? Know the venue? Think something is wrong? Let us know!
π Similar Papers
In the same crypt β Operating Systems
R.I.P.
π»
Ghosted
R.I.P.
π»
Ghosted
Occlum: Secure and Efficient Multitasking Inside a Single Enclave of Intel SGX
R.I.P.
π»
Ghosted
LazyFP: Leaking FPU Register State using Microarchitectural Side-Channels
R.I.P.
π»
Ghosted
SGX-LKL: Securing the Host OS Interface for Trusted Execution
R.I.P.
π»
Ghosted
Optimal Virtual Cluster-based Multiprocessor Scheduling
R.I.P.
π»
Ghosted
Ecovisor: A Virtual Energy System for Carbon-Efficient Applications
Died the same way β π» Ghosted
R.I.P.
π»
Ghosted
Language Models are Few-Shot Learners
R.I.P.
π»
Ghosted
PyTorch: An Imperative Style, High-Performance Deep Learning Library
R.I.P.
π»
Ghosted
XGBoost: A Scalable Tree Boosting System
R.I.P.
π»
Ghosted