From 7e4a24a6df00de2ebe1baeeeae2173cbf484b9e7 Mon Sep 17 00:00:00 2001 From: Greg Anderson Date: Wed, 22 Jul 2026 21:46:57 -0600 Subject: [PATCH] docs(connectors): Bright Security connector reference Document the Bright Security (brightsec) DAST connector: the API-key prerequisite, the Location/Secret/Minimum-Severity mappings, and the whole-account model (completed scan -> Record; each issue -> finding, severity/CVSS/CWE/remediation/endpoint/request-response, dynamic, dedupe on issue id). Companion to connectors#760 and dojo-pro#2010. sc-13908 Co-Authored-By: Claude Opus 4.8 --- .../connectors/connectors_tool_reference.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/content/import_data/pro/connectors/connectors_tool_reference.md b/docs/content/import_data/pro/connectors/connectors_tool_reference.md index 1ba6cb02969..87bc8f7fec6 100644 --- a/docs/content/import_data/pro/connectors/connectors_tool_reference.md +++ b/docs/content/import_data/pro/connectors/connectors_tool_reference.md @@ -208,6 +208,24 @@ Only Bitbucket Cloud (bitbucket.org) is supported. Bitbucket Server reached end Each repository becomes a Record named after the repository, grouped by its Bitbucket **project**. +## **Bright Security** + +The Bright Security connector uses the [Bright](https://brightsec.com) (formerly NeuraLegion) API to import **DAST findings**. DefectDojo discovers every scan the token can access and creates a Record for each completed scan, then imports that scan's issues as findings. + +#### Prerequisites + +You will need a Bright **API key**, created in the Bright app under **User settings → API keys** (an `Org` or personal key). The key is sent in the `Authorization: Api-Key` header and is never logged. + +#### Connector Mappings + +1. Leave the **Location** field blank to use `https://app.brightsec.com`, or enter your Bright host explicitly. +2. Enter the Bright API key in the **Secret** field. +3. Optionally, set a **Minimum Severity** to limit which findings are imported. + +DefectDojo maps each completed **scan** to a Record and each **issue** to a finding: the severity comes from Bright's own rating (Critical/High/Medium/Low), the CVSS score, CWE and remediation are carried over, the affected entry point becomes the endpoint, and the request/response evidence is included in the description. Findings are recorded as dynamic findings and de-duplicated on Bright's issue id. + +See the [Bright API documentation](https://docs.brightsec.com/) for more information. + ## **BurpSuite** DefectDojo’s Burp connector calls Burp’s GraphQL API to fetch data.