App Defense Alliance MASA AL2

Android apps

MASA AL2 Security Assessment for Android Apps

Get your Android application independently tested and validated against MASA Assurance Level 2 requirements through a structured, lab-led security assessment — $2,999 per app, with two retests included.

Backed byan accredited security firm.
AccreditationCREST-accredited
AssessmentPCI QSA
PlatformAndroid applications
Governing bodyApp Defense Alliance (ADA)
Assessment approachHigher-assurance, lab-led testing
Retest2 included per application
ValidationLab-validated MASA requirements

The definition

What is MASA AL2?

MASA (Mobile Application Security Assessment) is a security assessment framework defined by the App Defense Alliance, built on established OWASP mobile application security standards. MASA Assurance Level 2 (AL2) provides a higher level of assurance than AL1 through greater lab-led security testing and independent validation of applicable MASA requirements by an authorized lab, covering data storage, cryptography, authentication, network communication, Android platform interaction, and application security configuration.
  • Platform

    Android applications

  • Governing body

    App Defense Alliance (ADA)

  • Assessment approach

    Higher-assurance, lab-led testing

  • Retest

    2 included per application

Plan your assessment

Choose the right MASA AL2 plan

Tell us how many Android apps you need assessed. We'll suggest a plan, explain why it fits, and show every option.

MASA AL2 plan finder

Find your MASA AL2 plan

Your recommendation and all prices appear at the end.

About 20 seconds

Step 1 of 2

How many Android apps need a MASA AL2 assessment?

Each distinct Android application is one assessment. iOS apps are outside this service.

What does the MASA AL2 assessment cover?

Your Android application is tested against the applicable MASA AL2 security requirements.

  • Data storage & privacy

    How the application stores, processes, and exposes sensitive information — covering applicable controls relating to sensitive information, credentials, cryptographic material, application logs, and other protected data.

  • Cryptography

    Applicable cryptographic controls, including weak algorithms, insecure cryptographic implementation, and inappropriate handling of cryptographic keys.

  • Authentication & session management

    Where applicable, authentication mechanisms, credential handling, and session-management controls.

  • Network communications

    Security of communications between the Android application and remote services, including applicable TLS and certificate-validation controls.

  • Android platform interaction

    How the application interacts with the Android platform, including applicable permissions, exported components, external inputs, and inter-process communication.

  • Code quality & application configuration

    Applicable application security configuration, release settings, debugging functionality, and security-relevant implementation characteristics.

How the MASA AL2 assessment works

A structured digital process from purchase to completed validation.

  1. Step 1Day 1

    Purchase your assessment

    Need MASA AL2 for one or two Android applications? Purchase directly online for $2,999 per application. For three or more applications, request pricing.

  2. Step 2After purchase

    Complete digital onboarding

    Access Secusy and provide what the assessment needs — Google Play details, the application package or build, test credentials, functionality information, supporting evidence, testing instructions, and assessment authorization.

  3. Step 3In progress

    We perform the AL2 security assessment

    Our security team performs the applicable MASA AL2 testing, combining appropriate security testing techniques with analyst-led validation. Unlike AL1's streamlined approach, AL2 requires greater lab involvement in testing and validating the application's security controls.

  4. Step 4On completion

    Receive your findings

    If the application does not satisfy an applicable requirement, you receive findings explaining what needs to be addressed so your development team can remediate the issues.

  5. Step 5After findings

    Remediate the issues

    Your development team fixes the identified security issues and provides the updated application or supporting evidence. Development and remediation are not included in the standard assessment.

  6. Step 6Final

    Retest & complete AL2 validation

    We retest the applicable failed requirements — two remediation retests per application are included. Once the application satisfies the applicable requirements, we complete the MASA AL2 validation process.

Included

What you get

Standard assessment includes

  • MASA AL2 assessment for one Android application
  • Automated application security analysis
  • Lab-led security testing
  • Validation against applicable MASA requirements
  • Supporting evidence review
  • Security findings report
  • Remediation guidance
  • Two remediation retests
  • Final assessment review
  • Letter of Validation following successful completion

Scope boundaries

What's not included

If you need broader security assurance, consider a Mobile Application Penetration Test in addition to MASA.

  • Application development
  • Vulnerability remediation
  • Source-code modification
  • Secure coding implementation
  • Unlimited security consulting
  • Unlimited retesting
  • Testing outside the applicable MASA scope
  • Additional applications not purchased as part of the engagement
  • Full mobile application penetration testing outside the MASA scope

Intake

Before you start

To begin the assessment efficiently, be ready to provide the information and access required to test your application. Incomplete information, inaccessible application functionality, or invalid credentials may delay the assessment.

You will normally provide

  1. Access to the Android application
  2. Required application/build information
  3. Valid test credentials
  4. Information about application functionality
  5. Supporting evidence
  6. Required assessment authorization
  7. A technical contact who can respond to assessment questions
  8. An updated application build, if remediation is required

Questions

Frequently asked questions