Coastline’s methodology includes authenticated and non-authenticated testing and follows the OWASP Mobile Application Security Testing Guide (MASTG) and Mobile Application Security Verification Standard (MASVS) to validate strong security controls within code quality, handling of sensitive data, and interaction with the current environment. We first attempt to break into the mobile application itself and gain access to users’ accounts or the application’s administrator functionality. If unsuccessful in acquiring a valid account, we will ask for a temporary username and password. This lets us test from an authenticated user’s perspective. Once we have access and understand how the app works, our consultants investigate any areas of concern. Coastline’s mobile application assessment also includes testing for input validation flaws such as Cross-Site Scripting and SQL Injection.
Other common issues we test for include:
You get a detailed report covering every finding, with proof-of-concept evidence and step-by-step remediation. We walk your development team through the results on a readout call so they can reproduce what we found and fix it.
We test the app the way an attacker would take it apart: decompiling the binary, reading the source, pulling credentials and keys from storage, intercepting and modifying traffic between the app and your backend, and testing whether the server trusts what the app sends it. If your app stores data locally, handles authentication tokens, or talks to an API, we test all of it.
You choose the depth. We can test with no account at all, with a standard user, or with full source access for maximum coverage.