Cyber security · 04

Mobile app security for iOS, Android and the API behind them.

We pull your app apart, watch everything it sends, and check what it leaves on the device. Then we test the API it talks to, because that is where the data lives.

Overview

Anything shipped inside your app should be treated as public. We check what that includes.

We decompile and inspect the app for hard-coded keys, hidden endpoints, debug features and weak protections, then run it on test devices to see what it stores and sends.

Most real damage happens through the API, so we intercept the app's traffic and test the backend with the same rigour as our API tests.

Standards & frameworks

  • OWASP MASVS
  • OWASP MASTG
  • OWASP API Top 10
  • CREST-aligned
  • CVSS 3.1

What we test

What's in scope.
And what we look for.

01 · On the device

What the app holds. Storage, code and platform features.

  • Local storage

    Tokens, personal data and caches in files, databases, logs and backups.

  • Reverse engineering

    Hard-coded secrets, hidden endpoints and business logic in the binary.

  • Platform features

    Deep links, intents, WebViews, clipboard and screenshots.

  • Resilience

    Root and jailbreak detection, tamper checks and certificate pinning.

02 · In transit

What the app sends. The API and network behaviour.

  • Traffic interception

    TLS configuration, pinning bypass and sensitive data in requests.

  • Authentication

    Login, biometrics, session handling and token refresh.

  • Backend API

    Object-level access, data exposure and rate limits on the app's API.

  • Third parties

    SDKs, analytics and what they collect.

Process

How a test runs, start to finish.

  1. 1

    Scope

    Builds, platforms, environments and test accounts agreed.

  2. 2

    Static analysis

    Decompilation and code review of the app package.

  3. 3

    Dynamic testing

    On-device testing with traffic interception and runtime instrumentation.

  4. 4

    Report & retest

    Findings mapped to MASVS with fixes for your platform, then a retest.

Deliverables

What ships with
every test.

One report for two audiences: leadership gets the risk, engineers get the evidence and the fix. Here is how that compares with an automated scan.

Read the sample report →
DeliverableYUPL testAutomated scan
Executive summaryPlain-English risk overview for leadership, boards and auditors.YesBasic
Technical findingsEvery issue with a CVSS score, affected assets and business impact.YesYes
Evidence and reproduction stepsRequests, screenshots and steps so your engineers can confirm each finding.Yes—Not included
Chained and business-logic issuesLow-severity issues combined into real attack paths, and flaws a tool cannot understand.Yes—Not included
Remediation advice for your stackSpecific fixes for your framework and infrastructure, prioritised by risk.YesGeneric
Walkthrough callWe take your technical and business teams through the findings.Yes—Not included
Retest and reissued reportWe verify the fixes and reissue the report showing what is closed.Yes—Not included

“They managed to find a very serious vulnerability in our platform and walked us through fixing it. We will surely use their services!”

Assaf KostinerFounder, PaintYourLife

FAQ

Questions

About mobile app security. Anything else, call us.

Test builds for iOS (IPA or TestFlight) and Android (APK or AAB), test accounts and access to a non-production API if you have one.

Yes. Cross-platform apps have their own quirks in how code and secrets are packaged, and we test for those.

We test the API as the app uses it. A full standalone API test can be added if you have partners or other clients using the same API.

Yes. We build native and cross-platform apps, so we can implement fixes or support your team.

Scope your mobile app security.
Get a fixed quote.

A developer or security engineer reads every enquiry and replies, not a salesperson.

  • Fixed quote after a short scoping call
  • NDA available before you share details
  • Remediation and retest on every security engagement

Domains are fine as plain text (app.example.co.uk).

We only use your details to reply to this enquiry. See our privacy policy.