You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugfix: reimport: close_old_findings must respect service field (#12782)
* reimport: close_old_findings must respect service field
* reimport: close_old_findings must respect service field
* close_old_findings: update docs and help texts
* typo
* reimport docs tweak
* reimport: assert that reopen respect service field
Copy file name to clipboardExpand all lines: docs/content/en/about_defectdojo/faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ There are two different methods to import a report from a security tool into Def
48
48
-**Import** handles the report as a single point-in-time record. Importing a report creates a Test within DefectDojo that holds the Findings rendered from that report.
49
49
-**Reimport** is used to extend an existing Test. If you have a more open-ended approach to your testing process, you continuously Reimport the latest version of your report to an existing Test. DefectDojo will compare the results of the incoming report to your existing data, record any changes, and then adjust the Findings in the Test so that they match the latest report.
50
50
51
-
Both methods also use **Deduplication** differently: while two discrete Imported Tests in the same Product will identify and label duplicate Findings, Reimport will discard duplicate Findings altogether.
51
+
Both methods also use **Deduplication** differently: while two discrete Imported Tests in the same Product will identify and label duplicate Findings, Reimport will skip duplicates in uploaded reports as theses Findings already exist in Defect Dojo.
52
52
53
53
Generally speaking - if a point-in-time report is what you need, Import is the best method to use. If you are continuously running and ingesting reports from a tool, Reimport is the better method for keeping things organized.
|`close_old_findings`| if `true`, findings that are not duplicates and that were in the previous scan of the same type (example ZAP) for the same **engagement** (or product in case of `close_old_findings_product_scope`) and that are not present in the new scan are closed (`Inactive`, `Verified`, `Mitigated`). | if `true`, findings that that are in the same **test** and that are not present in the new scan are closed (`Inactive`, `Verified`, `Mitigated`) |
392
+
|`close_old_findings_product_scope`| if true, `close_old_findings` applies to all findings of the same type in the whole **product**. Note that "Deduplication on engagement" is no longer used to determine the scope of `close_old_findings`| has no effect |
393
+
394
+
The `close_old_findings` feature will respect the value of the `service` field to only close findings with an identical `service` value.
Copy file name to clipboardExpand all lines: dojo/forms.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -651,7 +651,7 @@ class ReImportScanForm(forms.Form):
651
651
label="Choose report file",
652
652
allow_empty_file=True,
653
653
required=False)
654
-
close_old_findings=forms.BooleanField(help_text="Select if old findings no longer present in the report get closed as mitigated when importing.",
654
+
close_old_findings=forms.BooleanField(help_text="Select if old findings in the same test that are no longer present in the report get closed as mitigated when importing.",
655
655
required=False, initial=True)
656
656
version=forms.CharField(max_length=100, required=False, help_text="Version that will be set on existing Test object. Leave empty to leave existing value in place.")
657
657
branch_tag=forms.CharField(max_length=100, required=False, help_text="Branch or Tag that was scanned.")
0 commit comments