OWASP MASVS assessment.

Need an OWASP MASVS report for your Android or iOS app? We tell you which controls it meets, which it doesn't and how to fix them.

A customer, partner or insurer may ask for it, or you may choose it yourself to know where your app stands and compare each release.

Unlike a penetration test, we check every applicable control, even when there is no exploitable vulnerability behind it.

OWASP defines testing profiles based on who your app needs to be protected against:

  • MAS-L1, essential security: the recommended baseline for every app. Protects against other apps installed on the same device.
  • MAS-L2, advanced security: for apps that handle highly sensitive data or functions. Also protects when the device is rooted or jailbroken, or a third party may have physical access to it.
  • MAS-R, resilience: for when the attacker is the device's own user, trying to tamper with, analyze or copy the app.
  • MAS-P, privacy: protection of your users' personal data.

Ideally, the choice comes from your app's actual risks. If you are not sure, we look at it with you on the call and recommend the profile or combination that fits.

We use OWASP MASTG tests to check the agreed controls and map each weakness to OWASP MASWE, OWASP's catalogue of mobile security weaknesses. When a test fails, we investigate the weakness and validate its impact. Depending on the profile, testing covers the MASVS control groups:

  • Storage of sensitive data and use of cryptography.
  • Authentication and authorization and secure network communication.
  • Platform interaction and code security.
  • Resilience to reverse engineering and tampering, and user privacy.
  1. Call: you tell us about your app and the requirements you need to meet.
  2. Proposal: we set out the agreed profile and controls, what we need from you, the schedule and a fixed price.
  3. Testing: you send us the builds and we start. If we find something critical, we let you know right away.
  4. Report and review: we send you the report and go through it with your engineers.
  5. Retest: once you have made the fixes, we check on the new build the controls that failed and any that the changes may have affected.

Technical report

The scope and the result for each control of the agreed profile, with the MASVS and MASTG version used, evidence, CVSS scores for vulnerabilities, CWE and OWASP MASWE references, and how to fix each gap.

Executive summary

Covers the profile and build tested, the results and the priorities, for management and non-technical readers.

Retest report

If you include the retest, we send a new version of the report with the status of each control on the new build.

Letter for your customers

On request, at no extra cost, we provide a signed letter with the profile, the version tested, the date and the result, for your customers or auditors. After the retest, we update it with the new results.

Tested by the people who write the standard

Your assessment is carried out by specialists who contribute to the OWASP MAS project: they define security controls, document weaknesses and write tests. OWASP recognized this work by naming vulnit an OWASP MAS Advocate, and the team holds offensive certifications such as OSCP, OSWE and OSED.

We know what an assessor looks for

Our team comes from security certification laboratories, with experience in schemes such as Common Criteria, EMVCo SBMP and LINCE.

Meet the team
Will I be able to say my app meets MAS-L1?

The report states which controls of the agreed profile your app meets, for which version and platform, and you can show it to customers or insurers. On request, we also provide a signed letter with the profile, the version tested, the date and the result, without disclosing the details of the findings. It is not a certification: OWASP does not certify apps. If a control is not met, you fix it and we check it in the retest.

How long does it take and what does it cost?

It depends on how many platforms we test (Android, iOS or both), the profile and controls in scope, and the complexity of your app. We send you a proposal with a fixed price and the schedule. It usually takes one to two weeks per platform, report included. We can usually start the same week you accept the proposal; the start date depends on our team's workload and is stated in the proposal.

How does this differ from a mobile penetration test?

A MASVS assessment evaluates controls against agreed requirements. A mobile application penetration test investigates exploitable vulnerabilities and their impact. If you need both, we can combine them in a single project: the work on one also serves the other.

Does MASVS cover our backend APIs?

No, MASVS focuses on the mobile app. If you also want the backend and APIs tested, we can combine the assessment with a mobile app penetration test.

What do you need from us?

The app builds (APK or AAB for Android, IPA for iOS), test accounts for each role in scope and access to the environment you prefer, whether production or a staging environment. The proposal sets out the details.

Do you need source code?

It is not required. Most MASVS controls can be checked on the compiled app, but it depends on the requirements of the agreed profile: some, such as the one on dependencies with known vulnerabilities, give a more complete result with a dependency list or the source code.

What if a dependency has known vulnerabilities?

MASVS-CODE asks you to use components without known vulnerabilities. When your dependencies flag some, you do not have to update every one: we analyze whether each known vulnerability is actually exploitable in your app (a VEX analysis), so you fix the real risks instead of rebuilding over CVEs that do not reach your code.

Do you test on physical devices?

When needed. On Android we mainly work with Chameleon, our analysis environment: it gives us deep visibility into what the app does in the operating system, and handles root, pinning and anti-instrumentation checks at the OS level by default. If we hit a limitation that matters for your app, we use physical devices. On iOS we use physical devices.

Do you use AI on my app?

Yes, to cover more of your app and go deeper in the same time. We use AI providers that do not train their models on your data. We only use accounts you provide or that we create ourselves, never other real users' accounts. Our specialists lead the work and validate every result. If your policy does not allow external AI, tell us when we agree on the scope and we work without it.

Is retesting included?

Retesting is quoted separately at a reduced rate. In the proposal we give you two options, testing only or testing with one retest round, so you know the total cost from the start.

What format do the findings come in?

You receive one report per platform, with every finding detailed. If you also want to use them in your own tools, we provide them as CSV or JSON too.

What language is the report in?

English by default. If you need it in Spanish, just tell us.

How do you handle confidentiality?

We agree confidentiality terms before you share builds or documentation. We have a standard NDA, but if you prefer to use yours, we are happy to review it.

Can I combine several services in one project?

Yes. They all start from the same analysis of your app. Tell us what you want to know, for example which vulnerabilities it has, whether your protections stop an attacker or which OWASP MASVS controls it meets, and we combine it into a single project.

Tell us about your app and the requirements you need to meet. We reply within one business day to arrange a scoping call.

Talk to our team

A necessary cookie remembers your choices for up to 180 days. Privacy policy.