Penetration testing · Mobile · iOS · Android
What the app keeps,and what it gives away.
iOS and Android applications tested on the device and on the wire: what is stored locally, how the app talks to its servers, and how well it resists being taken apart.
CREST-certified testers£950 + VAT a dayReport in five working daysRetest included
A mobile app runs on a device you do not control.
Anyone can install your application, inspect what it stores, watch its traffic and modify it. A mobile test establishes what an attacker learns by doing so: credentials or tokens left in storage, keys in the package, traffic that can be intercepted, checks performed on the device that belong on the server. We test to the OWASP Mobile Application Security Verification Standard and its testing guide. The servers the app talks to are scoped alongside it as an API test, because that is usually where a weakness in the app is turned into access to data.
- Scope
- The iOS and Android builds of one application
- Typical duration
- Three days of testing for one platform, five for both, plus one for reporting
- Typical price
- £3,800 + VAT for one platform, £5,700 + VAT for both
- You provide
- Test builds or store links, and accounts for each user role
- Methods
- OWASP MASVS · OWASP MASTG · MITRE ATT&CK mapping
Coverage
What a mobile test looks at
Local storage
What the app writes to the device, where, and whether other apps, backups or a lost phone would give it up.
Transport security
TLS configuration, certificate pinning, and what happens when the connection is intercepted.
Authentication and sessions
Biometrics, PINs, token lifetime and what survives signing out.
Platform interaction
Deep links, intents, the clipboard, backups and the permissions the app asks for.
Resistance to tampering
Root and jailbreak detection, obfuscation, and whether checks made on the device can simply be removed.
Secrets in the package
API keys, endpoints and credentials recoverable from the build.
Findings
What these tests usually find
- _01Tokens stored where they can be readSession tokens or credentials in plain files, logs or backups.Most common
- _02Keys and endpoints in the packageThird-party API keys and internal addresses recoverable in minutes.Secrets
- _03Controls enforced only on the deviceA limit, a role or a price checked by the app and trusted by the server.Logic
- _04Certificate pinning absent or easily bypassedTraffic that can be read and changed on a network the attacker controls.Transport
Cost
What it costs
Penetration testing is charged at one published rate, £950 + VAT a day, with one day added to every engagement for reporting, quality assurance and the debrief. The days follow the scope.
| Scope | Days | Price |
|---|---|---|
| One platform, iOS or Android | 3 testing + 1 reporting | £3,800 + VAT |
| Both platforms | 5 testing + 1 reporting | £5,700 + VAT |
| Both platforms and a 20-endpoint back-end API | 7 testing + 1 reporting | £7,600 + VAT |
These figures come from the estimator on the penetration testing page, where you can change the numbers and combine this test with others; one reporting day covers the whole engagement. A scoping call confirms the days and turns the estimate into a fixed price.
Questions
Questions about this test
Do you need the source code?
No. The test is run against the compiled app, as an attacker would meet it.
Does the app need to be in the store?
No. A test build is fine, ideally one with the same protections as the release build so that the results carry over.
Is the back end included?
Add it as an API item. The estimator prices the two together, and one reporting day covers both. The API testing page explains how endpoints are counted.
Both platforms share one codebase. Do both need testing?
The shared logic is tested once, but storage, permissions and platform protections differ between iOS and Android. That is why both platforms take five days and not six.
Start a conversation
Bring the build.
A thirty-minute scoping call covers the platforms, the roles and the back end, and gives you a fixed price.