docs: Pro set-based deduplication hash code fields for CWE/Vulnerability_Ids#15154
Merged
Conversation
This was referenced Jul 4, 2026
Merged
valentijnscholten
force-pushed
the
feat/dedupe-set-match-docs
branch
from
July 5, 2026 18:21
727b7cc to
1ca8895
Compare
valentijnscholten
changed the title
valentijnscholten
force-pushed
the
feat/dedupe-set-match-docs
branch
from
July 6, 2026 13:54
1ca8895 to
1bce7eb
Compare
valentijnscholten
changed the title
Maffooch
force-pushed
the
feat/cwe-vuln-id-consolidation
branch
from
July 14, 2026 01:07
354058e to
518df6c
Compare
Contributor
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
Bot
added
New Migration
Maffooch
force-pushed
the
feat/cwe-vuln-id-consolidation
branch
2 times, most recently
from
July 14, 2026 03:15
2f3a611 to
0b291ea
Compare
…+ CWE matchers) Document the Pro Tuner set-match hash-code fields: vulnerability_ids (exact), vulnerability_ids_partial/_subset, and cwes_partial/_subset — what each matches, how _partial/_subset are compared per pair rather than hashed, the empty-set behavior (abstain when another hashed field gates the pair; no match when the matcher is the sole field), and the config rules (a vulnerability IDs field may stand alone; CWE fields may not be the only criteria).
The token table listed cwes_partial/cwes_subset but omitted the bare `cwes` token (exact CWE set, folded into the hash like `vulnerability_ids`). Add the row, note it in the exact-matching sentence, and include `cwes` in the "CWE fields may not be the only criteria" rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Maffooch
force-pushed
the
feat/dedupe-set-match-docs
branch
from
July 14, 2026 03:56
7b81cfb to
9354609
Compare
github-actions
Bot
removed
New Migration
Contributor
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
Maffooch
marked this pull request as ready for review
July 14, 2026 04:02
blakeaowens
approved these changes
Jul 14, 2026
Maffooch
approved these changes
Jul 14, 2026
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
3 participants
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.
🔗 PR stack — CWE / vulnerability-ID consolidation (OSS)
Merge bottom-up:
👉 This PR: #15154
Documentation for the DefectDojo Pro set-match deduplication fields (Pro Tuner). Adds a "Set-based Hash Code Fields" section to the Pro deduplication tuning page covering the vulnerability-ID and CWE set matchers (
vulnerability_idsexact,vulnerability_ids_partial/_subset,cwes_partial/_subset), their empty-set behavior, and the configuration rules.Stack (merge bottom-up)
feat/vulnerability-id-type(autodetected vulnerability ID type + uniqueness) →devfeat/cwe-vuln-id-consolidation(multiple CWEs per finding) → stacked on feat(finding): copy finding fix + autodetected vulnerability id type + uniqueness constraint #15145feat/cwe-vuln-id-consolidation)The CWE matchers documented here rely on the
Finding_CWEmodel from #15143, so this PR is based on that branch. It accompanies the DefectDojo Profeat/dedupe-set-match-tokensPR (dojo-pro #1749), which implements the fields.