Building trusted path on untrusted device drivers for mobile devices
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Mobile devices are frequently used as terminals to interact with many security-critical services such as mobile payment and online banking. However, the large client software stack and the continuous proliferation of malware expose such interaction under various threats, including passive attacks like phishing and active ones like direct code manipulation. This paper proposes TrustUI, a new trusted path design for mobile devices that enables secure interaction between end users and services based on ARM's TrustZone technology. TrustUI is built with a combination of key techniques including cooperative randomization of the trusted path and secure delegation of network interaction. With such techniques, TrustUI not only requires no trust of the commodity software stack, but also takes a step further by excluding drivers for user-interacting devices like touch screen from its trusted computing base (TCB). Hence, TrustUI has a much smaller TCB, requires no access to device driver code, and may easily adapt to many devices. A prototype of TrustUI has been implemented on a Samsung Exynos 4412 board and evaluation shows that TrustUI provides strong protection of users interaction.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Using ARM trustzone to build a trusted language runtime for mobile applications
Santos, N., Raj, H., Saroiu, S., & Wolman, A. (2014) · Proceedings of the 19th international conference on Architectural support for programming languages and operating systems · doi:10.1145/2541940.2541949 · Cited by 192 · cited 3×
“Instead, TLR envisions future hardware feature to achieve the same goal of TrustUI.”
Background
Cited by
Trusted Execution Environment: What It is, and What It is Not
Sabt, M., Achemlal, M., & Bouabdallah, A. (2015) · 2015 IEEE Trustcom/BigDataSE/ISPA · doi:10.1109/trustcom.2015.357 · Cited by 724
Demystifying Arm TrustZone: A Comprehensive Survey
Pinto, S., & Santos, N. (2019) · ACM Computing Surveys · doi:10.1145/3291047 · Cited by 505
SoK: Understanding the Prevailing Security Vulnerabilities in TrustZone-assisted TEE Systems
Cerdeira, D., Santos, N., Fonseca, P., & Pinto, S. (2020) · 2020 IEEE Symposium on Security and Privacy (SP) · doi:10.1109/sp40000.2020.00061 · Cited by 208
“There is also a body of work in trusted I/O path primitives [82, 83] which aims at providing secure access to peripherals.”
BackgroundSGXIO: Generic Trusted I/O Path for Intel SGX
Weiser, S., & Werner, M. (2017) · Proceedings of the Seventh ACM on Conference on Data and Application Security and Privacy · doi:10.1145/3029806.3029822 · Cited by 79
Li, W., Xia, Y., & Chen, H. (2019) · GetMobile: Mobile Computing and Communications · doi:10.1145/3308755.3308761 · Cited by 33
Self-citation
Metadata
- Authors
- Li, W., Ma, M., Han, J., Xia, Y., Zang, B., Chu, C.-K., & Li, T.
- Venue
- Proceedings of 5th Asia-Pacific Workshop on Systems
- Publisher
- ACM
- Published
- 2014-06-25
- Pages
- 1-7
- OpenAlex
- W2136566423
- Cited by
- 75
- References
- 1
- FWCI
- 4.15
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.