Skip to content

Import MobSF Results

Normalize authorized MobSF results into a Mobile Application Security project.

What this solves

MobSF output can mix build settings, platform observations, code locations, and broad control suggestions that need application-specific interpretation.

How voiqq helps

Mobile Security Auto-populate converts supported MobSF output into reviewable voiqq candidates while preserving platform and build context and suggesting MASVS mappings.

Before you begin

  • An authorized Android or iOS assessment
  • A supported MobSF report for the assessed build
  • The correct Mobile Security Library and platform metrics
  • A sanitized source report

Step-by-step

  1. Open Auto-populate in the Mobile Security project
  2. Upload the MobSF output
  3. Review candidate titles, components, files, and evidence
  4. Confirm MASVS mappings and practical impact
  5. Accept legitimate candidates
  6. Assign remediation and validate against the correct application build

Check your result

  • Android and iOS context is not mixed
  • Evidence references the assessed version
  • Mappings correspond to the selected Library
  • False positives and informational observations are handled deliberately

Next steps

Open projects

Read the full guide

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.