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

ZAP Scan deduplication is not working #10252

Closed
1 of 3 tasks
zakrush opened this issue May 22, 2024 · 1 comment
Closed
1 of 3 tasks

ZAP Scan deduplication is not working #10252

zakrush opened this issue May 22, 2024 · 1 comment
Labels

Comments

@zakrush
Copy link
Contributor

zakrush commented May 22, 2024

Be informative
ZAP Scan reports is not deduplicated in new engagement of same product,

Bug description
A clear and concise description of what the bug is. For errors include at least the exact error message you are seeing (including traceback).

Steps to reproduce
Steps to reproduce the behavior:

  1. Create Engagment. Dedup on Engagment is disable.
  2. Import ZAP_Scan report.(attached)
  3. Create Second engagment. Dedup on Engagment is disable.
  4. Import the same ZAP_scan report
    some_report.txt

Expected behavior
After importing ZAP report to new engagement all findings have been deduplicated

Deployment method (select with an X)

  • Docker Compose
  • Kubernetes
  • GoDojo

Environment information

  • DefectDojo version v. 2.34.4

Logs
Use docker-compose logs (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).

Sample scan files
If applicable, add sample scan files to help reproduce your problem.

Screenshots
First import

image

second import
image

@zakrush zakrush added the bug label May 22, 2024
@mtesauro
Copy link
Contributor

Do you have dedupication turned on globally in System Settings?

image

@zakrush zakrush closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants