> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/nexpose.md).

# Nexpose

PlexTrac supports importing files from **Nexpose** in XML [Export 2.0 format](https://docs.rapid7.com/nexpose/working-with-report-formats/). Nexpose is vulnerability management software developed by Rapid7. It monitors exposures in real-time, adapts to new threats with fresh data, and provides features such as adaptive security, integrated policy scanning, and intuitive remediation reports.&#x20;

<div align="left"><figure><img src="https://lh7-us.googleusercontent.com/0z4juOXrg5_HftDfuUuAfcWMA5_Uj-FI3lGoPWIXPMksEkDKQGLz0W7LwTcto-E8rnf95hdqjNn3S5lopRxhop0-jT9TZpOxf2pTJqSyvc3PEuYRErNqMdFKhAL6kZKEdhe3pgy08M4E4sw=s2048" alt="" width="188"><figcaption></figcaption></figure></div>

## Field Mappings <a href="#field-mappings" id="field-mappings"></a>

Below are the field mappings from Nexpose to PlexTrac, broken up by findings and assets. If a field is not listed, PlexTrac does not currently import it.

Tables include the following columns:

* **Nexpose Field:** the field name that appears in Nexpose
* **PlexTrac Field:** the field name that appears in PlexTrac
* **Direction:** displays the direction in the flow of data occurring for the integration

### Finding Field Mappings

<table><thead><tr><th width="162" align="center">Nexpose Field</th><th width="104" align="center">Direction</th><th width="143" align="center">PlexTrac Field</th><th align="center">Notes</th></tr></thead><tbody><tr><td align="center">Title</td><td align="center">-></td><td align="center">Finding Title</td><td align="center"></td></tr><tr><td align="center">Description</td><td align="center">-></td><td align="center">Description</td><td align="center"></td></tr><tr><td align="center">Solution</td><td align="center">-></td><td align="center">Recommendation</td><td align="center"></td></tr><tr><td align="center">Numerical Severity Sore Mapping</td><td align="center"></td><td align="center">Finding Severity</td><td align="center"></td></tr><tr><td align="center"><em>10</em> or <em>9</em></td><td align="center">-></td><td align="center"><em>Critical</em></td><td align="center"></td></tr><tr><td align="center"><em>8</em> or <em>7</em></td><td align="center">-></td><td align="center"><em>High</em></td><td align="center"></td></tr><tr><td align="center"><em>6</em> or <em>5</em></td><td align="center">-></td><td align="center">Medium</td><td align="center"></td></tr><tr><td align="center"><em>4</em> or <em>3</em></td><td align="center">-></td><td align="center"><em>Low</em></td><td align="center"></td></tr><tr><td align="center"><em>2</em> or <em>1</em></td><td align="center">-></td><td align="center"><em>Informational</em></td><td align="center"></td></tr><tr><td align="center">CVSS Score</td><td align="center">-></td><td align="center">Score Type</td><td align="center"></td></tr><tr><td align="center">CVSS Score</td><td align="center">-></td><td align="center">Label</td><td align="center"></td></tr><tr><td align="center">CVSS Score</td><td align="center">-></td><td align="center">Score Value</td><td align="center"></td></tr><tr><td align="center">CVSS Vector</td><td align="center">-></td><td align="center">Calculation</td><td align="center"></td></tr><tr><td align="center">CVE ID</td><td align="center">-></td><td align="center">CVE</td><td align="center"></td></tr><tr><td align="center">Reference Source</td><td align="center">-></td><td align="center">References</td><td align="center">Any hyperlinked URLs will be retained.</td></tr><tr><td align="center">Exploit ID</td><td align="center">-></td><td align="center"><em>Custom Field</em>: Nexpose Exploit Available</td><td align="center"></td></tr><tr><td align="center">PCI Severity</td><td align="center">-></td><td align="center"><em>Custom Field:</em> Nexpose PCI Compliance Status</td><td align="center"></td></tr><tr><td align="center">Risk Score</td><td align="center">-></td><td align="center"><em>Custom FIeld:</em> Nexpose Risk Score</td><td align="center"></td></tr><tr><td align="center">Vulnerability Id</td><td align="center">-></td><td align="center"><em>Custom Field:</em> Nexpose Vulnerability Id</td><td align="center"></td></tr></tbody></table>

### Asset Field Mappings

<table><thead><tr><th>Nexpose Field</th><th width="116" align="center">Direction</th><th>PlexTrac Field</th><th>Notes</th></tr></thead><tbody><tr><td>Node Address</td><td align="center">-></td><td>Asset Name</td><td></td></tr><tr><td>Device-Type</td><td align="center">-></td><td>Asset Type</td><td></td></tr><tr><td>Family</td><td align="center">-></td><td>Operating System</td><td></td></tr><tr><td>PCI Severity</td><td align="center">-></td><td>PCI Compliance</td><td></td></tr><tr><td>Node Address</td><td align="center">-></td><td>Known Ip Addresses</td><td></td></tr><tr><td>Endpoint Port</td><td align="center">-></td><td>Port</td><td></td></tr><tr><td>Endpoint Service</td><td align="center">-></td><td>Service</td><td></td></tr><tr><td>Endpoint Protocol</td><td align="center">-></td><td>Protocol</td><td></td></tr><tr><td>Services</td><td align="center">-></td><td>Known Hostnames</td><td>Detailed results  included in affected asset evidence. </td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/nexpose.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
