Skip to main content

Import Scan Results from Other Tools into SpartanX

Import third-party scan results (Nessus XML, SAST output) into SpartanX. Set a severity threshold and watch assets and vulnerabilities auto-populate a new collection.

Written by Antônio Baggio

SpartanX doesn't require you to abandon your existing security tooling. With support for over 150 scanners and security platforms, you can import vulnerability data from tools like Tenable Nessus, Qualys, or Acunetix — and bring it into SpartanX for validation, enrichment, and tracking.


Navigating to Imports

Go to the Data menu in the left-hand navigation and select "Imports." Click "New Import" to begin. You can import two types of data:

  • Vulnerability scan results — from network scanners, web application scanners, and similar tools

  • Code analysis results — from SAST tools, if you've run static analysis outside SpartanX

Uploading a File

Select the file you want to import. Give it a name (e.g., "Nessus Q2 Scan") and specify the tool that generated it — SpartanX supports over 150 tools, and the list covers all major vendors.

Set a severity threshold to control which findings are imported:

  • Critical — imports only critical-severity findings

  • High — imports high and critical findings

  • Informational — imports everything in the report, regardless of severity

Choose the threshold that matches your workflow. For focused attack validation, "High" is typically sufficient. For comprehensive ingestion, use "Informational."

Click "Run" to begin the import. The process typically takes a few minutes.


Reviewing Imported Data

Once the import completes, SpartanX creates a new collection containing the imported assets and their associated vulnerabilities. Navigate to Collections to find it.


In the vulnerabilities view, imported findings are marked as "Suspected" — meaning they have been reported by a third-party scanner but have not yet been validated by SpartanX. Some findings may be flagged as likely false positives based on SpartanX's analysis.


The associated assets are also created automatically. For example, an internal IP with an open SMB port would appear as a network asset with the relevant vulnerability attached.


What Comes Next: Targeted Attack Validation

Importing is the first step. The real power comes from running Targeted Attack Validation on the imported data — SpartanX will attempt to exploit the imported findings to confirm whether they are genuinely exploitable. This is covered in the next section.

Did this answer your question?