Inquiry Regarding Automated Crawling and User Input Simulation in MobSF Dynamic Analysis

[pentesty]

I hope this email finds you well. My name is Vinayak and I am currently working on integrating MobSF into our CI/CD pipeline to automate DAST scanning for mobile applications.

I am particularly interested in understanding how MobSF performs the following operations during dynamic analysis:

1. Automated Crawling: How does MobSF crawl through mobile application screens? Does it simulate user interactions and explore app functionalities automatically on a physical mobile device (both android and iOS)?
2. User Input Simulation: Is there a mechanism to provide or automate the required user inputs (e.g: credentials or form fields) for successful navigation through app screens?

Additionally, could you please provide insights or documentation that explains the internal process MobSF follows for these actions?

Your guidance would be invaluable in ensuring that we fully leverage MobSF’s capabilities for automated mobile application security testing.

Thank you for your time and support. I look forward to your response.

[github-actions]

👋 @pentesty
Issues is only for reporting a bug/feature request. For limited support, questions, and discussions, please join MobSF Slack channel
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.