Skip to content

docs(threat-intel): KEV and EPSS from the bundle, the Intelligence Sources card, GHSA reach and vendor exploit claims - #16977

Open
devGregA wants to merge 11 commits into
DefectDojo:devfrom
devGregA:docs/threat-intel-phase0-dev
Open

devGregA wants to merge 11 commits into
DefectDojo:devfrom
devGregA:docs/threat-intel-phase0-dev

Conversation

@devGregA

@devGregA devGregA commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Documents the threat intelligence changes in DefectDojo Pro:

  • KEV and EPSS from the bundle. On a self-hosted instance with the KEV and EPSS lookups off, the threat intelligence bundle the instance already loads fills in CISA KEV and EPSS values, including on air-gapped installs. A lookup that is on always takes precedence. The pages also say what to expect on the first load after upgrading.
  • Intelligence Sources card. Superusers can see which bundle is loaded, the threat intelligence mode, how fresh each source is, and why a load failed, under Settings > System Settings. A stale or failing feed shows up there before it turns into unexpected scores.
  • GitHub advisory IDs. A finding reported only by its GHSA gets the linked CVE's exploit maturity, evidence and threat score.
  • Read-only CISA KEV fields and vendor exploit claims. Known Exploited (CISA KEV), Ransomware Used (CISA KEV) and KEV Date now come only from the CISA catalog, so KEV counts mean what they say. A scanner's, connector's or person's report is kept as Vendor Reported Exploited / Ransomware / Source, still raises priority, and is never overwritten by enrichment. The pages cover API behaviour, upgrade migration, filters, columns, rules, and which regulatory deadlines do and do not read a claim.

Pages:

  • Threat Intelligence
  • Findings (Pro)
  • Priority and SLA
  • Editing Findings
  • EPSS / KEV
  • Building Rules
  • Remediation SLAs
  • PAIN ratings setup
  • EU CRA setup
  • Air-gapped (Pro on-prem) and the Docker Compose air-gapped install
  • Filter index
  • Table customization
  • Generic Findings Import

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

devGregA and others added 11 commits November 12, 2026 17:07
…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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant