Clear Coverage.
Automatic Mapping.

Every Android and iOS scan maps its findings to the OWASP Mobile Top 10 (2024), the standard list of mobile application security risks. This page shows what is checked in each category, and what is not.

What Is the OWASP Mobile Top 10?

9 of 10 Categories Checked

Android scans check nine of the ten categories and iOS scans check six. M3 is not checked on either platform. Repository scans map to the OWASP Top 10 (2021), shown below.

IDCategoryAndroidiOSHighest Severity
M1Improper Credential Usage✓✓High
M2Inadequate Supply Chain Security✓NoHigh
M3Insecure Authentication/AuthorizationNoNoNot checked
M4Insufficient Input/Output Validation✓NoHigh
M5Insecure Communication✓✓High
M6Inadequate Privacy Controls✓✓High
M7Insufficient Binary Protection✓✓High
M8Security Misconfiguration✓✓High
M9Insecure Data Storage✓✓Medium
M10Insufficient Cryptography✓NoMedium

What Strata Checks in Each Category

Static checks that run on every Android APK and iOS IPA scan. Each item says which platform it applies to.

M1

Hardcoded credentials and API keys left in the app, where anyone who downloads it can extract them.

What Is Checked
  • Pattern matching for known key formats (AWS, Google, Stripe, GitHub, Slack, SendGrid, Twilio and others), JWTs and private key headers
  • Android: the DEX string pool is checked in full (up to 200,000 strings), so bare keys are found, not only strings near a URL or keyword
  • iOS: strings extracted from the app binary are checked against the same key formats
Example Finding
Hardcoded Stripe Secret Key detected

Key values are redacted in findings and reports. Rotate any key that shipped in a released build.

M2

Release builds that are not signed the way a production build should be.

What Is Checked
  • Android APK signed with the Android debug key
Example Finding
APK signed with Android debug key, not suitable for production

Mobile scans do not check SDK versions against advisories. Dependency advisories from the OSV database are checked in repository scans, which map to the OWASP Top 10 (2021) below.

M3

Weak login flows, missing session controls and broken access checks.

Not checked. A static scan of the app package cannot see how the app and its backend authenticate users or enforce access, so Strata reports nothing in this category. Cover it with a manual review or a dynamic test.

M4

Code that loads or runs code the app did not ship with.

What Is Checked
  • Dynamic code loading (DexClassLoader)
  • Shell command execution (Runtime.exec / ProcessBuilder)
Example Finding
Dynamic code loading detected (DexClassLoader)

These are Android checks. Injection rules (SQL, command, XSS) run on repository source code and map to the OWASP Top 10 (2021).

M5

Configuration and strings that let data travel without TLS.

What Is Checked
  • Android: cleartext traffic allowed (usesCleartextTraffic, or a target SDK below 28)
  • Android: network security config warnings
  • Plain http:// URLs in the app's strings
  • iOS: App Transport Security NSAllowsArbitraryLoads = true
  • iOS: network extension and VPN entitlements
Example Finding
App Transport Security: NSAllowsArbitraryLoads = true (all HTTP allowed)

Strata reads the declared configuration. It does not connect to your endpoints, so it does not test TLS versions, cipher suites or certificate pinning.

M6

Permissions and entitlements that give the app access to sensitive personal data.

What Is Checked
  • Android: SMS read and receive permissions
  • iOS: always-on location, health and tracking (ATT) permissions
  • iOS: HealthKit entitlement
Example Finding
Permission to read personal data: android.permission.READ_SMS

A finding here means the app asks for the access. Whether it needs that access is a call for the reviewer.

M7

Builds that are easy to reverse-engineer or tamper with.

What Is Checked
  • Android: no code obfuscation (human-readable class names)
  • Android: debug builds (debug-key signing or the debuggable flag)
  • Android: root and instrumentation strings (Frida, Magisk, Xposed)
  • iOS: jailbreak and Frida markers in the binary
  • Android: suspicious native libraries such as frida, substrate and xposed
  • VirusTotal detections, when VirusTotal is configured
Example Finding
Root or instrumentation tool strings detected in bytecode

These are signals found in the package, not a test of the app's anti-tampering behaviour at runtime.

M8

Manifest, Info.plist, entitlement and signing settings that weaken the app.

What Is Checked
  • Android: exported components with no permission protection, including implicitly exported ones on older targets
  • Android: allowBackup and debuggable enabled
  • Android: high-risk capability permissions (accessibility service, overlay, install packages, write settings, send SMS)
  • iOS: Face ID usage
  • iOS: entitlement warnings such as get-task-allow
  • iOS: development provisioning profiles
Example Finding
Exported activity 'com.example.LoginActivity' has no permission protection.

Exported components that declare a permission are not reported.

M9

Settings that put the app's files where other apps or users can reach them.

What Is Checked
  • Android: external storage permissions (READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE)
  • iOS: UIFileSharingEnabled and LSSupportsOpeningDocumentsInPlace
Example Finding
App writes to external storage (WRITE_EXTERNAL_STORAGE)

Strata does not inspect what the app writes to SharedPreferences, databases or the keychain.

M10

Use of broken or weak cryptographic algorithms.

What Is Checked
  • Android: flags weak algorithms such as MD5, SHA-1, DES and RC4 referenced in the app's code
  • Weak ciphers are rated Medium; weak hashes are rated Low, as they are often used for checksums
Example Finding
Weak cipher referenced in app code: DES

Android APKs only; iOS scans do not check this category. Strata matches exact algorithm names in the DEX code, including bundled libraries, so a hit can come from a library rather than your own code. It does not analyse key management or how ciphers are used.

Repository Scans Map to the OWASP Top 10 (2021)

Source code findings use the web application list. Six of its ten categories have rules today; the other four are not checked.

IDCategoryWhat Is Checked
A02:2021Cryptographic FailuresHardcoded secrets, committed sensitive files (.env, private keys), weak hashes and ciphers, cleartext key storage
A03:2021InjectionSQL injection, command injection, cross-site scripting and code injection patterns
A06:2021Vulnerable and Outdated ComponentsKnown advisories from the OSV database for npm, PyPI and Maven/Gradle dependencies
A07:2021Identification and Authentication FailuresHardcoded credentials in code (Basic Auth, JDBC connections, keychain values)
A08:2021Software and Data Integrity FailuresInsecure deserialization (pickle, yaml.load, ObjectInputStream, XMLDecoder) and eval of external data
A10:2021Server-Side Request Forgery (SSRF)Outbound requests built from user-controlled URLs

Not checked: A01 Broken Access Control, A04 Insecure Design, A05 Security Misconfiguration, A09 Security Logging and Monitoring Failures.

How Findings Are Rated

Each check has a fixed severity. In a mobile scan, the findings in one OWASP category share the highest severity among that category's checks that fired. Mobile findings are rated High, Medium or Low; Critical is used only in repository scans.

Critical

Repository scans only. Examples: committed AWS access keys, Java SQL statements built by string concatenation, os.system() with a dynamic command, pickle.load() on untrusted data.

High

Example checks: high-confidence hardcoded keys, exported components with no permission protection, cleartext traffic allowed, an APK signed with the debug key.

Medium

Example checks: debug builds, allowBackup enabled, plain http:// URLs in the app, weak ciphers such as DES, iOS development provisioning profiles.

Low

Example checks: no code obfuscation, reading external storage, weak hash algorithms such as MD5 or SHA-1 (often used for checksums rather than security).

Our False Positive Philosophy

Updated Detection

Try OWASP Mapping
Free Today

Upload an APK or IPA and get findings mapped to the OWASP Mobile Top 10 (2024) in under 30 seconds. No credit card required.

Want the detail behind each category? Browse the OWASP Mobile Top 10 reference collection.