Skip to content
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

set Dynamic finding to false by default in add finding manually to test #9794

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

FelixHernandez
Copy link
Contributor

set Dynamic finding (DAST) to false by default in add finding manually to test

[sc-3143]

Description

The initial data for the form in Add finding manually for test, now changes DAST field to false by default, the current value is set to True.

Test results

Now the default value is False.
Screenshot 2024-03-20 at 7 31 42 a m

Documentation

No docs provided

Copy link

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security Status Findings
Sensitive Functions Analyzer 0 findings
Configured Sensitive Files Analyzer 0 findings
Sensitive Files Analyzer 0 findings

Note

🟢 Risk threshold not exceeded.

Tip

Get answers to your security questions. Add a comment in this PR starting with @DryRunSecurity. For example...

@dryrunsecurity What are common security issues with web application cookies?

Powered by DryRun Security

Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@mtesauro mtesauro merged commit 566fa16 into DefectDojo:bugfix Mar 25, 2024
120 checks passed
manuel-sommer pushed a commit to manuel-sommer/django-DefectDojo that referenced this pull request Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants