Help for owners
I want my app checked for security before I launch it
Short answer
A pre-launch review is one engineer reading the app and its back end for common weaknesses: who can see whose data, where secrets are kept, how login works and how the app talks to the server. It lowers the risk and gives you a written list. It is not a certificate, and no review proves an app cannot be broken.
Does this sound like your situation?
- I am about to launch and nobody has looked at security.
- A customer or partner asked whether my app has been security tested.
- My developer says it is secure but cannot show me how they know.
- The app handles logins, payments or personal data.
- I do not know whether to pay for a full penetration test or something smaller.
Why does this happen?
Builders check that it works, not that it resists abuse
Most budgets go to features. Nobody is asked to try using the app in ways it was not meant for, such as asking for another customer's record.
Mobile apps have their own list of risks
OWASP publishes the Mobile Application Security Verification Standard. It groups checks into storage, cryptography, authentication, network communication, platform interaction, code quality, resilience and privacy, which is a useful frame for what a review looks at.
Confirmed by mas.owasp.org
The back end is where most damage happens
The app on a phone is only a window. Data is protected or not on the server, so a review that ignores the API misses the biggest risks.
Libraries carry known weaknesses
Packages the app depends on can have published vulnerabilities. A review checks which ones matter and which are noise.
Technical detail: npm audit fix runs, but the vulnerabilities are still listed
What can I do about it today?
- Write down what data the app holdsNames, emails, locations, payments, photos. The more sensitive it is, the more the review should cover.
- Ask your developer five plain questionsWhere are passwords and keys stored? Can one user ever see another's data? Is every connection encrypted? Who has admin access? Is there a backup?
- Check who holds the keysMake sure the hosting, the store accounts and the code are in your company's name, not someone's personal account.
- Do not launch with real customer data in a test setupSeparate test and live settings, so test shortcuts do not remain open after launch.
- Decide how deep you need to goA small app with simple data needs a focused review. An app with payments or health data may need a specialist firm on top.
When should I bring someone in?
- A partner, investor or app store asks for a written security statement.
- You hold payment, health or children's data.
- Your developer is also the only person who has checked it.
How do I handle it?
- Agree the scope in writingApp, API, servers and accounts: what is in, what is out, and how I will treat anything I find that is serious.
- Review the code and the setupI read how login, permissions, storage and server calls work and compare them with the OWASP mobile checklist.
- Test the back end like an outsiderI try requests the app would never send, such as asking for other users' data or sending requests too fast.
- Give you a ranked listEach finding is written in plain language with how bad it is, how to fix it and in what order.
- Fix and recheckIf you want, I make the fixes and check them again before launch, one change at a time with a backup.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is this a penetration test?
No. It is a code and setup review by one engineer with some hands-on testing of the back end. If you need a formal penetration test or certification, that is a specialist firm, and I can help you prepare for it.
Can you promise the app is secure afterwards?
No one can. A review finds and fixes known kinds of weakness and lowers risk. It does not prove nothing is left.
How long does it take?
It depends on the size of the app and its back end. I give a time estimate in the written scope after a short discovery call.
What is OWASP?
An open community that publishes security standards. Its mobile standard lists the areas a mobile app should be checked in.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
found 12 vulnerabilities (3 low, 6 moderate, 3 high)npm audit fix runs, but the vulnerabilities are still listedremote: error: GH013: Repository rule violations found for refs/heads/main. (a push blocked because it contains a secret)An API key or .env file was committed to a Git repositoryAccess to fetch at 'https://api.example.com/orders' from origin 'https://app.example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.The browser blocks your API response: no Access-Control-Allow-Origin header