Skip to content

docs(connectors): document the YesWeHack severity fallback and status mapping #15930

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Maffooch merged 1 commit into from
Sep 14, 2026
+14 −1
Merged

docs(connectors): document the YesWeHack severity fallback and status mapping #15930

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion docs/content/connectors/toolreference/yeswehack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,17 @@ You will need a YesWeHack **Personal Access Token (PAT)**. Read access to your p
2. Enter your Personal Access Token in the **Secret** field.
3. Optionally, set a **Minimum Severity** to limit which findings are imported. Findings below the selected severity will not be imported.

DefectDojo creates a separate Record for each program your token can access, and imports each report as a finding. The finding's severity is taken from the report's CVSS rating (falling back to the triage priority), and its status reflects the report's workflow state — for example, resolved reports are imported as mitigated, and reports marked invalid or out of scope are imported as inactive.
DefectDojo creates a separate Record for each program your token can access, and imports each report as a finding. The finding's severity is taken from the report's CVSS rating, falling back to the triage priority, and then to the report's numeric CVSS score.

The finding's status reflects the report's workflow state:

| YesWeHack workflow state | Finding status |
|--------------------------|----------------|
| New, Under Review, Reopen Under Review, Need More Info | Active |
| Accepted, Ask for fix verification | Active, Verified |
| Resolved, Auto Close | Inactive, Mitigated |
| Won't Fix | Inactive, Risk Accepted |
| Invalid, Not Applicable, Spam | Inactive, False Positive |
| Duplicate | Inactive, Duplicate |
| Out Of Scope, RTFS | Inactive, Out of Scope |
| Informative | Inactive |
Loading