Feature Request: Add Option to Group Findings by Service During Scan Import

[Durgaps]

Problem Statement

Currently, DefectDojo supports grouping imported findings using options such as component, finding title, and other existing grouping mechanisms. However, there is no option to group findings by service.

In environments where scans cover multiple services (for example, Kubernetes workloads, microservices, or cloud resources), grouping by service would significantly improve finding organization and reduce duplicate findings across imports.

Proposed Enhancement

Introduce a new grouping option that allows findings to be grouped based on the associated service.

This could be implemented similarly to the existing grouping strategies, allowing users to select "Service" as one of the available grouping fields during scan import.

Benefits

• Better support for microservice-based architectures.
• Improved deduplication of findings belonging to the same service.
• Easier tracking and management of vulnerabilities on a per-service basis.
• Consistent grouping for scanners that already provide service metadata.

Possible Implementation

• Add service as an available grouping field alongside existing options (component, finding title, etc.).
• Populate the service value from parser output when available.
• Ensure grouping logic considers the service field when this option is enabled.

Additional Context

Several scanners and integrations include service-related metadata in their results. Leveraging this metadata during grouping would provide a more intuitive way to organize findings for service-oriented deployments.

[tejas0077]

Hi, I'm interested in working on this. Could a maintainer confirm whether this enhancement is on the roadmap and provide guidance on the preferred implementation approach before I start coding?