Mobile Application Security (MAS)
summary
The project refactors the massive MDG into modular tests, techniques, tools and apps and introduces mobile-specific weaknesses called MASWE that map to MSVS and CWEs. Tests v2 come with runnable demos and sample Android/iOS apps, pipelines auto‑build APK/IPA via GitHub Actions, run static and dynamic checks, and compare outputs to expected results. Dynamic tooling includes Frida/Freda traces, and the goal is reproducible, versioned, automatable validations across platforms.
AI-written summary · about
chapters (18)
- 0:00Mobile Application Security intro
- 1:05Refactoring MAS guide
- 2:30MAS weaknesses overview
- 3:32Defining MAS weaknesses
- 5:01MAS weaknesses structure
- 6:27Goals for demos
- 7:34Automated testing with apps
- 9:20Exploring MAS beta guide
- 10:45Test structure guide
- 11:48Benefits of standardized tests
- 12:55Demo: insecure random generation
- 13:16Demo: sensitive data exposure
- 13:59Demo: insecure logging
- 15:26Clarifying MAS weaknesses
- 16:47MAS weaknesses to CWEs
- 17:30Automation in MAS pipelines
- 18:13Version tracking updates
- 19:17Summary and contribution
related talks
28mOWASP Mobile Application Security (MAS)
29mFixing Mobile AppSec
21mSecuring Mobile Apps with OWASP MASVS & MSTG
45mFast Forwarding Mobile Security With The OWASP Mobile Security Testing Guide
29mInsiders Guide to Mobile AppSec with Latest OWASP MASVS
19mFlagship Projects: Mobile Security Testing Guide
44mHow the latest MASVS & MSTG Specs Make the Best Mobile Pen Testing Cocktails
30mTopics of Interest: Creating an IoT-connected Mobile App Compliance Program... MASVS