Contact Us
Contact Us
Mobile Apps

Mobile App Security: An OWASP Mobile Checklist Before You Hit the App Store

An 18-point pre-release checklist built on OWASP MASVS and the Mobile Top 10: storage, network, authentication, APIs, supply chain and privacy.

JRC Software Team
6 min read
Mobile App Security: An OWASP Mobile Checklist Before You Hit the App Store

Unzip a release APK, run strings over it, and see what comes out. On apps that have never had a client-side review, it's common to find an API key, a staging URL or two, and a feature flag that unlocks an admin screen. The backend may have passed its pen test. The app sitting on a stranger's phone never got one.

That's why mobile app security needs its own pass. Your app runs on devices you don't control, where anyone determined can unpack the binary, read local storage on a rooted phone, proxy the traffic and replay API calls. Treat anything shipped in the app, from keys to business rules, as readable.

The checklist below gives product and engineering leads a structured way to review the client before release, with the OWASP mobile standards as the backbone.

Two OWASP references worth knowing

The OWASP Mobile Application Security Verification Standard (MASVS) sets baseline security and privacy requirements for mobile apps. OWASP links it to the Mobile Application Security Weakness Enumeration (MASWE) and the Mobile Application Security Testing Guide (MASTG), which holds the Android and iOS tests, techniques and demos used to verify the controls.

Alongside it, the OWASP Mobile Top 10 2024 ranks the most common mobile risks. Number one is improper credential usage, number two is inadequate supply chain security, and insecure data storage and insufficient cryptography sit at nine and ten.

A pattern we see often: the API is locked down and the client is forgotten. Tokens in SharedPreferences or UserDefaults, verbose logging left on in release builds, an analytics SDK collecting more than the privacy policy says. Each is cheap to fix before release and painful after.

The MASVS control groups in one table

The MASVS controls file lists eight groups with 24 controls in total. Use the groups as the headings of your review.

GroupWhat it coversExample control
MASVS-STORAGESensitive data on the deviceThe app securely stores sensitive data
MASVS-CRYPTOCryptography and keysKey management follows industry best practice
MASVS-AUTHAuthentication and authorisationSensitive operations need additional authentication
MASVS-NETWORKNetwork communicationAll network traffic is secured
MASVS-PLATFORMIPC, WebViews and the UIWebViews are used securely
MASVS-CODEPlatform version, updates, dependencies, inputOnly components without known vulnerabilities are used
MASVS-RESILIENCEReverse engineering and tamperingThe app implements anti-tampering mechanisms
MASVS-PRIVACYMinimisation, transparency, user controlThe app offers user control over their data

Not every app needs every control at the same depth. A banking or health app should take resilience seriously; a simple content app can write down why some controls don't apply. What matters is that the decision is deliberate and recorded.

Your pre-release mobile app security checklist

Run through this before each major release. Each item maps to a MASVS group or a Mobile Top 10 risk.

Storage

  1. No secrets, tokens or personal data in plain preferences, SQLite databases, logs or caches. Credentials go in the iOS Keychain or Android Keystore (MASVS-STORAGE, MASVS-CRYPTO).
  2. Sensitive screens are excluded from backups and blurred in the app switcher where appropriate, for example with FLAG_SECURE on Android (MASVS-STORAGE, MASVS-PLATFORM).
  3. Debug logging, test menus and staging endpoints are stripped from release builds, not just hidden.

Network

  1. All traffic uses TLS, with no cleartext exceptions left in network_security_config.xml or App Transport Security settings from development (MASVS-NETWORK).
  2. Where the risk justifies it, identity pinning is in place for endpoints you control, with a backup pin and a rotation plan so a certificate change doesn't brick the app.

Authentication and session

  1. No API keys or long-lived credentials hard-coded in the binary (Mobile Top 10 M1). If a key has to ship, scope it so it's useless on its own.
  2. Tokens are short-lived, refreshed securely and revoked on logout and password change (MASVS-AUTH).
  3. Biometric unlock is tied to a key in the Keystore or Keychain, not a callback that returns true or false (MASVS-AUTH).
  4. High-risk actions such as payments or changing contact details require step-up authentication.

APIs and backend

  1. Every authorisation decision happens on the server. Assume the app can be modified and every request replayed.
  2. APIs validate all input and return only the fields the screen needs (MASVS-CODE, Mobile Top 10 M4).
  3. Rate limiting and abuse monitoring cover login, sign-up and one-time code endpoints.

Code, dependencies and supply chain

  1. Third-party SDKs and packages are inventoried and scanned for known vulnerabilities (MASVS-CODE, Mobile Top 10 M2). Our guide to software supply chain security covers SBOMs and dependency scanning.
  2. The app can force an update when a critical fix ships (MASVS-CODE).
  3. Release builds are signed in a controlled pipeline, with signing keys kept off developer laptops.

Privacy

  1. The app asks only for the permissions and data it needs, and the App Store privacy labels and Google Play Data safety form match what the app and its SDKs actually collect (MASVS-PRIVACY, Mobile Top 10 M6).
  2. Users can view, export or delete their data where your obligations under the Privacy Act require it.

Resilience (risk-based)

  1. For apps handling money, health data or valuable content, consider root and jailbreak detection, tamper detection and obfuscation as defence in depth. They raise the cost of attack; they don't replace the controls above.

Fitting the checklist into your pipeline

A checklist used once before launch goes stale fast. Automate what you can: static analysis and dependency scanning on every pull request, secret scanning on every push, and a security test pass on release candidates. Keep the manual effort for design-level items like authorisation logic and privacy disclosures. If your organisation reports against the ASD Essential Eight, our article on Essential Eight for software teams shows how these pipeline controls line up.

How JRC Software secures mobile releases

Our mobile app development team builds these controls in from the first sprint, and our secure development engineers review apps built elsewhere. A review usually covers:

  • a MASVS-based review of the Android and iOS release builds, using MASTG techniques
  • API and authorisation testing against the backend the app depends on
  • an inventory of every SDK and what data each one sends, compared with your privacy disclosures
  • a findings report ranked by risk, with fixes your team can make before submission

The first thing we do is decompile your release builds and look for exactly what an attacker would: embedded secrets, endpoints, local storage and how tokens are handled. We'll also tell you what not to spend on first. Buying an app-shielding product rarely makes sense while the API still trusts whatever user ID the app sends.

If your launch date is close, book a discovery call for a mobile security review and get prioritised findings before you hit the App Store.

Frequently asked questions

What is OWASP MASVS?

MASVS is OWASP's Mobile Application Security Verification Standard, which sets baseline security and privacy requirements for mobile apps. It has eight control groups: storage, cryptography, authentication, network, platform interaction, code quality, resilience and privacy. Its companion, the Mobile Application Security Testing Guide (MASTG), provides the Android and iOS tests used to verify those controls.

How is the OWASP Mobile Top 10 different from MASVS?

The Mobile Top 10 is an awareness list of the most common mobile risks, such as improper credential usage, supply chain weaknesses and insecure data storage. MASVS is a verification standard with specific controls you can test against. Use the Top 10 to explain priorities to stakeholders and MASVS to structure the review and your acceptance criteria.

Do cross-platform apps need a different security review?

No, the controls are the same, but the details differ. Flutter and React Native apps still store data, call APIs and use platform features, so MASVS applies in full. Reviewers also check the framework layer: where the JavaScript bundle or compiled Dart code lives, how plugins reach native APIs, and whether secrets ended up in shared config such as .env files.

When should we run a mobile app security review?

Before the first public release, and again after major changes to authentication, payments or data handling. In between, rely on automated checks in your pipeline: static analysis, dependency scanning and secret scanning on every change. A late review is still worth doing, but findings are cheaper to fix while the feature is being built.

Mobile Apps

Book a mobile security review

Tell us where you're stuck and we'll come back with practical next steps.

Get in touch

Sources