Mobile App Security: Using the OWASP Mobile Top 10 and MASVS as a Checklist
Mobile apps store data and credentials on devices that can be lost or torn apart. The OWASP Mobile Top 10 and MASVS help teams map out the risks systematically.
This article was translated from Bahasa Indonesia with AI assistance and reviewed by our team.

Mobile apps run on devices we do not fully control: phones can be lost, rooted or infected with malicious apps, and anyone can take an app's files apart. For this reason, mobile app security needs to be designed in from the start, not patched on shortly before release.
OWASP provides two complementary references: the Mobile Top 10 for understanding the most common risks, and MASVS as a more detailed verification standard.
OWASP Mobile Top 10 (2024)
The final 2024 edition lists the following ten risks:
- M1 — Improper Credential Usage: credentials or API keys are embedded in code or stored carelessly.
- M2 — Inadequate Supply Chain Security: third-party libraries, SDKs or the build process are not properly secured.
- M3 — Insecure Authentication/Authorization: weak authentication, or access rights checked only on the app side.
- M4 — Insufficient Input/Output Validation: incoming and outgoing data is not validated.
- M5 — Insecure Communication: communication without encryption, or with weak certificate validation.
- M6 — Inadequate Privacy Controls: personal data is collected, stored or shared beyond what is needed.
- M7 — Insufficient Binary Protections: the app is easy to take apart or modify.
- M8 — Security Misconfiguration: insecure default configurations, for example components that are exposed to other apps.
- M9 — Insecure Data Storage: sensitive data is stored on the device without protection.
- M10 — Insufficient Cryptography: weak algorithms or incorrect key management.
MASVS: a measurable verification standard
The Mobile Application Security Verification Standard (MASVS) groups security controls into eight areas:
- MASVS-STORAGE — data storage
- MASVS-CRYPTO — cryptography
- MASVS-AUTH — authentication and authorisation
- MASVS-NETWORK — network communication
- MASVS-PLATFORM — interaction with the platform
- MASVS-CODE — code quality
- MASVS-RESILIENCE — resilience against reverse engineering and modification
- MASVS-PRIVACY — privacy
Where the Top 10 answers "which risks occur most often", MASVS answers "which controls must be in place and how to test them". Together with its testing guide, MASVS is well suited as acceptance criteria in a development contract or as a basis for penetration testing.
Do not forget platform updates
Security also depends on how up to date an app is with the platform. From 31 August 2026, Google Play requires new apps and app updates to target Android 16 (API level 36) or higher. Existing apps that still target Android 14 (API level 34) or lower will only be available to new users on devices running the same or an older Android version. Each Android version brings security and privacy improvements, some of which apply only when the app targets the latest API.
A starter checklist for teams
- Do not embed secret keys in the app; use short-lived tokens from the server.
- Perform all access-rights checks on the server, not only in the app.
- Store sensitive data using the platform's built-in encrypted storage (Keystore/Keychain), and store as little as possible.
- Enforce HTTPS and validate certificates correctly.
- Inventory and update third-party SDKs regularly.
- Plan for target API level updates every year in the maintenance budget.
- Run MASVS-based security testing before major releases.
For app owners, these two references are also useful for putting the right questions to a vendor: not just "is the app secure?", but "which MASVS controls have been verified, and how?"
Sources & references
This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.
