Mobile app security assessment: we check the device side and the traffic, and rank what to fix first

Assessment of iOS and Android apps: device data, traffic, embedded secrets and permissions behind login, with a Japanese report. From JPY 198,000 (excl. tax).

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Why do an app's holes sit outside the screen, where a web assessment cannot see them?

A mobile app is handed to the user's own device. That means anyone can examine the app itself on their own hands. The starting point for defense is different from a website that stays inside a server.

Take an API key, a passphrase for using an outside service, that a developer wrote into the app for convenience. Once the app is pulled apart, the key can sometimes be read. Member data saved on the device and weakly encrypted traffic are the same kind of problem. However tidy the screens look, holes like these do not show on a screen.

OWASP, an international non-profit that studies the safety of web and mobile software, lists ten risks that tend to arise in mobile apps in its Mobile Top 10 2024. Improper credential usage is first, insecure communication is fifth and insecure data storage is ninth. We set the scope of this assessment around that list.

In IPA's Top 10 Information Security Threats 2026, attacks that exploit system vulnerabilities rank fourth among threats to organizations, and an app can be one of those doors.

How far do we check? Seven areas, set out in a table

The detailed checks are carried out within the range agreed in the consent form. The right-hand column gives the matching OWASP item.

Area What we check Example of a problem OWASP
Data on the device Where data is stored, what is written to logs, how backups and caches are handled Member data stays on the device unencrypted M9
Traffic Whether it is encrypted, whether certificates are verified, whether the destination is valid Content that can be read on public Wi-Fi M5
Embedded secrets Keys, passwords and destinations written inside the app An extractable API key lets an outside service be used M1
Login and permissions The authentication flow, decisions made only on the device, where permission lines are drawn An ID that opens another person's data M3
App internals Resistance to analysis and tampering, configuration flaws, how WebView is used An app that is easy to rebuild as a fake M7, M8
Bundled components Versions of external libraries, matched against published vulnerabilities A known hole in a component that is no longer updated M2
Input and cryptography Validation of input, the cipher used and how keys are handled An outdated cipher, a fixed key M4, M10

Privacy handling (M6) is checked across all of the rows above: which data is collected, and for what purpose.

Each kind of hole has its own explainer. Reading insecure data storage, insecure communication, hard-coded secrets and reverse engineering first makes the report easier to follow.

To examine the server-side API that the app talks to in depth, there is a separate API assessment (from JPY 98,000, excl. tax, up to 10 endpoints). A website linked to the app falls under the web application assessment.

How do we check? A tool scan, then a person's review

We first scan the app broadly with tools. Embedded strings, component versions and the encryption settings of traffic are found faster and more completely by a machine.

Next, a person runs the app on a device and confirms each tool finding one by one. A tool only says something looks suspicious. It cannot judge whether that leads to real harm in your app. Screen transitions, behavior after login and permission lines are things only a person's eyes can read.

Ahead of the work, the consent form fixes the app, the test accounts and the period. We proceed in a way that does not touch real users' data. We do not assess other companies' apps.

How does this relate to standards for builders?

For Android, the Japan Smartphone Security Association (JSSEC) publishes its Secure Design and Secure Coding Guidebook. The 27 August 2025 edition is the 17th, counting from the first edition in 2012.

That document is a guide for developers who want to build safely from the start. An assessment is the outside check of whether the finished app is in that state. A standard for the build stage and a test of the finished product have different roles.

What does the report contain?

The report is in Japanese, and technical terms come with plain wording. It contains the following.

  • A summary an executive can read in a few minutes: the current state and what to fix first
  • A list of findings with a severity score (CVSS, 0 to 10, higher is more dangerous)
  • For each finding, where it is (screen, feature, destination) and what happens if it is left
  • Fixes written for developers, and the order to make them in
  • The result of the re-assessment after fixes (one is free)

If development is outsourced, you can hand the report straight to the development company.

What does it cost, and what changes the amount?

Item Price (all excl. tax) Contents
Smartphone app assessment from JPY 198,000 One iOS app and one Android app. Tool scan and a person's review, a report, one free re-assessment after fixes
API assessment (if ordered together) from JPY 98,000 Up to 10 endpoints
Individual vulnerability fix from JPY 10,000 per item Quoted by content

Two things move the amount.

  • Number of targets. One iOS and one Android app is the base. Beyond that we quote individually.
  • Features behind login. The more member screens, payments and features with separate permission levels, the more checking there is.

A formal quotation comes after the free consultation and after we see the result of the free assessment (a quick assessment made once you have signed the NDA and the consent form). All prices are on the pricing page. The free URL check shows what is visible from outside, which does not include the inside of an app. For the website your app connects to, use the free URL check to see its outside view, then contact us to agree an assessment scope for the app.

How does it proceed? The NDA comes first, the assessment after

  1. In the free consultation, we ask what the app is for and what worries you.
  2. We sign a non-disclosure agreement (NDA) before anyone touches the app.
  3. You sign the consent form, we run a quick assessment (the free assessment) and hand over an issue report.
  4. We quote the cost of fixing the issues found. When you agree, you place the order.
  5. We assess every item and fix what we can.
  6. We send a PDF with the details of each fix before delivery.
  7. You check behavior on the real screens, and we deliver. The month after delivery comes with free support.

Fixing the inside of an app is often done by the development company. In that case, pass them the report. We write it so that it explains how to fix each finding. The overall flow from first contact to delivery is also published.

Common questions about app assessments

The app passed store review and is on the store. Do we still need an assessment?

Store review checks that an app follows the rules. It does not find every secret embedded in the app or every weak way of storing data on the device.

Passing review and being safe are separate things. An app on the store is also an app that anyone can take apart.

Does the content differ between iOS and Android?

The viewpoints are shared. The places we look differ, because where data is stored and how permissions work are different on each platform. The price list assumes one app for each.

Do we have to hand over the source code?

An assessment basically runs the finished app and examines it. If you want a check that reads the source code itself, it is a separate menu, the source code assessment, quoted individually.

Frequently asked questions

How much does a mobile app assessment cost?

The smartphone app assessment is from JPY 198,000 (excl. tax, one iOS app and one Android app). The number of apps and the number of features behind login change the amount. A formal quotation follows the free assessment.

Can you assess only iOS or only Android?

The price list assumes one iOS app and one Android app. If you want only one of them, tell us in the free consultation and we will show the scope and the amount.

Is the API the app uses part of the assessment?

The safety of the app's traffic is covered. If you want the server-side processing at the other end examined in depth, consider the API assessment (from JPY 98,000, excl. tax, up to 10 endpoints) as well.

Will the assessment affect the app's users?

The consent form fixes the target, the period and the methods beforehand. We assess with test accounts, and we will discuss a setup that does not touch real customer data.

Does an assessment prove the app is safe?

No. An assessment confirms the state at that moment and is not a guarantee of safety. An app changes with every update, so we suggest assessing again before and after a major update.

Next step

The first step is the free URL check. Enter the URL of a website linked to the app, and it reads only what anyone can see from outside. No order or contract arises at that point.

To get a sense of the scope and cost for the app, contact us. We sign the NDA first, ask about the app and then show the scope and the amount.

Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.

Frequently asked questions

How much does a mobile app assessment cost?

The smartphone app assessment is from JPY 198,000 (excl. tax, one iOS app and one Android app). The number of apps and the number of features behind login change the amount. A formal quotation follows the free assessment.

Can you assess only iOS or only Android?

The price list assumes one iOS app and one Android app. If you want only one of them, tell us in the free consultation and we will show the scope and the amount.

Is the API the app uses part of the assessment?

The safety of the app's traffic is covered. If you want the server-side processing at the other end examined in depth, consider the API assessment (from JPY 98,000, excl. tax, up to 10 endpoints) as well.

Will the assessment affect the app's users?

The consent form fixes the target, the period and the methods beforehand. We assess with test accounts, and we will discuss a setup that does not touch real customer data.

Does an assessment prove the app is safe?

No. An assessment confirms the state at that moment and is not a guarantee of safety. An app changes with every update, so we suggest assessing again before and after a major update.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.