Burp Suite Enterprise

Application Security

Overview

The Burp Suite Enterprise connector connects to a Burp Suite Enterprise Edition server and synchronizes the sites, scans, issues (findings), and shared issue definitions discovered by those scans. Issue and scan data is retrieved through the Enterprise GraphQL API, while issue definitions are retrieved from the Enterprise REST knowledge base. Findings are mapped to dynamic application-security findings, definitions to shared finding definitions, scans to assessments, and sites to web application assets.

Data Category: Application Security

Data retrieved from Burp Suite Enterprise

Connector Object	Required	Maps to Data Model
Issue	Yes	Dynamic Code Finding
Issue Definition	Yes	Dynamic Code Finding Definition
Scan	Yes	Assessment
Site	Yes	Site

Model relationships

note

For detailed steps on how to view the data retrieved from Burp Suite Enterprise in the Brinqa Platform, see How to view your data.

Setup

Connection settings

When setting up a data integration, select Burp Suite Enterprise from the Connector dropdown and provide the following:

Setting	Required	Default	Description
Server URL	No	—	Burp Suite server URL
API Key	No	—	Burp Suite API key
Page size	No	—	Maximum number of records to get per API request
SSL / TLS	No	—	Skip certificate verification

Authentication

Element	Value
Method	API Key

The connector authenticates with a Burp Suite Enterprise API key. The key is used in two ways:

1. As a bearer-style value in the Authorization request header on every request.
2. As a path segment in the base URL for REST calls — REST requests are issued against /api/{apiKey}/{apiVersion}/... (current API version v0.1).

GraphQL requests are issued against the /graphql/v1 endpoint relative to the configured server URL.

Endpoints

Method	URL	Purpose
POST	{serverUrl}/graphql/v1	Sites, scans, and issues (GraphQL).
GET	{serverUrl}/api/{apiKey}/v0.1/knowledge_base/issue_definitions	Issue definitions (REST knowledge base).

Request Headers

Header	Value
Authorization	{apiKey}
Content-Type	application/json

Request Body (GraphQL)

{
  "query": "{ scans(limit: 1) { id } }",
  "variables": {}
}

Sample Response (GraphQL connectivity test)

{
  "data": {
    "scans": [
      { "id": "1" }
    ]
  }
}

Response Fields

Field	Description
data	Root object containing the requested query result.
data.scans	List of scans (used by the connectivity test).
data.scans[].id	Scan identifier.

The same API key is reused on every subsequent GraphQL and REST request via the Authorization header (and via the URL path for REST), so no token exchange or refresh step is required.

Sync Behavior

The connector supports incremental (delta) syncs. It maintains a sync token between runs and applies it as an incremental timestamp filter, so each run re-processes only the records that changed after the previous sync. The initial run retrieves the complete data set; later runs are incremental. The specific timestamp field applied to each object is documented under that object's Sync Duration Parameter.

How to obtain Burp Suite Enterprise credentials

Generate a Burp Suite Enterprise API key

For the connector to use the Burp Suite Enterprise API, you must provide an API key. Burp Suite Enterprise does not allow for retrieval of an existing API key. To create a new API user and generate an API key, follow these steps:

1. Log in to your organization's Burp Suite Enterprise server as an administrator.

2. Navigate to Team > Add a new user.

3. Enter the name, username, and email address for the user.

4. For the login type, select API key.

5. Click Save.

   A window displays with your API key. You cannot view the key after this, so copy the key and save it to a secure location.

Note: If you do not have the permissions to create an API key, contact your Burp Suite Enterprise administrator. For additional information, see Burp Suite Enterprise documentation.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Issue

Source Field Name	SDM Attribute
Folder association (issue UID)	FOLDER_ID
Folder.name	FOLDER_NAME
IssueResource.confidence / display_confidence	CONFIDENCE
IssueResource.description_html (HTML stripped to text)	SUMMARY
IssueResource.issue_type.name	NAME
IssueResource.issue_type.type_index	TYPE
IssueResource.novelty	PROVIDER_STATUS
IssueResource.novelty	SOURCE_STATUS
IssueResource.novelty	STATUS
IssueResource.novelty	STATUS_CATEGORY
IssueResource.origin	ORIGIN
IssueResource.path	PATH
IssueResource.request	REQUEST
IssueResource.response	RESPONSE
IssueResource.serial_number	UID
IssueResource.severity	SEVERITY
IssueResource.severity	SOURCE_SEVERITY
IssueResource.severity	SEVERITY_SCORE
ScanResource.agent.name	AGENT_NAME
ScanResource.end_time	LAST_FOUND
ScanResource.id	ASSESSMENT
ScanResource.scan_target.id	TARGETS
SiteObject.name / ScanResource.scan_target.name	SITE_NAME

Issue Definition

Source Field Name	SDM Attribute
IssueDefinitionResource.description (HTML to text)	DESCRIPTION
IssueDefinitionResource.issue_type_id	UID
IssueDefinitionResource.name	NAME
IssueDefinitionResource.references + classification URLs	REFERENCES
IssueDefinitionResource.remediation (HTML to text)	RECOMMENDATION
IssueDefinitionResource.vulnerability_classifications	CLASSIFICATIONS
IssueDefinitionResource.vulnerability_classifications	WEAKNESSES
IssueDefinitionResource.vulnerability_classifications	CWE_IDS
IssueDefinitionResource.vulnerability_classifications	ATTACK_PATTERNS

Scan

Source Field Name	SDM Attribute
Folder association (scan UID)	FOLDER_ID
Folder.name	FOLDER_NAME
ScanResource.agent.name	AGENT_NAME
ScanResource.end_time	END_TIME
ScanResource.id	UID
ScanResource.scan_target.id	TARGETS
ScanResource.start_time	START_TIME
ScanResource.status	STATUS
SiteObject.name / ScanResource.scan_target.name	SITE_NAME

Site

Source Field Name	SDM Attribute
derived	CATEGORIES
derived (sync time)	LAST_CAPTURED
SiteObject.ephemeral	EPHEMERAL
SiteObject.id	UID
SiteObject.name	DESCRIPTION
SiteObject.name (falls back to id)	NAME
SiteObject.parent_id	PARENT_ID
SiteObject.scope_v2.start_urls	START_URLS
SiteObject.scope_v2.start_urls	HOSTNAMES

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Issue

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: See connector README

query scans($offset: Int, $limit: Int) {
  scans(offset: $offset, limit: $limit) {
    id
    status
  }
}

Issue Definition

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: See connector README

Scan

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: See connector README

query GetScan($scanId: ID!) {
  scan(id: $scanId) {
    id
    scan_target { id name }
    start_time
    end_time
    status
    agent { id name }
    scan_configurations { id name }
    scope_v2 { start_urls }
  }
}

Site

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: See connector README

query GetSiteTree {
  site_tree {
    sites { id parent_id name }
    folders { id name }
  }
}

Changelog

Changelog

The Burp Suite Enterprise connector has undergone the following changes:

Version	Description	Migration Steps
3.1.8	Improvements - Connector-sourced attribute values now take precedence over non-connector data channels (manual edits, bulk imports, UI input) when the platform consolidates records, so Burp Suite data is no longer overridden by lower-priority sources. Bug Fixes - Scan "Start time"/"End time" and Issue "Last found" are now stored as proper timestamps instead of numeric epoch values, so date-based filtering, sorting, and display behave correctly.	• Scan, Issue: the attributes listed above changed type. Re-sync the Burp Suite Enterprise connector to repopulate these records with the corrected types.
3.1.7	New Features - Site records now include "Ephemeral" and "Parent ID", providing additional context about each site's nature and its place in the site hierarchy.	• Site: the unique identifier used for Site records changed. Re-sync the Burp Suite Enterprise connector and purge any orphaned Site records to avoid duplicates.
3.1.6	New Features - Finding status is now reported with greater fidelity: a provider status value (the raw status as reported by Burp Suite) is captured alongside the normalized status and status category. - Site records now include a "Last captured" timestamp indicating when the site was most recently captured during scanning. Improvements Dependency Upgrades - Updated underlying storage and supporting libraries.	• Issue: finding status attributes were re-worked (a new provider status was added and status values are now derived differently). Re-sync the Burp Suite Enterprise connector to repopulate findings with the updated status values.
3.1.5	New Features - Scans are now associated with their individual scan targets, so multi-target scans correctly attribute findings to each target. Improvements - The Site "Included urls" attribute was renamed to "Start urls" to better reflect the scan scope it represents.	• Site: the "Included urls" attribute was renamed to "Start urls". Re-sync the Burp Suite Enterprise connector to repopulate Site records under the new attribute.
3.1.4	Improvements - Site records are now identified by their hostnames (derived from the scan scope) rather than a single URL, improving how sites are matched and de-duplicated.	• Site: the identifying attributes for Site records changed. Re-sync the Burp Suite Enterprise connector and purge any orphaned Site records to avoid duplicates.
3.1.3	Improvements Dependency Upgrades - Updated supporting libraries.	N/A
3.1.2	Improvements Dependency Upgrades - Updated supporting libraries.	N/A
3.1.1	Improvements Dependency Upgrades - Updated supporting libraries.	N/A
3.1.0	Overview The Burp Suite Enterprise connector integrates with Burp Suite Enterprise Edition to synchronize sites, scans, and the security issues and issue definitions discovered during scanning. Category: Application Security Models	N/A
3.0.4	No changes in this release.	N/A
3.0.3	No changes in this release.	N/A
3.0.2	No changes in this release.	N/A
3.0.1	No changes in this release.	N/A
3.0.0	No changes in this release.	N/A