> 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/burp-suite.md).

# Burp Suite

**Burp HTML is not supported as of Release 3.0 (23 April 2026).**

PlexTrac supports importing XML files from **Burp Suite Professional** and **Burp Suite Community** product offerings. Burp Suite is a software tool for web application security testing that helps security professionals and developers identify and exploit security vulnerabilities.

{% hint style="info" %}
Responses will be trimmed if HTML is used.
{% endhint %}

Below are the mappings of fields and any reference notes to provide context. If a field is not listed, PlexTrac does not currently import it. 

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FLheCFfnf038R48qUNkXF%2Fburpsuite.jpg?alt=media&amp;token=21af3061-2184-4508-a0c4-8279e3f65ca9" alt=""><figcaption></figcaption></figure></div>

## Finding Field Mappings

If a field is not listed, PlexTrac does not currently import it.&#x20;

<table data-full-width="false"><thead><tr><th>PlexTrac Field</th><th>Burp Path</th><th>Notes</th></tr></thead><tbody><tr><td>Finding Title</td><td>issue/name</td><td></td></tr><tr><td>Severity</td><td>issue/severity</td><td>maps "Information" to "Informational"</td></tr><tr><td>References</td><td>issue/vulnerabilityClassifications</td><td>removes the chars</td></tr><tr><td>References</td><td>references</td><td></td></tr><tr><td>Finding Description</td><td>issue/issueBackground</td><td></td></tr><tr><td>Evidence</td><td>issue/issueDetail</td><td></td></tr><tr><td>Finding Status</td><td>"Open"</td><td></td></tr><tr><td>Recommendations</td><td>remediationBackground</td><td></td></tr><tr><td>CWE ID</td><td>vulnerabilityClassifications</td><td></td></tr></tbody></table>

## Asset Field Mappings&#x20;

| PlexTrac Field        | Burp Path                      |
| --------------------- | ------------------------------ |
| Asset                 | issue/path                     |
| Hostname              | <https://issue/path>           |
| Known IP Addresses    | issue/host\@ip                 |
| Evidence              | issue/requestresponse/request  |
|                       | issue/requestresponse/response |
| Vulnerable Parameters | vulnerableParameters           |

Please note that vulnerable parameters vary based on the URL.&#x20;

PlexTrac users will now see additional path details on Asset names and asset metadata fields, ensuring findings are accurately communicated for unique web app assets.

## Parent Asset Field Mappings

| PlexTrac Field     | Burp Path       |
| ------------------ | --------------- |
| Asset              | issue/host/path |
| Hostname           | issue/path      |
| Known IP Addresses | issue/host\@ip  |

## Additional Information

* [Burp Suite Professional](https://portswigger.net/burp/pro)
* [Burp Suite Community](https://portswigger.net/burp/communitydownload)
* [Burp Suite Documentation](https://portswigger.net/burp/documentation)


---

# 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/burp-suite.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.