Skip to content
CISO Marketplace Services

Mobile Application Security Assessment

Comprehensive security testing of iOS and Android applications

In scope

  • iOS and Android application testing against OWASP MASVS
  • Local data storage, keychain / keystore and cryptography review
  • Authentication, session and authorization testing
  • Backend API testing for the application
  • Reverse-engineering resistance and tamper checks
  • Third-party SDK and permission review

You receive

  • Mobile application security report mapped to OWASP MASVS
  • Reproducible findings with risk ratings
  • Developer remediation guidance
  • Executive summary
  • Retest of fixed findings

Tiers

Choose the depth.

Basic Assessment

$10K

Security test of 1 mobile app on 1 platform (a single iOS build or a single Android build): static and dynamic analysis of the app binary, local storage, authentication, and app-to-server traffic. One retest.

mobile apps
1
  • 1 app, 1 platform build
  • Static and dynamic analysis of the binary
  • Local data storage, auth and session checks
  • Traffic interception of app-to-server calls
  • One retest of fixed findings
  • — Second platform build
  • — Dedicated backend API penetration test
  • — Source code review
  • — CI/CD integration of SAST/DAST
Scope Basic Assessment

Advanced Assessment

$15K

Security test of 1 mobile app on both platforms (iOS and Android builds) plus its 1 backend API (up to 50 endpoints), with dependency analysis and source-assisted review where code is provided. One retest.

mobile apps
2
apis
1
  • iOS and Android builds of 1 app (2 builds)
  • 1 backend API, up to 50 endpoints
  • Third-party dependency/SDK analysis
  • Source-assisted review where code is supplied
  • One retest of fixed findings
  • — Additional apps
  • — Internal network testing
  • — Social engineering
  • — Ongoing testing of new releases
Scope Advanced Assessment

Members: engagement coupons from the CISO Marketplace coupon book apply to services. There is no blanket discount.

What's inside this engagement

Phase by phase.

How a application, api & code testing engagement runs, what happens in each phase and what you see. Exact scope, tier and timeline are fixed in your proposal and SOW.

  1. 01Scoping & threat model

    Roles, key workflows, integrations and the data that matters are mapped before testing.

    You see · Architecture overview and test accounts.

  2. 02Authenticated testing

    Manual testing against OWASP WSTG / ASVS / MASVS / API Top 10: authorization, business logic, injection, session handling.

    You see · A heads-up on any confirmed critical.

  3. 03Business-logic abuse

    The flaws scanners can't find: broken object-level authorization, workflow bypasses, pricing and entitlement abuse.

    You see · Findings in your application's own terms.

  4. 04Reporting

    Each finding with severity, request/response evidence, reproduction steps and a code-level fix.

    You see · A report developers can act on.

  5. 05Retest

    Fixes verified and the report reissued, where the tier includes it.

    You see · An attestation you can share with customers.

Commercials

From first call to final report.

  1. 01

    Scoping call

    A practitioner, not a salesperson, walks through targets, constraints and what a good outcome looks like for you.

  2. 02

    Proposal & rules of engagement

    A fixed-scope proposal with tier, price and deliverables. Rules of engagement, contacts and out-of-bounds systems are agreed in writing.

  3. 03

    Sign, then start

    MSA and SOW are signed electronically and the deposit is paid. Only then does testing begin.

  4. 04

    Execution

    Testing runs to the agreed plan. Critical findings are escalated as they are found; you don't wait for the report.

  5. 05

    Report & debrief

    An executive summary plus technical findings with evidence, reproduction steps and fixes, walked through with your team.

  6. 06

    Retest

    Where the tier includes it, we verify your fixes and reissue the report, so auditors and customers see the issues closed.

Timelines are set per engagement in the SOW.

Related

Research

Latest from the blog

All posts on cisomarketplace.com →
Talk to an advisor
Advisor