Aurasium: Practical Policy Enforcement for Android Applications

By Rubin Xu, Hassen Saïdi, Ross J. Anderson. USENIX Security Symposium, 2012

477 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/fff4d5caf5fed010576f81745ab57c049a144f7d

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

CopperDroid: Automatic Reconstruction of Android Malware Behaviors (2015, methodology): “Although recently explored to enforce user-authorized security policies [42], to the best of our knowledge, CopperDroid is the first approach to carry out a detailed analysis of such communication channels to comprehensively characterize OS- and Android-specific behaviors of malicious applications.”
Android Security: A Survey of Issues, Malware Penetration, and Defenses (2015, background): “Aurasium [125] is a powerful technique that takes control of execution of apps, by enforcing arbitrary runtime security policies.”
PScout: analyzing the Android permission specification (2012, background): “Saint [29], Apex [27] and Aurasium [35] are three systems proposed to provide runtime policy enforcement to complement existing permission systems.”
ContexloT: Towards Providing Contextual Integrity to Appified IoT Platforms (2017, background): “Moreover, ContexIoT allows user control in cases where a particular data flow might be allowed in one scenario, but should be blocked in another.”
The Evolution of Android Malware and Android Analysis Techniques (2017, background): “…or clustering frameworks [Zhang et al. 2014; Schmidt et al. 2009a; Zhou and Jiang 2012b; Grace et al. 2012; Rasthofer et al. 2014], policy frameworks [Ongtang et al. 2009; Distefano et al. 2010; Dietz et al. 2011; Xu et al. 2012; Davis et al. 2012; Backes et al. 2013], and malware detectors.”
TaintDroid (2010, background): “Aurasium [Xu et al. 2012] and RetroSkeleton [Davis and Chen 2013] seek similar semantics by rewriting applications to include inline reference monitors.”
IccTA: Detecting Inter-Component Privacy Leaks in Android Apps (2015, unknown): “Aurasium: practical policy enforcement for android applications.”
Amandroid: A Precise and General Inter-component Data Flow Analysis Framework for Security Vetting of Android Apps (2014, background): “Multiple prior works [9, 26, 35] investigated the root security problems in the Android system and proposed augmented infrastructures to enforce the given security policy.”
FlowDroid: precise context, flow, field, object-sensitive and lifecycle-aware taint analysis for Android apps (2014, background): “Aurasium [38] and DroidScope [39] largely suffer from the same shortcomings with respect to static leak detection.”
A Machine-learning Approach for Classifying and Categorizing Android Sources and Sinks (2014, methodology): “Aurasium [15] shifts the problem of identifying sources and sinks by intercepting calls at the system level, i.”