-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add settings #11446
base: dev
Are you sure you want to change the base?
Add settings #11446
Conversation
* DD_SEARCH_SCM_TYPE - flag to enable/disable scm_type search * DD_DEFAULT_SCM_TYPE - default value for scm_type * DD_JIRA_CONNECT_METHOD - import path for jira connect method
DryRun Security SummaryThe pull request enhances DefectDojo's configuration by modifying the SCM type retrieval logic, adding timeout and deduplication settings, and introducing new configuration options to improve application security and vulnerability management. Expand for full summarySummary: The code changes in this pull request are focused on enhancing the configuration and functionality of the DefectDojo application, with a particular emphasis on improving the application security features. The changes include modifications to the logic for retrieving the SCM type, as well as the addition of new configuration settings related to timeouts and deduplication of findings. The changes to the The addition of new configuration settings related to timeouts and deduplication of findings are also important from an application security perspective. The timeout settings can help ensure that the application is able to handle requests in a timely manner, which is important for maintaining the performance and reliability of the application, especially in high-load scenarios. The deduplication configuration settings, on the other hand, can have a significant impact on the accuracy and effectiveness of the vulnerability management process, by allowing customization of the fields used for deduplication and the deduplication algorithms. Files Changed:
Code AnalysisWe ran
Overall Riskiness🔴 Risk threshold exceeded. We've notified @mtesauro, @grendel513. |
HI @FirePanda169 I am curious about how much we would gain from short circuiting the SCM search times. If the performance gain is negligible, I am unsure if these settings will be more helpful than they would be confusing |
Hi @Maffooch I checked the response time on loading 10 findings. The time is almost the same. But I don't have records in the DojoMeta model. I don't have a chance to check more thoroughly yet. |
@FirePanda169 thank you for doing the quick validation! Once you test with some DojoMeta that would trigger the code paths that these new settings are influencing, let me know what the performance savings are |
Description
Add settings:
DD_DEFAULT_SCM_TYPE makes it a little easier to work with scm-type, since most people use only one scm-type
DD_SEARCH_SCM_TYPE allows you to disable search to speed up the work a little
I think that for most it will be useful to use a combination
DD_SEARCH_SCM_TYPE = False
DD_DEFAULT_SCM_TYPE = "github" (or other)
Test results
...