Mobile app scanning
Analyse mobile app builds for insecure storage, secrets and weak crypto.
Overview
The mobile engine inspects mobile application packages for common risks — hard-coded secrets, insecure data storage, weak transport security and unsafe configuration.
It helps mobile teams ship apps that protect user data on the device and over the network.
How it works
You upload or point SecNxt at the app build, and it inspects the package contents and configuration for security weaknesses, mapping each to a finding.
How to use it
- 1Choose 'Mobile App Scan' on the New scan screen.
- 2Provide the app build/package.
- 3Run the scan and review the findings.
- 4Fix and re-scan the next build.
When to use it
- Pre-store-submission security checks.
- Auditing an app for hard-coded keys or tokens.
Tips & best practices
- Scan release builds, not just debug builds — configuration often differs.
FAQ
- Which platforms are supported?
- Provide your platform's standard release package; the engine inspects the build artefacts.