2013 IEEE International Conference on Communications (ICC) 2013
DOI: 10.1109/icc.2013.6654845
|View full text |Cite
|
Sign up to set email alerts
|

SanAdBox: Sandboxing third party advertising libraries in a mobile application

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(5 citation statements)
references
References 6 publications
0
5
0
Order By: Relevance
“…e TPLs can no longer share the permissions of the host application and thus can only access limited system resources or user data [10][11][12][13][14][15]. For example, CompARTist [13] splits Android applications at compile-time into isolated, privilege-separated compartments for the host app and the included TPLs.…”
Section: Introductionmentioning
confidence: 99%
“…e TPLs can no longer share the permissions of the host application and thus can only access limited system resources or user data [10][11][12][13][14][15]. For example, CompARTist [13] splits Android applications at compile-time into isolated, privilege-separated compartments for the host app and the included TPLs.…”
Section: Introductionmentioning
confidence: 99%
“…TPLs can access the system resources via two ways: (1) directly invoke the system calls to get the system services or resources; (2) indirectly access the resource through the interfaces from the host app logic. [58] 2016 NDSS LibCage [79] 2016 ESORICS PEDAL [16] 2015 MobiSys NativeGuard [95] 2015 Wisec COMPAC [93] 2014 CODASPY AFrame [15] 2013 ACSAC SanAdBox [14] 2013 ICC AdDroid [18] 2012 ASIACCS AdSplit [17] 2012 USNIX Security…”
Section: Existing Solutionsmentioning
confidence: 99%
“…SanAdBox [14] is a privilege separation framework that can separate the advertising libraries from the host app and run the advertising libraries as different independent applications. In addition, SanAdBox is an updating sandbox where the host app and ad libraries run into and only can invoke their own permissions.…”
Section: Existing Researchmentioning
confidence: 99%
See 1 more Smart Citation
“…Wang et al [177] proposed adding purposes to permissions requests to inform users what their data will be used for, while Agarwal et al [178] used crowdsourcing to help users determine which permissions were really necessary for a given application. Another suggested approach aims to help users by splitting permissions needed for the core application and any third-party libraries that these applications may include [179][180][181][182], thus reducing any confusion as to which parties will be accessing the data.…”
Section: A More Private Futurementioning
confidence: 99%