Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Mobile application penetration testing examines the client binary, its local storage, its network communication, and the backend behind it, on a device the attacker fully controls.

What Is Mobile Application Penetration Testing?
Mobile application penetration testing is a security assessment of an iOS or Android application across every layer it occupies: the compiled binary, the data it stores on the device, the traffic between the application and its servers, and the backend APIs that do the real work. The organising assumption is specific to the platform, and it changes everything about how the testing is conducted.
That assumption is that the attacker owns the device. They can root or jailbreak it, decompile the application, attach a debugger, hook any function, and read any file the application writes. Nothing on the client is secret, and nothing on the client can be trusted. The job of a test is to find out what the application assumed it could rely on, and what happens when it cannot.
Most engagements are structured around the OWASP Mobile Application Security Verification Standard. Version 2 organises controls into groups that map neatly onto the phases of an assessment:
The companion testing guide, described under MASVS and MASTG, sets out how each control is verified.
Static analysis starts with the package. An Android APK is decompiled with jadx and apktool to recover near-source Java or Kotlin, the manifest is read for exported components and permissions, and native libraries go to a disassembler. An iOS IPA yields the Mach-O binary, the property lists, and the entitlements. Automated platforms such as MobSF cover the first pass efficiently; the hardcoded API keys, embedded certificates, debug endpoints, and third-party SDK inventory come out here.
Dynamic analysis requires a test device. Traffic is routed through an intercepting proxy, which means installing the proxy’s certificate into the device trust store and, almost always, disabling certificate pinning with Frida or Objection. Once traffic is visible, the backend API becomes the main target, because that is where the serious findings usually are: the same broken object level authorisation that dominates API penetration testing, except reached through an application that was trusted to send only well-formed requests.
Runtime work also covers what the application stores while running, whether sensitive values survive in memory longer than they should, how it behaves when backgrounded, and whether its root detection and tamper checks can be hooked away. On a rooted device they always can; the question is how much effort it takes and whether the application degrades safely when it notices.
The recurring findings across assessments are consistent. Authentication tokens with no expiry stored in plain preferences. Full card numbers or health data in an unencrypted local database. Deep links that trigger privileged actions without verifying the caller. WebViews with JavaScript interfaces exposed to loaded content. Backup flags left enabled so the entire application sandbox can be extracted over USB. Business logic enforced only in the client, so an edited request produces a free upgrade. And consistently, API endpoints that trust the user identifier supplied in the request.
A useful scope names the platforms and versions, states whether source code is provided, identifies the backend environment to be tested, and provides multiple test accounts in each role. It should also say which third-party services may be touched, since a payment or identity provider’s sandbox is in scope and its production system is not.
For UK organisations, several frameworks apply directly. PCI DSS and the PCI Mobile Payment on COTS standards cover applications handling card data. The FCA expects firms to understand and test the technology supporting important business services, which includes customer-facing applications. Under UK GDPR, data minimisation obligations extend to what SDKs collect on your behalf, and PECR governs access to information stored on a user’s device, which is why the privacy control group is not optional. NCSC guidance on application development sets out the baseline expectations.
At Privia Security, our Mobile Application Security Services cover client, transport, and backend layers against the MASVS control groups.
No, and most testing is done without it. Android packages decompile to near-source Java or Kotlin, and iOS binaries can be analysed with a disassembler and runtime instrumentation. Source code accelerates the work and improves coverage of logic that is hard to reach at runtime, so providing it is useful, but black-box testing reflects what an attacker actually has.
Because the application’s own sandbox hides its stored data, and instrumentation requires the privileges to attach to another process. Without that access, the tester cannot see what the application writes, intercept pinned traffic, or observe cryptographic operations. Where a rooted device is unavailable, the application can be repackaged with the Frida Gadget embedded, which works on an unmodified device.
It should be, and in most assessments it produces the most serious findings. The application is a client that an attacker controls completely, so every assumption it makes about the requests it will send can be violated. Authorisation flaws at the API are reachable by anyone who can read the traffic, which is anyone with the application installed.
It depends on the application. For banking, payments, and anything handling high-value transactions, yes, as one signal among several, reported to the server rather than acted on locally. It can always be bypassed on a device the attacker controls, so treat it as raising cost rather than providing protection, and pair it with platform attestation such as Play Integrity or App Attest validated server-side.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.