A mobile assessment should cover the application, local data, platform controls and the APIs behind the mobile client.
Checklist
- Review authentication, session and token storage.
- Check local storage for credentials, tokens and sensitive business data.
- Assess transport security and certificate validation where applicable.
- Review exported components, deep links and platform permissions.
- Test API authorization independently of the mobile interface.
- Inspect sensitive logging, backup behavior and debug exposure.
- Validate cryptographic use and secret management.
- Document exploitable paths with reproducible evidence.
Preparing for an assessment
Share supported platforms, test builds, backend scope, important user journeys and any test-device constraints. Build signing, device access and test credentials are arranged privately after authorization.
Keep scope, access assumptions and exclusions explicit. Use redacted evidence and representative test data. Report what was verified, what remains uncertain and which checks could not be completed.
For backend authorization boundaries, pair the mobile review with API security testing.
Further reading
Related resources
Guides
OWASP Top 10 for Modern Applications
Use OWASP guidance to structure web testing around authentication, authorization and business workflows.
Read articleGuides
API Security Best Practices
A practical review of API identity, object authorization, schemas and evidence.
Read article