Nexpose Reporting,
InsightVM Results in the Engagement
Nexpose report import for Rapid7 Nexpose and InsightVM XML exports. Every vulnerability lands as a scan issue with its hosts, CVEs, and exploit flag, ready to triage.
Import Once. Report From One Place.
Rapid7 Nexpose and InsightVM scan thoroughly and report for a vulnerability management program. A pentest client wants something different: a short list of confirmed vulnerabilities with proof. Neuron imports the XML Export and gets you there through triage.
The import reads the vulnerability definitions first, then joins every node's test results to them, so each issue arrives with the Rapid7 title, severity, CVSS score, description, solution, CVE references, and whether an exploit is known. Only positive results, vulnerable-exploited, vulnerable-version, and potential, come across.
Hosts are built from each node's address, DNS name, best OS fingerprint, and MAC address. Minimum Severity and Only Exploitable Findings narrow the import before it reaches the queue.
$ neuron import acme-insightvm.xml --tag external Importing into Acme External Q4 nexpose: 37 hosts, 412 positive tests✓ 88 scan issues queued for triage- 11:18 Finding Apache Tomcat AJP Ghostcat (CVE-2020-1938)
- 11:02 Import Nexpose: 37 hosts, 88 scan issues
- 11:01 Command neuron import acme-insightvm.xml
- 10:20 Import Masscan: 37 hosts, 96 ports
Why Nexpose Reporting Takes So Long
A Nexpose XML export splits each vulnerability in two. The test on the node only says that a vulnerability ID was found, while the title, severity, and remediation live in a definitions block at the end of the file. Reading it by hand means jumping between the two for every result.
The console's report templates help a remediation team prioritise, but they are not a pentest deliverable and their layout is not yours. So the useful parts get copied into a document one vulnerability at a time.
Meanwhile vulnerable-version results that rest on a banner sit next to vulnerable-exploited ones, and nothing records which of them a tester actually confirmed.
Everything Nexpose Produces, On the Engagement
Import Nexpose output from the browser or with neuron import, and it lands the moment the import finishes.
Hosts
Each node as a host with its address, DNS name, the highest-certainty OS fingerprint, and MAC address.
One Issue per Vulnerability
Each Rapid7 vulnerability ID as a single scan issue, with every affected host and port listed beneath it.
Definitions Joined In
Title, severity, CVSS score, description, and solution from the vulnerability definitions, attached to every issue automatically.
Positive Results Only
Vulnerable-exploited, vulnerable-version, and potential results are imported. Tests that came back not vulnerable are left out.
Exploit Flag
Vulnerabilities whose definition lists a known exploit are flagged, and Only Exploitable Findings imports just those.
CVE References
CVE IDs from each definition's references, so a library entry keyed on a CVE matches the issue whichever scanner found it.
How to Import Nexpose Results
- 01
Create an XML Export report
In the Nexpose or InsightVM console, create a report in the XML Export 2.0 format, scope it to the sites or assets you tested, and download it. Files in the original XML Export format import too.
- 02
Import it in the browser
In the engagement, choose Import, then Nexpose. Set Minimum Severity, tick Only Exploitable Findings if you only want vulnerabilities with a known exploit, and click Start Import.
- 03
Or import it from the terminal
neuron import recognises the NexposeReport format and sends it to the right importer. Add --tag to label every host the import creates.
$ neuron import acme-insightvm.xml --tag external - 04
Triage, then promote
Check vulnerable-version results against the target before trusting them, then promote confirmed issues into findings. Issues with an approved library match can be promoted in bulk.
Your Infrastructure. Your Data.
Neuron is self-hosted. Import Nexpose results from the browser or the CLI and they land on your own server, inside your network. Scan data never passes through a third-party cloud.
From Nexposeto the Final Report
Promoted Nexpose issues become findings with the hosts that are still affected and the remediation your team already approved in the Findings Library, rather than the console's generic solution text.
If the same network was also scanned with Nessus or Qualys, issues that share a CVE match the same library entry and link to a single finding, so the report never lists one vulnerability twice.
Once the client patches and you rescan for the retest, import the new XML Export. Vulnerabilities that no longer appear are marked Fixed, and a mistaken import can be undone with Rollback Import without touching anything already promoted.
Nexpose Integration FAQ
The questions teams ask most about Nexpose and Neuron.
How do I import Nexpose results into a pentest report?
Create a Nexpose report in the XML Export 2.0 format and import it into the Neuron engagement, in the browser or with neuron import. Every positive result becomes a scan issue with its hosts and CVEs, ready to confirm and promote into a finding.
Does Neuron support InsightVM exports?
Yes. InsightVM offers the same XML Export report formats as Nexpose, and Neuron imports them the same way. Hosts, vulnerabilities, CVEs, and exploit flags all come across.
Which Nexpose report format should I use?
XML Export 2.0. The original XML Export format also imports. Nexpose PDF, HTML, and CSV reports are not imported because they do not carry the definitions and per-node test results the import joins together.
Which Nexpose results are imported?
Only positive ones: vulnerable-exploited, vulnerable-version, and potential. Each is joined to its vulnerability definition so the issue has a title, severity, CVSS score, description, solution, and CVEs.
Can I import only exploitable Nexpose vulnerabilities?
Yes. Tick Only Exploitable Findings on the Nexpose import page and only vulnerabilities whose definition lists a known exploit are imported. Combine it with Minimum Severity to cut the queue down further.
Where does the Nexpose data go?
To your own self-hosted Neuron server, on the engagement it belongs to. Nothing passes through a third-party cloud.
More Neuron Integrations
Nessus Reporting and .nessus File Import
Vulnerability ScannersQualys Report Import for Pentest Reporting
Vulnerability ScannersOpenVAS Reporting and Greenbone Report Import
Vulnerability ScannersBloodHound Reporting and Attack Path Import
Active DirectoryPCAP Import: Hosts and Services From Captures
Network DiscoveryOpenAPI and Swagger Import for API Pentests
Web TestingNikto Reporting and Output Import
Web TestingAcunetix Report Import for Pentest Reports
Web TestingReady to Transform Your Security Practice?
See how Neuron helps security teams replace fragmented tools with a single platform for offensive security, bringing structure, visibility, and consistency to every engagement.
Platform