FAQ
Questions deserve direct answers.
What gets assessed, what you share and where the work stops. Open a question for its answer.
What you share, and when.
No. It is a mobile app security assessment, not a penetration test or certification. We focus on the release build and say clearly what is outside that scope.
Android APK or AAB files and iOS IPA files. Send the build you intend to ship, not a development build.
No. We ask for the release artifact and a dependency lockfile. Your source code stays with you.
Not yet. We first confirm the scope, ownership proof, a mutual NDA and written authorisation. Technical work starts only after those are in place.
How a signal becomes a finding.
We inspect the release binary, run the app on a device and have a person review possible issues. Standard gives all 24 OWASP MASVS v2.1 controls a verdict or a written reason, with the MAS-L1 testing profile as the baseline. Controls outside MAS-L1 are checked where the release build allows. Other tiers have a written test scope.
No. A scanner alert is a candidate. A reviewer confirms or rejects it against the release build. Rejected candidates keep the reason in the report appendix.
The report names the control and explains why it could not be tested. It is not counted as a pass.
It is handled in an isolated analysis environment. Client artifacts are deleted within 30 days of report delivery.
What comes back, and what it costs.
A report with control results and human-confirmed findings. Each confirmed finding includes evidence, impact and a practical fix. There is also a short readout call.
Standard includes one retest within 60 days. For Beta, Indie and Enterprise, retest terms are agreed in the written scope.
Yes, while the beta is open. We ask for honest feedback, and the exact assessment scope is agreed before work begins.
Your request is saved and a person reviews it. We email you when your access is unlocked. Nothing technical starts until the scope and permissions are agreed.