AWare: Preventing Abuse of Privacy-Sensitive Sensors via Operation Bindings
summary
AWare implements operation bindings in Android middleware to tie camera, microphone and other sensor requests to the exact user input and window configuration, preventing stealthy background captures. The system is built as an Android extension, adds a small memory footprint (~3 MB) and minimal latency, and is evaluated in a lab study (tricked users drop from ~85% to 7%), a field study (average +2.28 authorization prompts per app) and a 1,000‑app compatibility run.
AI-written summary · about
chapters (10)
- 0:00Privacy-sensitive sensor abuse
- 2:23Current permission limits
- 4:55User-driven access challenges
- 8:54Operation bindings to prevent abuse
- 13:37Design goals for AWare
- 16:56Implementation and OS compatibility
- 19:29Effectiveness and performance evaluation
- 22:46Results and UI attack prevention
- 23:52Performance overhead and memory
- 25:33Cross-platform support and future
related talks
19mProtecting Your Users in an Agentic World
36mRevisiting Stealthy Sensitive Information Collection from Android Apps
25mSimple Spyware: Android's Invisible Foreground Services and How to (Ab)use Them
37mHey, You, Get off My Private Data: Do Apps Respect Your Privacy as They Claim?
28mEmbracing innovation by building privacy friendly apps
20mChameleon Devices: Investigating More Secure and Discreet Mobile Interactions via Active ...
35mLow Level Sensor Programing and Security Enforcement with MRAA
13mFoster user trust by adopting privacy-respecting permission workflows