-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[docs] add Pro Finding Enhancements documentation #12310
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.
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
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
acee283
2.45.2 pro changelog
5473bfa
add nextgen finding enhancements documentation
cab672a
Merge branch 'bugfix' into docs-nextgen
Maffooch 36de8e1
Correcting messy conflict resolution
Maffooch da0b58e
Update docs/content/en/changelog/changelog.md
paulOsinski 4061bf4
Update docs/content/en/working_with_findings/finding_priority.md
paulOsinski 9207e58
Update finding_priority.md
paulOsinski File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,77 @@ | ||
| --- | ||
| title: "Finding Priority Enhancement (Pro)" | ||
| description: "How DefectDojo ranks your Findings" | ||
| weight: 1 | ||
| --- | ||
|
|
||
| Additional Finding filters are available in DefectDojo Pro to more easily triage, filter and prioritize Findings. | ||
|
|
||
| * Priority sorts Findings based on the context and importance of the Product they are stored in. | ||
| * Risk considers the Product's context, with a greater emphasis on the exploitability of a Finding. | ||
|
|
||
| ## Finding Priority | ||
|
|
||
| In DefectDojo Pro, Priority is a calculated field on Findings that can be used to sort or filter Findings according to Product-level metadata: | ||
|
|
||
| - Product's Business Criticality | ||
| - Whether the Product has an External Audience | ||
| - Whether the Product is Internet Accessible | ||
| - The Product's estimated revenue or user records count | ||
|
|
||
| DefectDojo Pro's Finding Priority assigns a numerical rank to each Finding according to this metadata, to provide users with a stronger context on triage and remediation. | ||
|
|
||
|  | ||
|
|
||
| The range of Priority values is from 0 to 1150. The higher the number, the more urgency the Finding is to triage or remediate. | ||
|
|
||
| Priority numbers can be used with other filters to compare Findings in any context, such as: | ||
|
|
||
| * within a single Product, Engagement or Test | ||
| * globally in all DefectDojo Products | ||
| * between a few specific Products | ||
|
|
||
| ## How Priority is calculated | ||
|
|
||
| Every Active finding will have a Priority calculated. Inactive or Duplicate Findings will not. | ||
|
|
||
| Priority is set based on the following factors: | ||
|
|
||
| #### Product-Level | ||
|
|
||
| - The assigned Criticality for the Product (if defined) | ||
| - The estimated User Records for the Product (if defined) | ||
| - The estimated Revenue for the Product (if defined) | ||
| - If the Product has External Audience defined | ||
| - If the Product has Internet Accessible defined. | ||
|
|
||
| All of these metadata fields can be set on the Edit Product form for a given Product. | ||
|
|
||
| #### Finding-Level | ||
|
|
||
| - Whether or not the Finding has an [EPSS score](/en/working_with_findings/intro_to_findings/#monitor-current-vulnerabilities-using-cves-and-epss-scores-pro-feature), this is automatically kept up to date for Pro customers | ||
| - How many Endpoints in the Product are affected by this Finding | ||
| - Whether or not a Finding is Under Review | ||
|
|
||
| If Product-level metadata is not set, the Priority level will follow the Severity for a given Finding: | ||
paulOsinski marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| - Critical = 90 | ||
| - High = 70 | ||
| - Medium = 50 | ||
| - Low = 30 | ||
| - Info = 10 | ||
|
|
||
| Currently, Priority calculation and the underlying formula cannot be adjusted. These numbers are meant as a reference only - your team's actual priority for remediation may vary from the DefectDojo calculation. | ||
|
|
||
| ## Finding Risk | ||
|
|
||
|  | ||
|
|
||
| The Risk column on a Findings table is another way to quickly prioritize Findings. Risk is calculated using a Finding's Priority level, but also factors in a Finding's exploitability to a greater degree. This is meant as a less granular, more 'executive-level' version of Priority. | ||
|
|
||
| The four assignable Risk levels are: | ||
|
|
||
|  | ||
|
|
||
| A Finding's EPSS / exploitability is much more emphasized in the Risk calculation. As a result, a Finding can have a both a high priority and a low risk value. | ||
paulOsinski marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| As with Finding Priority, the Risk calculation cannot currently be adjusted. | ||
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.
Uh oh!
There was an error while loading. Please reload this page.