Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
MASVS states what a secure mobile app must achieve; MASTG explains how to test each requirement. Together they are the reference pair for mobile application assessments.

What Are OWASP MASVS and MASTG?
Ask two consultancies to test the same iOS app and, without a shared standard, you will get two reports with little in common. OWASP’s Mobile Application Security project exists to remove that ambiguity. It publishes two documents that work as a pair: the Mobile Application Security Verification Standard, which states what a secure app must achieve, and the Mobile Application Security Testing Guide, which shows how each requirement is verified in practice.
Both are free, vendor-neutral, and maintained in the open at mas.owasp.org. They are the mobile counterpart to the web-focused OWASP Top 10, with one important difference: the Top 10 is an awareness list, while MASVS is written to be used as a requirements specification.
Version 2.0, published in 2023, restructured the standard around control groups rather than a long flat list. Version 2.1 added a privacy group.
| Group | What it governs |
|---|---|
| MASVS-STORAGE | Where sensitive data is stored, backed up, logged, or cached |
| MASVS-CRYPTO | Algorithm choice, key generation, and key management on device |
| MASVS-AUTH | Authentication, session handling, and biometric binding |
| MASVS-NETWORK | Transport security, certificate validation, and pinning |
| MASVS-PLATFORM | IPC, exported components, deep links, WebViews, and UI exposure |
| MASVS-CODE | Dependencies, build configuration, and platform hardening features |
| MASVS-RESILIENCE | Integrity checks, anti-tampering, and obfuscation |
| MASVS-PRIVACY | Transparency and minimisation of data the app collects |
Scope is set with the MAS profiles. L1 is the baseline that any app handling user data should meet; L2 adds the defence-in-depth expected of banking, payment, and health apps; R covers resilience against reverse engineering and is relevant where the app itself is the target, such as DRM or anti-fraud. The R group is deliberately separate, because obfuscation without the L1 and L2 controls is decoration rather than security.
MASTG is the working manual. It carries identified tests—referenced as MASTG-TEST entries—plus reusable techniques and tool notes for both platforms, and a set of deliberately vulnerable demo apps to practise on. Where MASVS says sensitive data must not be written to logs, MASTG tells the tester to capture logcat or the iOS device console while exercising the flow, and shows what the finding looks like.
Holding the two together is the MAS Checklist, a spreadsheet mapping every MASVS control to the MASTG tests that verify it. That is the artefact most useful in a commercial engagement: it turns an abstract requirement into a list of pass, fail, or not applicable entries that a developer can act on.
Three habits make the difference between citing MASVS and actually using it.
Note what MASVS does not cover. Back-end APIs are out of scope, and they are where a large share of serious mobile findings live—so pair the mobile assessment with API security testing rather than assuming the app standard reaches that far.
No UK regulation names MASVS, but it is a practical way to evidence the “appropriate technical and organisational measures” that UK GDPR Article 32 requires of an app processing personal data, and it maps cleanly onto PCI DSS expectations for payment applications. Financial services firms use it in supplier assurance, and public sector buyers increasingly reference it in tender documents because it is free to read and impossible to fudge.
At Privia Security, our Mobile Application Security Services test iOS and Android apps against MASVS using MASTG procedures, and deliver the completed checklist alongside the report.
MASVS is the standard: a set of security requirements grouped by storage, cryptography, authentication, network, platform, code, resilience, and privacy. MASTG is the testing guide that explains how to verify each requirement on iOS and Android, with techniques, tools, and worked examples. You scope an assessment with MASVS and carry it out using MASTG.
L1 is the sensible baseline for any app handling personal data. L2 adds controls appropriate to banking, payments, healthcare, and government services, where compromise has direct financial or safety consequences. Add the R group only when the app itself must resist reverse engineering, for example where anti-fraud logic or licensed content lives on the device.
No. There is no OWASP body that certifies apps or testers against it, and any claim of MASVS certification should be read carefully. What it provides is a common, public yardstick, so a report can state which controls were verified, by which tests, with what result. Independent assurance comes from the testing organisation, not from OWASP.
Before first release, and after any significant change to authentication, data storage, payment flows, or back-end integration. Many organisations commission a full assessment annually and run automated static and dependency scanning in the build pipeline between those reviews, so routine regressions are caught without waiting for the next engagement.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.