MOB — Penetration testing
Mobile Application Penetration Testing
A mobile app is a client you hand to every attacker. We examine what it stores, what it trusts, how it talks to your backend — and whether the backend still enforces the rules when the app is bypassed.
Who it's for
Built for teams that ship.
01
Consumer & fintech apps
Apps handling accounts, payments or personal data on devices you don't control.
02
Enterprise mobile
Internal apps that connect employees' devices to business systems.
03
App store releases
Teams preparing major versions or responding to customer security questionnaires.
What we test
Coverage, defined up front.
Security assessments of Android and iOS applications covering local storage, authentication, transport security, platform interaction and the backend APIs the app relies on.
Client-side security
- Local data storage and keychain/keystore use
- Hard-coded secrets and configuration
- Logging, caching and clipboard exposure
- Binary protections where in scope
Authentication & sessions
- Login, biometric and token flows
- Session renewal and revocation
- Deep links and intent handling
- Local authentication bypass
Communication
- TLS configuration and certificate validation
- Certificate pinning behaviour
- Sensitive data in transit
- Third-party SDK traffic
Backend APIs
- Authorisation enforced server-side
- IDOR and data exposure
- Input validation
- Abuse and rate limiting
Common risks
What typically goes wrong.
Sensitive data on device
Tokens, personal data or keys stored where other apps, backups or a lost device expose them.
Trusting the client
Security decisions made in the app that the server doesn't re-check.
Weak transport
Traffic that can be intercepted or modified on hostile networks.
Embedded secrets
API keys and credentials recoverable through authorised reverse engineering.
Methodology
How the testing works.
- STEP 01
Static analysis
Review of the application package, configuration and code paths where authorised.
- STEP 02
Dynamic analysis
Runtime testing on instrumented devices to observe storage, traffic and behaviour.
- STEP 03
API testing
Direct testing of the backend endpoints the app uses, independent of the client.
- STEP 04
Validate
Confirm impact, document reproduction steps and map findings to remediation.
What you receive
Deliverables
Executive summary
Scope, overall risk posture and the priorities leadership needs to act on — in plain language.
Technical findings
Each issue with affected components, description, evidence and severity reasoning.
Risk prioritisation
Severity and likelihood in the context of your business, so fixes are ordered by real risk.
Reproduction evidence
Requests, responses, screenshots and step-by-step reproduction for your engineers.
Impact explanations
What an attacker could realistically achieve with each finding in your environment.
Remediation guidance
Specific fixes that address root causes, not just symptoms.
Retesting
Verification that fixes work, with an updated report — when included in scope.
CONFIDENTIALITY
Reports are delivered through an agreed secure channel. Client findings are never published or reused.
Engagement process
What to expect, step by step.
- 01
Scoping call
We clarify objectives, targets, environments, constraints and any compliance or customer-review drivers.
- 02
Proposal & authorisation
You receive a written scope, timeline and rules of engagement. Testing starts only after written authorisation.
- 03
Testing window
Manual testing within the agreed window, with a named point of contact and immediate escalation of critical issues.
- 04
Reporting
A structured report with executive and technical layers, delivered through an agreed secure channel.
- 05
Debrief
A walkthrough of findings with your engineering team, focused on root causes and remediation order.
- 06
Retest
Where included, fixed findings are verified and the report is updated to reflect remediation status.
FAQ
Questions buyers ask.
Not necessarily. Many assessments are performed on release or debug builds. Source access enables a deeper review and can be scoped in.
Yes — each platform can be scoped individually or together, including the shared backend API.
Only where you authorise it in writing as part of the scope.
Next step
Get a penetration testing proposal.
Tell us what you need tested. We'll arrange a scoping call and come back with a written proposal — scope, approach, timeline and rules of engagement.