-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[docs] Prioritization Engine adjustments #13581
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 all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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.
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
62 changes: 62 additions & 0 deletions
62
docs/content/en/working_with_findings/priority_adjustments.md
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,62 @@ | ||
| --- | ||
| title: "Adjusting Priority and Risk (Pro)" | ||
| description: "Change weighting of Priority and Risk calculations" | ||
| weight: 2 | ||
| --- | ||
|
|
||
| DefectDojo Pro's Priority and Risk calculations can be adjusted, allowing you to tailor DefectDojo Pro to match your internal standards for Finding Priority and Risk. | ||
|
|
||
| ## Prioritization Engines | ||
|
|
||
| Similar to SLA configurations, Prioritization Engines allow you to set the rules governing how Priority and Risk are calculated. | ||
|
|
||
|  | ||
|
|
||
| DefectDojo comes with a built-in Prioritization Engine, which is applied to all Products. However, you can edit this Prioritization Engine to change the weighting of **Finding** and **Product** multipliers, which will adjust how Finding Priority and Risk are assigned. | ||
|
|
||
| ### Finding Multipliers | ||
|
|
||
| Eight contextual factors impact the Priority score of a Finding. Three of these are Finding-specific, and the other five are assigned based on the Product that holds the Finding. | ||
|
|
||
| You can tune your Prioritization Engine by adjusting how these factors are applied to the final calculation. | ||
|
|
||
|  | ||
|
|
||
| Select a factor by clicking the button, and adjust this slider allows you to control the percentage a particular factor is applied. As you adjust the slider, you'll see the Risk thresholds change as a result. | ||
|
|
||
| #### Finding-Level Multipliers | ||
|
|
||
| * **Severity** - a Finding's Severity level | ||
| * **Exploitability** - a Finding's KEV and/or EPSS score | ||
| * **Endpoints** - the amount of Endpoints associated with a Finding | ||
|
|
||
| #### Product-Level Multipliers | ||
|
|
||
| * **Business Criticality** - the related Product's Business Criticality (None, Very Low, Low, Medium, High, or Very | ||
| High) | ||
| * **User Records** - the related Product's User Records count | ||
| * **Revenue** - the related Product's revenue, relative to the total revenue of the Product Type | ||
| * **External Audience** - whether or not the related Product has an external audience | ||
| * **Internet Accessible** - whether or not the related Product is internet accessible | ||
|
|
||
| ### Risk Thresholds | ||
|
|
||
| Based on the tuning of the Priority Engine, DefectDojo will automatically recommend Risk Thresholds. However, these thresholds can be adjusted as well and set to whatever values you deem appropriate. | ||
|
|
||
|  | ||
|
|
||
| ## Creating New Prioritization Engines | ||
|
|
||
| You can use multiple Prioritization Engines, which can each be assigned to different Products. | ||
|
|
||
|  | ||
|
|
||
| Creating a new Prioritization Engine will open the Prioritization Engine form. Once this form is submitted, a new Prioritization Engine will be added to the table. | ||
|
|
||
| ## Assigning Prioritization Engines to Products | ||
|
|
||
| Each Product can have a Prioritization Engine currently in use via the **Edit Product** form for a given Product. | ||
|
|
||
|  | ||
|
|
||
| Note that when a Product's Prioritization Engine is changed, or a Prioritization Engine is updated, the Product's Prioritization Engine or the Prioritization Engine itself will be "Locked" until the prioritization calculation has completed. | ||
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.