Mobile app security: a practical checklist

The most important security practices for mobile apps, based on industry guidance, covering data storage, authentication, network security, APIs and testing.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Mobile app security covers the app on the device, the network connection and the APIs behind it. Store sensitive data securely or not at all, use strong authentication, encrypt all traffic, protect and validate every API request on the server, keep secrets out of the app, update dependencies and test regularly against recognised standards such as the OWASP Mobile Application Security guidance.

Mobile apps handle personal details, payments, health information and business data. Attackers can download your app, inspect it, intercept traffic and probe your APIs. Security has to be designed in from the start, not added at the end.

Use recognised guidance

The OWASP Mobile Application Security project publishes the Mobile Application Security Verification Standard (MASVS), a testing guide and a Mobile Top 10 list of common risks. These provide a solid checklist for planning and testing.

Secure data storage

  • Store as little sensitive data on the device as possible.
  • Use the platform's secure storage, such as the iOS Keychain and Android Keystore, for tokens and keys.
  • Encrypt local databases containing sensitive information.
  • Don't write sensitive data to logs, caches or screenshots.
  • Clear sensitive data on logout.

Authentication and sessions

  • Use proven authentication standards, such as OAuth 2.0 and OpenID Connect, rather than custom schemes.
  • Support multi-factor authentication for sensitive apps.
  • Offer biometric sign-in backed by secure storage.
  • Use short-lived access tokens with secure refresh.
  • Invalidate sessions on the server at logout and after password changes.

Network security

  • Use HTTPS for all traffic with modern TLS.
  • Don't disable certificate validation, even in testing builds that might ship.
  • Consider certificate pinning for high-risk apps, with a plan for certificate updates.

Protect your APIs

The server is where security is enforced:

  • Authenticate and authorise every request on the server; never trust the app to enforce permissions.
  • Validate all input.
  • Rate-limit endpoints to slow abuse.
  • Return only the data the user is allowed to see.
  • Log and monitor suspicious activity.

Our guide to app backend options covers choosing a secure backend.

Keep secrets out of the app

Anything shipped inside an app can be extracted. Never embed private API keys, database credentials or admin secrets. Route sensitive calls through your own backend, where secrets live securely.

Code and dependencies

  • Keep third-party libraries and SDKs updated.
  • Review what data third-party SDKs collect.
  • Use code obfuscation where appropriate to slow reverse engineering, but don't rely on it for security.
  • Detect tampered apps or compromised devices for high-risk apps, while accepting that these checks can be bypassed.

Platform features

  • Request only the permissions you need.
  • Use app attestation services offered by Apple and Google to help verify requests come from your genuine app.
  • Follow platform security updates and guidelines.

Privacy

Security and privacy go together. Collect only necessary data, be transparent in privacy disclosures and give users control over their data.

Testing

  • Static analysis of code for common flaws.
  • Dynamic testing of the running app and its traffic.
  • API security testing.
  • Penetration testing by specialists for sensitive apps.
  • Regression tests for security fixes.

Security testing should be part of your wider mobile app testing process.

Incident response

Plan how you'll respond to a vulnerability or breach: who investigates, how you release a fix quickly, how you revoke compromised tokens and how you inform users and authorities if required.

Quick checklist

  • Sensitive data minimised and stored securely
  • Strong authentication and session management
  • HTTPS everywhere, certificate validation enforced
  • Server-side authorisation on every API call
  • No secrets in the app
  • Dependencies updated and reviewed
  • Minimal permissions
  • Regular security testing
  • Incident response plan

Security in the development process

Security works best as a habit, not a final check. Include threat modelling when designing new features, security-focused code reviews, automated dependency and secret scanning in your build pipeline and security testing before major releases. Train developers on common mobile risks so issues are prevented rather than fixed later.

Third-party SDKs

Every analytics, advertising or support SDK runs inside your app with your app's permissions. Review what each one collects and transmits, remove those you don't need and keep the rest updated.

Security for small teams

Small teams can't do everything at once. Start with secure storage, strong authentication, server-side authorisation and dependency updates, then add deeper testing as the app and its user base grow.

How we help

Our mobile app development team builds apps following recognised security standards. Our web app team secures the APIs and backends behind them, and our app development service includes security reviews and testing before launch.

Frequently asked questions

What is OWASP MASVS?

The Mobile Application Security Verification Standard, a widely used set of security requirements for mobile apps from the OWASP project.

Is it safe to store API keys in a mobile app?

Private keys and secrets shouldn't be stored in apps, because they can be extracted. Use your own backend to make sensitive calls.

Do I need penetration testing for my app?

For apps handling sensitive data or payments, independent penetration testing is strongly recommended.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides