How to Meet the New Mobile Application Security Imperative
summary
Surveys and research report real numbers: 81% leaking sensitive information in one financial-app sample, analysis of over a million apps finds 131,000 apps using public cloud buckets exposing data, and operations discover 5,000 new malware samples in a year. Recommendations are concrete: run static and dynamic tests early and inside CI/CD, gather telemetry on physical devices, protect keys with hardware-backed or robust software KMS, add anti-tamper shielding and runtime detection, and automate response and threat-modeling so mitigations evolve without re-releasing binaries.
AI-written summary · about
chapters (8)
- 0:00Start
- 12:38Mobile Application Security Testing (MAST)
- 13:34MAST Best Practices
- 19:08Cryptographic Key Protection Best Practices
- 21:38Mobile Application Shielding
- 23:17Application Shielding Best Practices
- 25:09Runtime Application Self-Protection (RASP)
- 27:42RASP Best Practices
related talks
21mUnlocking Mobile App Security- Key Insights for Navigating a Rapidly Evolving Threat Landscape
24mModern Android App Security: Protecting Code, Keys, and Data
45mTen Secrets to Secure Mobile Applications
21mSecuring the Unseen: Advanced Threats, Best Practices & Challenges in Mobile App Security
33mBest Practices for Mobile App Security Testing
30mMobile DevSecOps 5 Tips from Building Mobile Apps Used by Millions
25mMobile App Security: Threat Landscape
39mMobile App Security