<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scoring &amp; Prioritization on DefectDojo Documentation</title><link>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/</link><description>Recent content in Scoring &amp; Prioritization on DefectDojo Documentation</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2025 DefectDojo, Inc.</copyright><lastBuildDate>Mon, 19 Oct 2026 06:03:12 +0000</lastBuildDate><atom:link href="https://beta-docs.defectdojo.com/triage_findings/finding_scoring/index.xml" rel="self" type="application/rss+xml"/><item><title>CVSS Version Support</title><link>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/cvss_support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/cvss_support/</guid><description>&lt;p&gt;DefectDojo supports CVSS metadata on Findings, including the CVSS 4.0 standard. This page describes which CVSS versions are stored end-to-end, where you can enter or view them, and what to expect from parser-side coverage.&lt;/p&gt;</description></item><item><title>EPSS / KEV</title><link>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/epss_kev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/epss_kev/</guid><description>&lt;p&gt;DefectDojo Pro automatically enriches your Findings with two external threat-intelligence sources — &lt;strong&gt;EPSS&lt;/strong&gt; and &lt;strong&gt;CISA KEV&lt;/strong&gt; — so that prioritization reflects how likely a vulnerability is to be exploited, not just its CVSS severity. Both sources match to Findings by &lt;strong&gt;CVE&lt;/strong&gt;, refresh on a &lt;strong&gt;daily schedule&lt;/strong&gt;, and feed directly into each Finding&amp;rsquo;s computed &lt;strong&gt;priority&lt;/strong&gt; score.&lt;/p&gt;</description></item><item><title>Reachability</title><link>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/reachability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/reachability/</guid><description>&lt;p&gt;A Critical CVE in code your application never calls is not the same risk as
the same CVE on a live request path. &lt;strong&gt;Reachability&lt;/strong&gt; captures that
difference: DefectDojo Pro records whether each Finding&amp;rsquo;s vulnerable code can
actually be reached, shows you where that conclusion came from, and feeds it
into the Finding&amp;rsquo;s computed &lt;strong&gt;priority&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Asset Exposure</title><link>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/asset_exposure/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/triage_findings/finding_scoring/asset_exposure/</guid><description>&lt;p&gt;A Critical vulnerability on a service anyone on the internet can reach is not the same
risk as the same vulnerability on an isolated internal system, or on a branch nobody has
deployed. &lt;strong&gt;Asset Exposure&lt;/strong&gt; captures both differences: DefectDojo Pro records how
reachable each asset is from outside, whether each Finding&amp;rsquo;s code is actually running in
production, shows you where those conclusions came from, and feeds both into the Finding&amp;rsquo;s
computed &lt;strong&gt;priority&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>