Get Early Access

Importing Nessus Files

Last updated: 2026-03-29

Supported Format

JuturnaReport imports standard .nessus XML files exported from Nessus Professional or Nessus Essentials. Files up to 500 MB are supported. No network connection to a Nessus scanner is required — import is file-based only.

Importing a Scan

  1. Navigate to the Engagement where you want to add the scan.
  2. Click + Import Nessus Scan.
  3. A file picker opens. Select your .nessus file.
  4. JuturnaReport parses the file and shows a preview:
    • Detected scan name
    • Host count
    • Finding count
  5. Optionally override the Scan Name field with a custom label.
  6. Click Import.

A progress indicator appears while the file is processed. When complete, a confirmation message appears and the scan is listed under the engagement.

What Gets Imported

For each scan, JuturnaReport extracts and stores:

Per scan:

  • Scan name and metadata
  • Scanner type (Nessus)

Per host:

  • IP address, hostname, FQDN
  • Operating system
  • MAC address, NetBIOS name

Per finding:

  • Plugin ID and name
  • Original title, description, and solution
  • Severity (Critical / High / Medium / Low / Informational)
  • CVSS score and vector string
  • CVE reference IDs
  • Affected hosts with port, protocol, and service name

All data is stored in the local encrypted database. Nothing is sent externally.

Multiple Scans per Engagement

An engagement can hold multiple scans — useful if you ran separate scans for different subnets, phases, or tool configs. Import each .nessus file separately. When generating a report, you can select one scan or combine all scans from an engagement.

After Import

Once imported, findings are immediately available for review and triage:

  • Findings page — full list of findings for the scan, filterable by severity and status
  • Triage page — workflow view for bulk status and priority updates

See the Triage Workflow doc for next steps.

Troubleshooting

File rejected or parse error: Confirm the file is a valid .nessus XML export. Re-export from Nessus and try again.

File too large: Files over 500 MB are not supported. Consider splitting the scan in Nessus before exporting if you hit this limit.

Duplicate findings: Re-importing the same file creates a second scan record. Delete the duplicate scan from the engagement if this happens.