RD / Services

Mobile application security assessment

Examine security weaknesses in your mobile product and the way it handles data and interacts with its backend. Agree the client and API boundaries before testing.

150+ security vulnerabilities reported · 7 acknowledged by Meta · 2 Linux kernel CVEs

  • Mobile client
  • Local data
  • Backend boundaries

For mobile product owners and development teams preparing a release, introducing sensitive data flows or arranging an independent customer assessment.

Before a mobile release or a change to sensitive data handling.

What we examine

  • Confirm the platform, application build, access and backend services in scope.
  • Examine relevant data handling, trust boundaries and client-server interactions.
  • Validate findings and distinguish client-side issues from backend risks.

How I test

Testing guided by the OWASP Mobile Application Security Verification Standard (MASVS) and testing guide, covering the app, its local data and its backend API.

How an engagement runs

Send a short brief

The product, what changed, what you need to know and by when. A paragraph is enough, and I reply within three days.

Get a written proposal

Scope, method, exclusions, deliverables, price and dates. Confidentiality, NDA and retesting terms are agreed in the same proposal.

Follow the work as it develops

For assessments, you see evidence and priorities as they emerge. For engineering, you review the agreed milestones.

Report and walkthrough

You receive the report or the delivered work and a walkthrough with your team. Any further fixes or verification are agreed with you.

Security vulnerabilities I have reported

I have reported 150+ security vulnerabilities, including seven in Facebook and Instagram that Meta validated and acknowledged. Your application gets the same attacker’s view: authentication, permissions and the business logic between them.

See the track record

Questions before we begin

Which mobile platforms can you assess?

Share the platform, framework and build requirements. We confirm suitability and the testing approach before agreeing the engagement; the proposal names the supported targets.

Is backend and API testing included?

Only when it is explicitly in scope. A mobile application assessment and a backend assessment have connected but different boundaries, which the proposal makes clear.

What access do you need?

This depends on the agreed approach. Relevant builds, test accounts, environment details and, for code-assisted work, selected source code may be needed.

How quickly will you reply?

Within three days at most. You get questions about your product or an outline of the proposal.

What does it cost?

Published prices are starting points. The final price depends on scope and technical complexity and is fixed in the written proposal before work starts.

How long does it take, and when can you start?

Duration and start date depend on the scope, the technical complexity and my current workload. The proposal states the dates.

Can we work under an NDA?

Yes. Confidentiality terms, including an NDA if you need one, are agreed as part of the proposal before you share code, credentials or findings.

Is a retest included?

Retesting is agreed for each engagement in the proposal: which findings, which version and the time window.

Do you work with agencies?

Yes. Agencies can bring me in for a client’s project. Delivery terms, including white-label reports, are agreed case by case in the proposal.

Related reading

Services

08Contact

Shipping something that handles user data?

Send me a short brief. I reply within three days with questions or a proposal outline, and the price is agreed in writing before work starts.