docs(connectors): Bright Security connector reference#15341
Draft
devGregA wants to merge 1 commit into
Draft
Conversation
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 <noreply@anthropic.com>
Contributor
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Bright Security section to the Pro connectors tool reference. Companion to connectors#760 + dojo-pro#2010. Story sc-13908.
Prerequisites (API key), the Location/Secret/Minimum-Severity mappings, and the whole-account model: each completed scan → a Record, each issue → a finding (severity/CVSS/CWE/remediation/endpoint/request-response, dynamic, dedupe on issue id). Placed alphabetically between Bitbucket and BurpSuite. Draft until the connector lands.