Updated Nexpose XML (Rapid7) Parser Documentation

[skywalke34]

Description
Update Nexpose XML (Rapid7) Parser documentation including Field Mapping Details, Special Processing Notes, Conversion details, and links.

Test results
No tests changed

Documentation
Documentation update only.

[dryrunsecurity]

No security concerns detected in this pull request.

---

All finding details can be found in the DryRun Security Dashboard.

[kiblik]

If we are doing this kind of rewrite, it might be a good idea to add information about https://docs.rapid7.com/insightvm/
InsightVM is a Nexpose instance connected to the cloud. The steps for obtaining the report are the same. Also, the report is the same.

[Maffooch]

Approving for now. Great suggestion from @kiblik

@skywalke34 please take a look at that comment

[skywalke34]

If we are doing this kind of rewrite, it might be a good idea to add information about https://docs.rapid7.com/insightvm/ InsightVM is a Nexpose instance connected to the cloud. The steps for obtaining the report are the same. Also, the report is the same.

Rapid7 Insight VM generates reports both from build-in report templates or custom SQL query reports. As I do not have access to a Rapid7 environment, if I include information on Insight VM, is it possible to know which standard report templates (i.e. "Top Remediation Report") that can be imported and parsed without error?
Should I also include information that custom reports are not supported?

[kiblik]

If we are doing this kind of rewrite, it might be a good idea to add information about https://docs.rapid7.com/insightvm/ InsightVM is a Nexpose instance connected to the cloud. The steps for obtaining the report are the same. Also, the report is the same.

Rapid7 Insight VM generates reports both from build-in report templates or custom SQL query reports. As I do not have access to a Rapid7 environment, if I include information on Insight VM, is it possible to know which standard report templates (i.e. "Top Remediation Report") that can be imported and parsed without error? Should I also include information that custom reports are not supported?

As far as I know, Nexpose and InsightVM use (almost) the same Console UI, and they share most of the documentation.
DD support XML Export 2.0 report generated by Nexpose (successfully tested). This should be true about InsightVM as well.
Top Remediations is a different kind of report. The output is PDF.
XML Export 2.0 is information which should user look for in Template section (see pictures in https://docs.rapid7.com/insightvm/creating-a-basic-report)

• https://docs.rapid7.com/nexpose/working-with-report-formats/
• https://docs.rapid7.com/insightvm/working-with-report-formats/

[Maffooch]

As far as I know, Nexpose and InsightVM use (almost) the same Console UI

Unless we are certain of this, I think we should leave off the insightVM note