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?
The OWASP Mobile Top 10 is a community-curated list of the ten most critical security risks in mobile applications, published by the Open Web Application Security Project (OWASP). It provides a standardised vocabulary for mobile vulnerabilities and serves as the foundational reference for secure mobile application development.
The 2024 version of the OWASP Mobile Top 10 (M1–M10) covers the risks that appear most frequently in real-world mobile application penetration tests and security assessments, representing consensus from hundreds of security practitioners worldwide.
Strata Security tags each mobile finding with its OWASP Mobile Top 10 (2024) category and a link to the OWASP page for it, so reports carry context that clients, auditors and compliance reviewers recognise. No manual tagging is needed. Repository scans are not mobile apps, so their findings map to the OWASP Top 10 (2021) instead.
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.
| ID | Category | Android | iOS | Highest Severity |
|---|---|---|---|---|
| M1 | Improper Credential Usage | ✓ | ✓ | High |
| M2 | Inadequate Supply Chain Security | ✓ | No | High |
| M3 | Insecure Authentication/Authorization | No | No | Not checked |
| M4 | Insufficient Input/Output Validation | ✓ | No | High |
| M5 | Insecure Communication | ✓ | ✓ | High |
| M6 | Inadequate Privacy Controls | ✓ | ✓ | High |
| M7 | Insufficient Binary Protection | ✓ | ✓ | High |
| M8 | Security Misconfiguration | ✓ | ✓ | High |
| M9 | Insecure Data Storage | ✓ | ✓ | Medium |
| M10 | Insufficient Cryptography | ✓ | No | Medium |
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.
Hardcoded credentials and API keys left in the app, where anyone who downloads it can extract them.
- 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
Hardcoded Stripe Secret Key detectedKey values are redacted in findings and reports. Rotate any key that shipped in a released build.
Release builds that are not signed the way a production build should be.
- Android APK signed with the Android debug key
APK signed with Android debug key, not suitable for productionMobile 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.
Insecure Authentication/Authorization
Not checkedWeak 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.
Code that loads or runs code the app did not ship with.
- Dynamic code loading (DexClassLoader)
- Shell command execution (Runtime.exec / ProcessBuilder)
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).
Configuration and strings that let data travel without TLS.
- 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
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.
Permissions and entitlements that give the app access to sensitive personal data.
- Android: SMS read and receive permissions
- iOS: always-on location, health and tracking (ATT) permissions
- iOS: HealthKit entitlement
Permission to read personal data: android.permission.READ_SMSA finding here means the app asks for the access. Whether it needs that access is a call for the reviewer.
Builds that are easy to reverse-engineer or tamper with.
- 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
Root or instrumentation tool strings detected in bytecodeThese are signals found in the package, not a test of the app's anti-tampering behaviour at runtime.
Manifest, Info.plist, entitlement and signing settings that weaken the app.
- 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
Exported activity 'com.example.LoginActivity' has no permission protection.Exported components that declare a permission are not reported.
Insecure Data Storage
MediumSettings that put the app's files where other apps or users can reach them.
- Android: external storage permissions (READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE)
- iOS: UIFileSharingEnabled and LSSupportsOpeningDocumentsInPlace
App writes to external storage (WRITE_EXTERNAL_STORAGE)Strata does not inspect what the app writes to SharedPreferences, databases or the keychain.
Use of broken or weak cryptographic algorithms.
- 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
Weak cipher referenced in app code: DESAndroid 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.
| ID | Category | What Is Checked |
|---|---|---|
| A02:2021 | Cryptographic Failures | Hardcoded secrets, committed sensitive files (.env, private keys), weak hashes and ciphers, cleartext key storage |
| A03:2021 | Injection | SQL injection, command injection, cross-site scripting and code injection patterns |
| A06:2021 | Vulnerable and Outdated Components | Known advisories from the OSV database for npm, PyPI and Maven/Gradle dependencies |
| A07:2021 | Identification and Authentication Failures | Hardcoded credentials in code (Basic Auth, JDBC connections, keychain values) |
| A08:2021 | Software and Data Integrity Failures | Insecure deserialization (pickle, yaml.load, ObjectInputStream, XMLDecoder) and eval of external data |
| A10:2021 | Server-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.
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.
Example checks: high-confidence hardcoded keys, exported components with no permission protection, cleartext traffic allowed, an APK signed with the debug key.
Example checks: debug builds, allowBackup enabled, plain http:// URLs in the app, weak ciphers such as DES, iOS development provisioning profiles.
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
Static analysis is inherently imperfect. Our goal is to surface actionable findings, not to bury developers under noise.
Strata Security takes the following approach to minimise false positives:
- File context: in repository scans, a name-keyed secret match (such as password = ...) in a test file, documentation or a comment is down-weighted. A key in a provider's own format is reported wherever it sits.
- Entropy thresholds: repository secret rules for keyed values (passwords, generic API keys, cloud secrets) use entropy analysis to separate real secrets from placeholders.
- Suppression support: findings you have reviewed can be marked as accepted risk, false positive or suppressed, and stay that way in future scans, with an audit trail of each change.
We acknowledge that some findings will require human judgement. Each finding carries its evidence, and repository findings include the file path and line number, so a reviewer can make a quick determination.
Updated Detection
The mobile threat landscape evolves constantly. New vulnerabilities emerge, platform APIs change, and attackers discover novel techniques. Strata Security keeps its rules and mappings current.
- Dependency advisories are looked up in the OSV database at scan time, in repository scans
- Mobile findings map to the OWASP Mobile Top 10 2024 (updated from 2016)
When you scan the same app twice, once today and once in three months, you may get different results as we improve detection accuracy and add coverage. We believe that is a feature, not a bug.
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.