06

Mobile App Security

Assess the real security of your iOS and Android apps aligned with OWASP MASVS.

Mobile apps store credentials, tokens and sensitive data on the user's device. We perform static and dynamic analysis of iOS and Android apps (native and hybrid) following OWASP MASVS and MSTG, validating cryptography, local storage, communications and resistance to reverse engineering.

95%

of mobile apps fail at least one OWASP MASVS control

NowSecure Mobile Risk Benchmark 2024

84%

of apps exhibit weaknesses from third-party SDKs/frameworks

NowSecure Mobile App Risk 2025

15%

of apps ship third-party components with known CVEs (MASVS-CODE-3)

NowSecure Mobile App Risk 2025

Reference framework

OWASP MASVS v2.1

We validate against the eight domains of OWASP MASVS (Mobile Application Security Verification Standard), applying level L1 (baseline) or L2 (defense in depth) according to the app's criticality.

MASVS-STORAGE

Secure Storage

Keychain/Keystore, avoid sensitive logs, don't expose data in backups, protect shared files.

MASVS-CRYPTO

Cryptography

Modern algorithms, secure key management, don't roll your own primitives, proper randomness.

MASVS-AUTH

Authentication & Authorization

Secure session handling, biometrics, MFA, server-side validation of all authorization.

MASVS-NETWORK

Secure Communication

TLS 1.2+, certificate pinning, chain validation, reject invalid certificates.

MASVS-PLATFORM

Platform Interaction

Secure WebViews, controlled IPC, validated deep links, safe handling of intents and schemes.

MASVS-CODE

Code Quality

Compiler with security flags, up-to-date libraries, exception handling, no debug enabled.

MASVS-RESILIENCE

Reverse-Engineering Resilience

Anti-debug, anti-tampering, root/jailbreak detection, obfuscation proportional to risk.

MASVS-PRIVACY

Privacy

Data minimization, explicit consent, tracking transparency, GDPR/Habeas Data compliance.

What we evaluate

  • Static analysis of iOS (.ipa) and Android (.apk/.aab) binaries
  • Dynamic analysis on jailbroken / rooted devices
  • Local storage assessment (Keychain, Keystore, SQLite)
  • Cryptography and certificate pinning review
  • Reverse-engineering resistance assessment
  • Backend and API communication analysis

Methodology

  1. 1Instrumentation with Frida and Objection
  2. 2MASVS level 1 and level 2 testing
  3. 3Review of permissions and exposed components
  4. 4Traffic analysis with MITM interception
  5. 5Jailbreak and root-detection testing
  6. 6Retesting included at no additional cost

Deliverables

  • Report aligned with OWASP MASVS
  • Exploitation PoC on a real device
  • Severity classification with business context
  • Platform-specific recommendations
  • Review of critical native code (Java / Kotlin / Swift / ObjC)

Frequently asked questions

What is assessed in a mobile application penetration test?

The binary and its resistance to reverse engineering, local storage of sensitive data, backend communication, session and credential handling, and device integrity controls. We use OWASP MASVS as the reference framework.

Do you test both iOS and Android?

Yes, both platforms. Each has its own permission model, storage and platform protections, so findings are rarely identical even for the same app.

What is a MITM attack and why does it matter on mobile?

A man-in-the-middle attack intercepts traffic between the app and the server. It is critical on mobile because many applications do not implement certificate pinning correctly, allowing data to be read or altered on hostile networks such as public wifi.

Does the app need to be published in the store?

No. We can work with a pre-production build or the APK/IPA file directly, which lets you fix issues before release.

Request an assessment

Schedule a free consultation and receive an external cybersecurity assessment with no commitment.

Schedule Free Assessment

Other services

Need help with your cybersecurity? 💬