What OWASP MASVS is
OWASP, the open foundation that serves as a reference for application security, runs a project dedicated to mobile apps called MAS (Mobile Application Security). It has three pieces worth telling apart:
- MASVS, the verification standard: it says what a secure app must achieve, organized into categories and controls.
- MASTG, the testing guide: it explains how to check each control.
- MASWE, the weakness catalog: it describes what can go wrong and links each weakness to its controls and tests.
For a team that builds apps, MASVS is useful mainly for two reasons: it provides a common language for talking with auditors, customers and regulators, and it separates what every app must address from what only some apps need. That separation is exactly what makes the resilience category special.
The latest published version of MASVS is v2.1.0, from January 18, 2024. The text of its resilience category was updated in 2025 and now explicitly mentions runtime application self-protection (RASP). If you see references to other versions or to older identifiers, such as those from version 1, check that they match the current structure.
Resilience is not mandatory
MASVS-RESILIENCE is a special category. Unlike the storage, cryptography or network categories, its controls are not a requirement for every app. The standard says so itself: the absence of these measures does not, by itself, constitute a vulnerability, and an app that implements them must still meet the rest of MASVS.
So when do they apply? When your threat model includes someone who has your app in their hands and wants to study or manipulate it. OWASP sums this up in its testing profiles: the MAS-R profile is meant for apps where “the user of the device is an attacker”, including reverse engineers and cheaters.
A banking app, a health app with sensitive data, a game with its own economy or a loyalty app that gives away points all fit that profile. A personal note-taking app probably does not. Either way, the decision is yours, and it is worth writing down: an auditor will ask why you applied the profile, or why you did not.
The four controls
MASVS-RESILIENCE has four controls. We quote them as OWASP publishes them and explain what they mean in practice.
MASVS-RESILIENCE-1
“The app validates the integrity of the platform.”
The app checks that the operating system it runs on can be trusted. In practice: detecting root on Android, jailbreak on iOS, emulators and other altered environments, and relying on platform attestation.
Think about someone who wants to study your app: they almost always start with a rooted or jailbroken phone or with an emulator, because that is where they get the control they need. This control is the first line.
MASVS-RESILIENCE-2
“The app implements anti-tampering mechanisms.”
The app detects whether someone has modified it. That includes verifying the signature, checking that data and code have not been altered and detecting changes while the app runs, such as memory patches or injected code.
It is the control that stops re-signed copies that skip a payment, unlock features or pose as your app.
MASVS-RESILIENCE-3
“The app implements anti-static analysis mechanisms.”
The app makes it harder for someone to understand its code by analyzing it without running it. This is the territory of obfuscation: renaming symbols, transforming the code and not leaving clues in logs or debug symbols.
MASVS-RESILIENCE-4
“The app implements anti-dynamic analysis techniques.”
The app makes it harder for someone to study it while it runs. In practice: detecting debuggers, instrumentation tools and hooking, and responding to them.
It is probably the most relevant control today: instrumentation lets someone change an app’s behavior without touching its package, which is why static protections do not see it.
How they are tested
The MASTG testing guide released version 2.0.0 on June 30, 2026, the first stable release of its new structure. In it, tests are organized around MASWE weaknesses, and each one is linked to a MASVS control.
Without going into the procedures, which are best read at the source, the test groups for each control are:
- RESILIENCE-1: root and jailbreak detection, and detection of emulators and virtual devices.
- RESILIENCE-2: signature verification, storage integrity and detection of runtime hooking.
- RESILIENCE-3: code obfuscation and the absence of symbols and logs that make analysis easier.
- RESILIENCE-4: debugging detection.
One important detail for auditors: a passing test shows that the mechanism exists and works under the conditions of the test. It does not show that it is impossible to bypass, because that depends on each attacker’s time and resources.
Pulse coverage map
This mapping identifies Pulse capabilities that can contribute to assessment of each control. It is not a certification and does not by itself establish that the application meets the standard.
| Control | Pulse contribution | Related capability |
|---|---|---|
| RESILIENCE-1 | Support | Root, jailbreak and emulator detection; attestation with each platform’s official services |
| RESILIENCE-2 | Support | Detection of modified or off-store copies, and of changes to the app while it runs |
| RESILIENCE-3 | No | It is obfuscation: pair Pulse with an obfuscation tool |
| RESILIENCE-4 | Support | Detection of debuggers, hooking and instrumentation |
| PLATFORM-3 | Partial | Screen recording signals; overlays and disallowed accessibility services on Android |
A few notes on the map:
- RESILIENCE-2 at runtime. Part of the detection of changes while the app runs is specific to Android.
- Attestation in RESILIENCE-1. OWASP associates it with this control, but its scope is worth remembering: on iOS it proves that your app is talking, not the state of the system. That is why it is combined with on-device detection.
- PLATFORM-3 belongs to another MASVS category, the one about platform interaction, and asks that the app use the user interface securely. Pulse provides signals that help cover it, but it does not cover all of it.
- RESILIENCE-3. Pulse does not obfuscate code. If your threat model includes static analysis, you need an obfuscation tool in addition to Pulse. We explain this in RASP vs. obfuscation.
Review the scope of each category on the pages for root, jailbreak, hooking and instrumentation, tampered apps and emulators.
How to use the map in an audit
If your organization assesses its apps against MASVS, or if a customer or regulator asks you for evidence, these steps help:
- Decide whether the MAS-R profile applies. Document why your app needs resilience: what it protects and who might want to attack it.
- Assign each control to a tool. Use the map above for RESILIENCE-1, -2 and -4, and assign RESILIENCE-3 to your obfuscation tool.
- Configure the responses. Decide in advance what the app does in each case: record, alert or close. A detection without a defined response leaves the decision for the worst possible moment.
- Keep the evidence. Retain test results and received reports. The absence of reports does not establish absence of threats or complete coverage.
- Review with every release. Both MASVS and MASTG evolve; what covers a control today may change.
Remember that resilience complements the other MASVS categories rather than replacing them. An app with good resilience and poor data storage is still an insecure app.
Common mistakes when citing MASVS
When reviewing vendor and audit documentation, the same mistakes come up again and again. They are worth avoiding:
- Citing versions that do not exist. The latest published version of MASVS is v2.1.0. If a document cites another one, ask for the link.
- Mixing identifiers from different generations. The identifiers from version 1 of the standard and its old testing guide do not map one-to-one to those in version 2.
- Presenting resilience as mandatory. It is not. An app lacking these measures does not, by that fact alone, have a vulnerability.
- Talking about certification. MASVS is a verification standard, not a seal. A tool can help cover controls; verification is done on your specific app.
Sources
- Published MASVS releases: github.com/OWASP/masvs/releases
- MASVS-RESILIENCE: mas.owasp.org/MASVS/11-MASVS-RESILIENCE/
- Controls: RESILIENCE-1, RESILIENCE-2, RESILIENCE-3, RESILIENCE-4
- MASTG v2.0.0: github.com/OWASP/mastg/releases/tag/v2.0.0
- MASTG tests: mas.owasp.org/MASTG/tests/
- MAS testing profiles: mas.owasp.org/Profiles/