Penetration Testing

Mobile Application Penetration Test

Once your app is in the stores, anyone can download it, dig into its code and intercept every request it sends. That is how an attacker finds keys left in the app, gets around checks that run only on the phone and reaches your back-end directly. We test your Android and iOS apps with the same techniques.

REQUEST THIS SERVICE
Why choose us

We are an Italian security company focused on cloud and application security. Our services draw on years of penetration testing, consulting, training and research.

Solid methodology built by experts
International certifications
Fast-growing security company
MORE ABOUT US

FAQ

Mobile app penetration testing: common questions

What clients usually ask us before we test a mobile app.

What do you need from us?

The production build of each app you want tested and a test account for each user role, plus the API documentation if you have it. If we need to go deeper, we may also ask you for a build without protections such as obfuscation and certificate pinning.

Our app uses certificate pinning, root detection and obfuscation. Can you still test it?

Yes. Certificate pinning, root and jailbreak detection, obfuscation and anti-tampering controls are the first defenses an attacker tries to get around, and so do we. The report also assesses how effective they are, which matters most for apps that handle payments or sensitive data.

Do you need our source code?

No. We work on the compiled app, which is also what an attacker has. If you want to go further, the source code can be checked with a secure code review, which finds issues that testing the running app alone can miss.

Our APIs have already been tested. Do we still need a mobile test?

If the app handles valuable data or features, yes. An API test doesn't see what the app keeps on the phone, what is left in its code, such as keys or hidden features, or how other apps on the same device can interact with it. Those are the parts a mobile test adds.