Enterprise Edition

Downloading reports

  • Last updated: January 29, 2024

  • Read time: 3 Minutes

This section describes how to generate Standard and Compliance reports. You can send scan summary reports automatically, by email.

For more information about the contents of these reports, refer to Reports.

You can also export scan data as an XML file, for import into other tools or reporting frameworks.

Download a standard report

To download a standard report in HTML format:

  1. Open the Scans tab and select a scan.
  2. Select the Reporting tab.
  3. From the Report type drop-down menu, select Summary or Detailed.
  4. From the Include severities drop-down menu, select the severity levels you want to include in the report.
  5. To include false positives in the report, select Include false positive issues.
  6. Click Download.

Download a compliance report

To download a compliance report in HTML format:

  1. Open the Scans tab and select a scan.
  2. Select the Reporting tab.
  3. From the Report type drop-down menu, select OWASP Top 10: 2021 or PCI DSS V3.2.
  4. Click Download.

Note

Burp Suite Enterprise Edition's compliance reports do not guarantee compliance or non-compliance with any specific security standard.

Send scan summary reports automatically

After you configure a connection to an SMTP server, you can configure Burp Suite Enterprise Edition to automatically send scan summary reports:

  1. Open the Sites tab and select a site.
  2. In the Details tab, click Edit.
  3. In Scan settings, select the Scan notifications tab.
  4. In the Send scan summary reports by email section, enter an email address.
  5. To send the report to more than one email address, click and enter another address.
  6. To remove an email address, click the trash icon .
  7. Click Save.

Export issue data

To export issue data in XML format:

  1. Open the Scans tab and select a scan.
  2. Select the Reporting tab.
  3. From the Report type drop-down menu, select Export Issue Data.
  4. From the Include severities drop-down menu, select the severity levels you want to include in the report.
  5. To include false positives in the report, select Include false positive issues.
  6. To encode requests and responses in Base64, select Base64-encode requests and responses.
  7. Click Download.

Note

The XML file uses an internal DTD. If you're an author of interoperability code, we recommend that you review a sample report to obtain the current DTD. These XML elements are specific to the scan results:

  • The serialNumber element contains a long integer that uniquely identifies the individual issue instance. If you export issues several times from the same instance of Burp, you can use the serial number to identify incrementally new issues.
  • The type element contains an integer that uniquely identifies the issue type (such as SQL injection, or XSS). This value is stable across different instances of Burp. See the list of scan issue types for a list of all numeric type identifiers.
  • The name element contains the descriptive name for the issue type. See the list of scan issue types for a list of all issue names.
  • The path element contains the URL for the issue (excluding query string).
  • The location element includes both the URL and a description of the entry point for the attack, where relevant. For example, a specific URL parameter or request header.
  • The request and response elements have a base64 attribute, which contains a Boolean value to indicate whether the messages are Base64-encoded.

Related pages

Was this article helpful?