Mobile Security Auto-populate turns supported MobSF results into normal findings for Android and iOS assessment projects. The resulting candidates use the same assignments, comments, evidence, remediation, validation, and reporting workflow as manual findings.
How the integration works
voiqq parses supported MobSF output, normalizes technical records, suggests canonical MASVS controls, and keeps ambiguous mappings visible for professional review instead of forcing unrelated fields.
What you need
- A Mobile Application Security project configured for the assessed platform
- Authorized MobSF output for the correct application build
- Application version, package or bundle context, and assessment scope
- A sanitized report without signing secrets, credentials, or unnecessary personal data
A practical workflow
- Open Auto-populate in the Mobile Application Security project
- Upload the supported MobSF report
- Review parsed candidates and mapping warnings
- Accept relevant records and preserve build-specific evidence
- Validate control mapping, practical impact, remediation, and retest outcome
What enters the project
- Finding title, platform, component, file, and technical evidence
- Severity and source confidence
- Likely MASVS control and references
- Remediation, scanner metadata, and duplicate fingerprint
Continue with voiqq
Open Mobile Security workspace
Explore Mobile Application Security
voiqq uses OWASP MASVS 2.1.0 with 24 high-level controls across 8 official control groups. Where a mobile weakness needs more detail, it can also be mapped to the related official MASWE weakness beneath the MASVS control. MASTG remains a testing reference, not a substitute control catalogue.