Security in Android Applications
summary
Shows that 75% of apps had critical vulnerabilities (HPE 2015) and explains Android’s real attack surface: Linux UID isolation, separate processes and ART/Dalvik copy‑on‑write, plus how preinstalled/rooted malware can patch system libs at boot. Gives concrete fixes: avoid external storage, use Android Keystore or SQLCipher for secrets, enforce HTTPS with Diffie‑Hellman and certificate pinning, mark exported components/intent filters explicitly, run ProGuard, and push high‑value logic into native code where appropriate.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:29Android security model
- 11:07Real-world security issues
- 13:55App vulnerabilities
- 20:21Data storage and encryption
- 25:40Network security
- 30:17Anti-reverse engineering
- 33:04Security vs usability
- 37:15Summary
related talks
34mDemystifying Android Security
56mThe Android Security Jungle: Pitfalls, Threats & Survival Tips
29mSecuring Android Applications - The not so se…
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
29mSecuring Android: Tackling Advanced Threats and Enhancing App Security
24mModern Android App Security: Protecting Code, Keys, and Data
47mSecuring Android Applications, The Right Way
21mSecuring the Unseen: Advanced Threats, Best Practices & Challenges in Mobile App Security