Mobile DevSecOps 5 Tips from Building Mobile Apps Used by Millions
summary
Five case studies show what actually works: Uber (500M Android installs) and McDonald’s use a single codebase with feature flags and automated security gates; Allstate provides on‑demand infra and built‑in testing; Vivid Seats embeds security skills in small teams; a global payments firm runs app‑store pulled tests across regions. Benchmarks report 2.6B devices, 4.5M public apps, 20–30M internal apps, 85% of apps with a security bug and ~50% with insecure data storage (M2) or insecure communication (M3). Pipelines use binary testing and CI/CD like Jenkins -> automated test suite to cover ~70–80% of checks.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:58The World's Mobile App Economy
- 4:01Mobile Security Challenges by the Numbers
- 12:44Establish Mobile Security Training Program
- 13:37Web & Mobile are Fundamentally Different
- 14:50Understand the Mobile Attack Surface
- 16:39Leverage OWASP Mobile Project
- 18:19Automate Mobile Binary AppSec Testing
- 20:07Integrate Automated Mobile Binary AppSec Testing
- 22:06Inject Security Throughout the Toolchain
- 26:52Mature DevOps Teams Automate Compliance
related talks
37mMobile DevSecOps: 5 Tips from Building Mobile Apps Used by Millions
33mBest Practices for Mobile App Security Testing
48mHow to Meet the New Mobile Application Security Imperative
21mUnlocking Mobile App Security- Key Insights for Navigating a Rapidly Evolving Threat Landscape
26mHow to become your app's 'security champion'.
24mModern Android App Security: Protecting Code, Keys, and Data
52mMobile Application Assessments By The Numbers: A Whole-istic View
45mTen Secrets to Secure Mobile Applications