QUIRE: Lightweight Provenance for Smart Phone Operating Systems

QUIRE: Lightweight Provenance for Smart Phone Operating Systems

Cached

Download Links

by Michael Dietz , Shashi Shekhar , Dan S. Wallach , Yuliy Pisetsky , Anhei Shu

Citations:

7 - 0 self

Versions

Version 0

Version History

Metadata Version 0

Datum	Value	Source
TITLE	QUIRE: Lightweight Provenance for Smart Phone Operating Systems	SVM HeaderParse 0.2
AUTHOR NAME	Michael Dietz	SVM HeaderParse 0.2
AUTHOR AFFIL	Rice University	SVM HeaderParse 0.2
AUTHOR NAME	Shashi Shekhar	SVM HeaderParse 0.2
AUTHOR AFFIL	Rice University	SVM HeaderParse 0.2
AUTHOR NAME	Dan S. Wallach	SVM HeaderParse 0.2
AUTHOR AFFIL	Rice University	SVM HeaderParse 0.2
AUTHOR NAME	Yuliy Pisetsky	SVM HeaderParse 0.2
AUTHOR AFFIL	Rice University	SVM HeaderParse 0.2
AUTHOR NAME	Anhei Shu	SVM HeaderParse 0.2
AUTHOR AFFIL	Rice University	SVM HeaderParse 0.2
ABSTRACT	Smartphone apps often run with full privileges to access the network and sensitive local resources, making it difficult for remote systems to have any trust in the provenance of network connections they receive. Even within the phone, different apps with different privileges can communicate with one another, allowing one app to trick another into improperly exercising its privileges (a Confused Deputy attack). In QUIRE, we engineered two new security mechanisms into Android to address these issues. First, we track the call chain of IPCs, allowing an app the choice of operating with the diminished privileges of its callers or to act explicitly on its own behalf. Second, a lightweight signature scheme allows any app to create a signed statement that can be verified anywhere inside the phone. Both of these mechanisms are reflected in network RPCs, allowing remote systems visibility into the state of the phone when an RPC is made. We demonstrate the usefulness of QUIRE with two example applications. We built an advertising service, running distinctly from the app which wants to display ads, which can validate clicks passed to it from its host. We also built a payment service, allowing an app to issue a request which the payment service validates with the user. An app cannot not forge a payment request by directly connecting to the remote server, nor can the local payment service tamper with the request. 1	SVM HeaderParse 0.2
CITATIONS	31 found	ParsCit 1.0