‍Once access to the mobile application is granted, all of the models/API endpoints are enumerated, if applicable, the source code is analyzed to look for misconfigurations and sensitive data exposed, the technology stack used is analyzed as well to look for potential CVEs, and the permissions schema is tested to look for broken access controls and privilege escalation possibilities. Overall, the test is conducted following the OWASP Top 10 Mobile methodology.

After scoping, the assessment team tries to access every page of the application and look for the different requests made. From that list, a set of possible attacks is made and then executed to prove impact. A usual requirement here is to look for vulnerabilities that allow a basic user to access either to an admin’s or to another user’s data.

A cloud engagement will look for different misconfigurations inside a Cloud environment that can turn a malicious insider task much easier. The assessment team will look for issues related to the authentication mechanism being used and the virtual assets inside the infrastructure, like database instances, containers, storage buckets and running applications. We will need access to the cloud environment with read only or security audit access to conduct testing. After we gain access to the Cloud, we run a couple of tools to look for both technical and user-generated misconfigurations.

After scoping, an asset discovery is performed to collect all of the active host + port combinations. Once done, we start looking for potential exploits either by searching CVEs associated with the technology stack behind the service running on a certain port, or by performing a set of standard attacks.
Additionally, we look for breached credentials which are still valid on different platforms.