Mobile Application Penetration Testing: What Gets Tested on iOS and Android
Harsh
Cybersecurity Experts
Table of Contents
- 01What is mobile application penetration testing?
- 02The four areas every mobile pen test covers
- 03Android penetration testing: what gets checked
- 04iOS penetration testing: what gets checked
- 05How the test maps to the OWASP Mobile Top 10
- 06What to prepare before the test
- 07What you receive at the end
- 08Scope your mobile app pen test
- 09Frequently Asked Questions
What is mobile application penetration testing?
Mobile application penetration testing is a manual security assessment of an iOS or Android app, the device storage it uses and the backend APIs it talks to. A tester installs the app on real or jailbroken and rooted devices, takes the binary apart, intercepts its traffic and tries to reach data or functions that a normal user should never see.
A mobile test differs from a web test in one basic way. The attacker holds a full copy of your code. Anyone can download the app from the App Store or Google Play, unpack it and read what is inside. Anything stored in the binary, such as API keys, hidden endpoints or feature flags, should be treated as public.
This guide covers what gets tested on each platform, how the work maps to the OWASP Mobile Top 10 and what to have ready so the test starts on time.
The four areas every mobile pen test covers
Area | What the tester examines | Typical findings
|
|---|---|---|
The app binary | Decompiled code, embedded strings, third-party SDKs, build settings | Hardcoded keys, debug code left in release builds, outdated libraries |
Data on the device | Local databases, preference files, caches, logs, backups, keychain or keystore use | Tokens or personal data stored in plain text |
Network traffic | TLS configuration, certificate validation, pinning, what the app sends and to whom | Traffic that can be intercepted, sensitive data sent to analytics SDKs |
Backend APIs | Authentication, authorization on each object and function, input handling | One user reading another user's records by changing an ID |
Most serious findings come from the last row. The app is a client, and the server decides who can see what. A test that only looks at the binary and skips the API misses the place where data leaks at scale.
Android penetration testing: what gets checked
Android penetration testing starts with the APK or app bundle. The tester decompiles it and reads the manifest and code before running anything.
Exported components. Activities, services, broadcast receivers and content providers that other apps on the device can call. An exported activity can let another app skip your login screen.
Deep links and intents. Whether a crafted link can open internal screens or pass untrusted data into the app.
Local storage. SharedPreferences, SQLite databases and files on external storage, checked for tokens and personal data.
Keystore use. Whether keys are generated and held in the Android Keystore or sit in code.
WebViews. JavaScript interfaces and file access settings that let web content reach native functions.
Build and backup settings. The debuggable flag, cleartext traffic permission and whether app data can be pulled through device backup.
Tamper and root checks. How easily the app can be modified, re-signed and run on a rooted device with instrumentation tools attached.
iOS penetration testing: what gets checked
iOS penetration testing uses a decrypted copy of the IPA and, for full coverage, a jailbroken test device.
Keychain and data protection. Which items are stored in the Keychain, with which accessibility class, and which files lack data protection.
Plist files and local databases. Configuration and cached responses that hold credentials or session data.
App Transport Security. Exceptions in Info.plist that allow unencrypted connections.
URL schemes and universal links. Whether another app or a web page can trigger actions inside yours.
Pasteboard, screenshots and logs. Sensitive data copied to the shared clipboard, captured in the app switcher snapshot or written to device logs.
Binary protections. Jailbreak detection, anti-debugging and how quickly a tester can bypass them with runtime hooks.
Biometric checks. Whether Face ID or Touch ID gates a real secret in the Keychain or only flips a local boolean that can be patched.
How the test maps to the OWASP Mobile Top 10
The OWASP Mobile Top 10 was updated in 2024, its first revision since 2016. Testers use it with the OWASP Mobile Application Security Verification Standard (MASVS) and the testing guide (MASTG) to structure the work. Buyers and auditors often ask for findings mapped to it.
OWASP Mobile Top 10 (2024) | What a tester does
|
|---|---|
M1 Improper Credential Usage | Searches the binary and storage for hardcoded or badly stored credentials |
M2 Inadequate Supply Chain Security | Reviews third-party SDKs and libraries for known flaws |
M3 Insecure Authentication/Authorization | Tests login, session handling and server-side permission checks |
M4 Insufficient Input/Output Validation | Sends malformed input through forms, deep links and intents |
M5 Insecure Communication | Intercepts traffic and tries to defeat certificate validation |
M6 Inadequate Privacy Controls | Tracks where personal data is stored, logged and shared |
M7 Insufficient Binary Protections | Reverse engineers, modifies and repackages the app |
M8 Security Misconfiguration | Checks permissions, debug flags and exported components |
M9 Insecure Data Storage | Inspects files, databases, caches and backups |
M10 Insufficient Cryptography | Reviews algorithms, key storage and random number use |
What to prepare before the test
A mobile test stalls when the tester cannot get a working build or a usable account. Have these ready before the start date:
A release-equivalent build for each platform, delivered as an IPA and an APK or through TestFlight and an internal testing track.
Two test accounts for every user role, so the tester can check whether one account can reach another's data.
A note on whether certificate pinning and root or jailbreak detection are active. Many teams supply one build with protections on and one with them off, so the tester can assess the controls and still cover the API in the time available.
API documentation or a Postman collection for the backend.
The environment to test against, with realistic data and no real customer records.
A list of anything out of scope, such as third-party payment screens.
What you receive at the end
A mobile pen test report should give your developers enough to reproduce and fix each issue. Expect an executive summary, a technical finding for each vulnerability with a CVSS score, proof of exploitation, remediation guidance and a mapping to the OWASP Mobile Top 10. After fixes ship, a re-test confirms each one is closed.
Digisecuritas tests iOS and Android apps with reverse engineering and binary analysis, covers the backend APIs in the same engagement and includes a re-test of remediated findings. The testing team holds OSCP, CEH and CREST certifications. Details are on the VAPT services page.
Scope your mobile app pen test
Send us the platforms, the number of user roles and a rough count of screens and API endpoints. We will come back with a scope, a test plan and a start date.
Scope your mobile app pen test
