iOS · Android · Mobile APIs
Mobile Application Penetration Testing
We test your iOS and Android apps together with the APIs they call: how they store data, handle sessions and resist reverse engineering, so a lost phone or a curious attacker does not become a breach.
- iOS and Android
- App and API tested together
- Static and dynamic analysis
In one sentence
What is mobile application penetration testing?
Mobile application penetration testing examines your iOS and Android apps and the back-end APIs they use, to find weaknesses in how they store data, authenticate users, communicate and resist tampering.
An app runs on a device you do not control, so anything inside it can be extracted and anything it trusts can be changed. We test the app on the device, its traffic, and the API behind it.
What we need from you
- Test builds for iOS and Android (or store versions)
- Test accounts for each user role
- Access to the API environment the app uses
- Any documentation of custom security features
Scope
What we test
The app on the device, its communication, and the API behind it.
Data storage on the device
Tokens, personal data, caches, logs and backups: what an attacker with the phone or its backup can read.
- Keychain and Keystore
- Backups
- Caches
Authentication and sessions
Login, biometrics, session handling and how the app and API trust each other.
- Biometrics
- Tokens
- Sessions
Network communication
Transport security, certificate validation and pinning, and what an attacker on the same network can see or change.
- TLS
- Certificate pinning
- Interception
Reverse engineering and tampering
Hard-coded secrets, obfuscation, root and jailbreak detection, and client-side checks that can be bypassed.
- Decompiling
- Secrets
- Tampering
Platform interaction
Permissions, deep links, intents and other ways other apps or links can reach into yours.
- Permissions
- Deep links
- Intents
The API behind the app
Access control, business logic and data exposure in the back end the app calls.
- Access control
- Business logic
- Data exposure
Approach
Testing approaches based on access
Choose how much you share with us. More context means deeper coverage in the same time.
No prior knowledge
Black box
We test the store version of the app and its traffic as an attacker would.
Accounts and some context
Grey box
With test accounts and debug-capable builds, we test storage, sessions and the API in depth.
Full access
White box
With source code, we add a review of how security features are implemented.
Engagement
How we work with you
Scope online
Describe what you need in Flint, our scoping platform. Answer only the questions that apply.
Proposal, signed online
Effort, price and the statement of work are built from your answers.
Ready for day one
Authorisation, test accounts and rules of engagement are agreed before testing starts.
Senior-led testing
Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.
Report and retest
Your report is ready in Slate, our client portal, within 48 hours of testing ending.
What you receive
Everything stays in one place, in your own client portal.
- A report in Slate within 48 hours of testing ending
- Every finding with evidence, a risk rating and a fix
- An executive summary for leadership
- Retests you can request finding by finding
- Downloads as PDF or Excel
- Evidence you can hand to your auditors
Standards
Standards we test against
Aligned with the mobile and application security standards your teams use.
- OWASP MASVS
- OWASP MASTG
- OWASP Top 10
- PCI DSS
Do you test both iOS and Android?
What do you need from us?
Do you test the API the app uses?
Can you bypass certificate pinning and jailbreak detection?
How long does a mobile app test take?
When will we receive the report?
Contact
Tell us what you need to test
A senior tester reads every message and replies directly.
What happens next
- A senior tester replieswith any questions about your scope.
- You scope it in Flintor on a short call, if that is quicker.
- A proposal you sign onlinewith effort, price, dates and the statement of work.
Prefer email? Write to [email protected]
