"Mobile Wanderlust"! Our Journey To Version 2.0!
summary
Project announces MAS v2.0 with concrete changes: storage drops from ~15 controls to 2, storage now splits “securely stores sensitive data” and “leakage” with dozens of atomic tests possible; testing guide refactors long test cases into atomic test cases for automation and CI pipelines for runnable snippets; profiles replace L1/L2 and become machine‑readable profiles so tools can trace tests; Google Play uses a MASVS subset via App Defense Alliance and authorized labs for a badge.
AI-written summary · about
chapters (9)
- 0:00Mobile App Security intro
- 3:11MAS project overview
- 10:32Refactoring MASVS v2.0
- 18:36Storage & crypto updates
- 20:24Authentication changes
- 22:34MSTG test cases
- 25:06Compliance profiles
- 31:07Next steps & contribution
- 32:53Q&A
related talks
46m“Mobile Wanderlust”! Our Journey to Version 2 0!
28mOWASP Mobile Application Security (MAS)
20mMobile Application Security (MAS)
21mSecuring Mobile Apps with OWASP MASVS & MSTG
30mTopics of Interest: Creating an IoT-connected Mobile App Compliance Program... MASVS
44mHow the latest MASVS & MSTG Specs Make the Best Mobile Pen Testing Cocktails
29mFixing Mobile AppSec
29mInsiders Guide to Mobile AppSec with Latest OWASP MASVS
