Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Knowledge hub / OWASP MASVS

Knowledge hub

OWASP MASVS

A standard listing what a secure mobile app should do.

Illustration explaining OWASP MASVS

What it means

The OWASP Mobile Application Security Verification Standard, or MASVS, is a list of security requirements for iOS and Android apps. It is part of OWASP's Mobile Application Security project, which also publishes a testing guide (MASTG) that explains how to check each requirement.

Version 2 groups the requirements into areas: storage, cryptography, authentication, network communication, platform interaction, code quality, resilience and privacy. Each area has a few short control statements, such as that the app handles sensitive data securely on the device. The project also publishes a checklist you can fill in for each app.

Why it matters

It gives your team and your testers a common checklist, so a mobile pentest is measured against something written down. Buyers and regulators increasingly ask whether a mobile app has been assessed against a recognised standard, and MASVS is the usual answer.

It also keeps the scope sensible. Most serious mobile problems are not in the app screen. They sit in the backend the app calls. A mobile pentest against the standard should cover both the device-side controls and the API behind them.

How it shows up

Teams use it at design time to write requirements, at build time as a review list, and at test time as the basis of a report. The MASTG gives test cases, and the project also provides a checklist you can fill in per app.

Be realistic about the resilience group. Controls against reverse engineering and tampering raise the effort for an attacker, but they do not stop a determined one. Spend your first effort on storage, network and authentication, and make sure the server enforces access checks, because anyone can call your API without your app.

Questions people ask

OWASP MASVS, answered

Is MASVS a certification?

No. It is a standard to measure against. A tester can state that an app meets its requirements, but OWASP does not certify apps.

Be wary of anyone selling a MASVS certificate.

What is the difference between MASVS and MASTG?

MASVS says what a secure app should do. The Mobile Application Security Testing Guide says how to check it, with test cases and tools.

Use them together. Teams usually cite both in a report.

How is MASVS different from the OWASP Mobile Top 10?

The Mobile Top 10 is an awareness list of common risks. MASVS is a verification standard with controls you can test against.

One tells you what to worry about, the other what to check. Together they form a testing baseline. Use both on each release. Teams usually cite both in a report.

Does MASVS cover the backend API?

Its network and authentication areas cover how the app talks to the server, but backend logic is mostly tested separately.

A good assessment covers the API as well as the app.

Do small teams need to follow all of it?

Start with storage, network communication and authentication, then work through the rest as the app grows.

Record which controls you chose and why. Use the privacy group too if you hold personal data.

Cyberlop mark

Is the API behind the app sound?

The server behind a mobile app decides who sees what. We test the web apps and APIs your app depends on and prove each finding with the request and the response. Ask us to run it on one of your applications.

Or start with a $199 pilot on one application: thirty days, success criteria agreed before day one, credited against the annual if you convert.