What we test
We assess authentication, sessions, permissions and business workflows alongside local data storage, logs, network communications and device integrations. Agreed APIs and connected services are included so we can check where access rules are enforced.
The scope identifies the platforms, application versions, devices and access conditions to assess. We investigate how the app handles sensitive data, what it exposes to other applications and what happens when a user changes role or signs out.
How we test
We start with a walkthrough of the app and its important user journeys, then agree test environments, accounts and devices. A pentester combines examination of the application package with testing of its behaviour and communications with the services in scope.
We compare the available functions with the intended permissions and verify outcomes using representative accounts and test data. Each finding records the conditions needed and the demonstrated effect on the application, device or user data.
What you receive
A report with an executive summary, the platforms and builds assessed, coverage, limitations and prioritised findings. Each finding includes evidence, reproduction conditions, business impact and remediation guidance.
We distinguish issues in the mobile client from those in its API or connected services. We agree which fixes to verify and set out retesting arrangements in the proposal.
What we need from you
Your intended platforms and versions, target date and a demonstration of the important functions. We will confirm how to share a test build, representative accounts, test data and any required access.
Tell us about device requirements, supported configurations and third-party integrations. We agree the permitted devices, build distribution and handling of data before testing begins.