How to become your app's 'security champion'.
summary
Argues that mobile security matters now—3 billion Android devices, ~$2B stolen in crypto this year, 70% of fraud via mobile—and gives concrete starter steps: run SAST with MobSF and act on high-priority findings, tighten ProGuard/R8 rules using the web ProGuard Playground, decompile APKs with Jadx to check obfuscation, run lunch‑and‑learn sessions, and gamify participation. Cites a company with ~130 champions (≈10% of staff) as proof that a lightweight program gets engineers and non‑security staff doing measurable security tasks.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:32Why developers should care about mobile security
- 8:52What is a security champion?
- 10:20How to become a security champion
- 13:07Setting up a security champion program
- 15:10Quick wins to start your program
- 17:59Lunch and learn ideas
- 22:34Decompiling your app for security checks
- 24:59Resources and closing
related talks
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
24mModern Android App Security: Protecting Code, Keys, and Data
56mThe Android Security Jungle: Pitfalls, Threats & Survival Tips
21mSecuring the Unseen: Advanced Threats, Best Practices & Challenges in Mobile App Security
39mAndroid App Security Fundamentals
21mUnlocking Mobile App Security- Key Insights for Navigating a Rapidly Evolving Threat Landscape
29mSecuring Android: Tackling Advanced Threats and Enhancing App Security
52mPhilosophizing Security In A "Mobile-First" World
