Skip to content

Option to trigger notifications based on severity of the CVE #3767

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

Open
2 tasks done
tapmch opened this issue May 28, 2024 · 3 comments · May be fixed by #4879 or DependencyTrack/frontend#1235
Open
2 tasks done

Option to trigger notifications based on severity of the CVE #3767

tapmch opened this issue May 28, 2024 · 3 comments · May be fixed by #4879 or DependencyTrack/frontend#1235
Labels
enhancement New feature or request

Comments

@tapmch
Copy link

tapmch commented May 28, 2024

Current Behavior

I can configure an alert notification for newly detected vulnerabilities.

Proposed Behavior

Currently, it is possible to configure a notification when a new vulnerability is detected. I would like to be able to trigger an alert notification only when the severity level is critical or high.

Checklist

@tapmch tapmch added the enhancement New feature or request label May 28, 2024
@farsheedify
Copy link

This feature would be incredibly helpful in reducing the number of notifications sent to our security champions. Currently, some teams in our organization manage numerous microservices, and they receive notifications about new vulnerabilities for every severity level. This results in a flood of emails, which can lead to important messages being ignored due to the sheer volume.

By filtering notifications based on severity, we could limit the emails to only high and critical vulnerabilities. This would significantly reduce the number of emails, ensuring that only the most important notifications are sent, making it easier for our security champions to stay focused on critical issues.

@Hunroll
Copy link
Contributor

Hunroll commented Mar 28, 2025

We also need this feature.
Actually our usecase would be to separate only Critical vulnerabilities and give them e.g. Warning level.

If you have a vision, how it should be configured - I could take this task.

Right now I see it as new setup page (Notifications -> Severity Mapping) which will have such a grid:

Severity Notification level
Critical ERROR
High WARNING
Medium INFORMATIONAL
Low INFORMATIONAL
Unassigned INFORMATIONAL

I'm not sure if it's OK to tag @nscuro , sorry if it's not. But I'm ready to help with this one.

Thanks!

@emyhrberg
Copy link

PR's posted @nscuro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
4 participants