Repository navigation
Conversation
…HSA reach and vendor exploit claims Self-hosted Pro now fills in CISA KEV and EPSS values from the threat intelligence bundle when the lookups are off, shows the loaded bundle on an Intelligence Sources card, carries a CVE's evidence to findings reported only by a GitHub advisory ID, and keeps a scanner's own exploited/ransomware claim apart from CISA KEV as Vendor Reported values. Document each on the pages a customer reads for it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… and vendor claim text Carry the English change into the de, es, fr, it, ja, pt-br and zh-hans copies of the seven translated pages, keeping each page's terminology and the UI labels in English. New headings carry the English anchor as an explicit id, so links to them work in every language. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n the Vendor Reported fields Rewrite the vendor-evidence text to the revised Pro behaviour: Known Exploited (CISA KEV), Ransomware Used (CISA KEV) and the KEV date come only from CISA's catalog and cannot be set in the UI or API; scanner, connector and hand-set claims go to the Vendor Reported fields, which the finding form and API can set and clear; the upgrade moves existing non-CISA flags there with the source pre-upgrade; and regulatory deadlines read CISA KEV, EPSS and a direct decision only, so a vendor claim changes them only through a rule. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…evision Carry c8e22c8 into the de, es, fr, it, ja, pt-br and zh-hans copies of the Findings, Priority & SLA and Remediation Deadlines pages. The translated Priority & SLA pages predate the vulnerability response policies section, so its new sentence has no place there yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…SA KEV fields - Editing Findings and EPSS / KEV: the KEV values come only from CISA's catalog and cannot be set by hand; a person sets the Vendor Reported fields instead, and a rule reacting to a hand-set flag uses Vendor Reported Exploited. Filters use the (CISA KEV) labels and list the Vendor Reported filters, and self-hosted installs get KEV and EPSS from the threat intelligence bundle when the lookups are off. - Setting Up PAIN Ratings: the API example no longer writes known_exploited. The walkthrough now drives likely exploitability through EPSS on a finding without a CVE, because a KEV-listed CVE such as Log4Shell is capped to CISA's past due date on the FedRAMP VDR preset and hides every PAIN change. A vendor claim does not by itself change the PAIN or VDR result. - EU CRA setup: name the field Known Exploited (CISA KEV), as the UI does. - Building Rules: list the vendor fields in the rule item and give the condition builder's labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… / KEV and Building Rules Carry 7cfe8b6 into the de, es, fr, it, ja, pt-br and zh-hans copies. Most of these translations predate the Threat Intelligence form panel and the exploit-evidence field row, so the new text is added where it would sit rather than replacing an existing line; the unchanged English around it is still untranslated there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hange Match the pages to the final Pro behaviour: - the finding form shows CISA KEV read-only and offers Vendor Reported checkboxes; - API v2 refuses a change to the CISA fields with a 400 naming the vendor field, accepts a resent unchanged value, clears a claim on null, and keeps vendor_exploited_source read-only; - Mend's flags are no claim at all, and a duplicate's claim lands on the original finding; - the upgrade moves only flags that no CISA KEV listing backs, so CISA KEV counts can drop at the upgrade itself; - the flat VDR tiers, PAIN and the KEV cap never read a vendor claim; only a vulnerability response policy can take it in, through a rule that sets credible exploitability. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Carry c76df57 into the de, es, fr, it, ja, pt-br and zh-hans copies of the Findings, Remediation Deadlines, Editing Findings and Threat Intelligence pages. The translated Priority & SLA pages predate the vulnerability response policies section, so its sentence has no place there yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in the KEV/EPSS-from-bundle, Sources card, GHSA reach, read-only CISA KEV and vendor exploit claim docs (docs/threat-intel-phase0). Conflicts: - threat_intelligence*.md (8 languages): kept dev's "The vulnerability page" section (DefectDojo#16810) and the branch's "Findings reported by a GitHub advisory ID" section, in that order, before "Source ratings" / the scoring section. - editing_findings.md: kept the branch's split of the Threat Intelligence panel (read-only CISA KEV, Vendor Reported checkboxes) and carried over dev's added trigger "when a Finding is created or its vulnerability IDs change" (DefectDojo#16890). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… on-save trigger into the translations The em dashes on the lines this branch adds become colons or commas (EPSS / KEV "On the Finding / Sorting / Filtering" list, the PAIN field list, and the Internet-reachable sentence on Remediation SLAs), in every language. The Editing Findings translations now name the same triggers as the English page: a Finding being created or its vulnerability IDs changing (DefectDojo#16890). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…in Pro The card now shows the threat intelligence mode, when the intelligence was compiled (Intelligence As Of) and loaded, an expired notice beside the 14-day warning, and per-source status (included, left out, stale), key counts and notes. Say so, and why it helps, in all eight languages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Summary
Documents the threat intelligence changes in DefectDojo Pro:
Pages:
Languages: English, Deutsch, Español, Français, Italiano, 日本語, Português (Brasil), 简体中文.
Merge with the DefectDojo Pro release that carries dojo-pro#7406 (the first release after 3.5.200).
🤖 Generated with Claude Code