-
Notifications
You must be signed in to change notification settings - Fork 8
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
CRAVEX: Alerting/notification #106
Comments
Refer to issue #94 for discussion of the vulnerability lookup process. |
We can make use of the existing DejaCode Notifications feature to support this one. Additionally (or alternatively) we could consider providing an ability to create a workflow request automatically to alert the appropriate users and to track the progress of the analysis and resolution. |
@DennisClark let's start with this for now
|
@tdruez We can possibly consider triggering a notification based on an update (change) to the Vulnerability Risk field. |
I think the new notification should be based on the Package for security reasons, although the message could say something like there is a vulnerability risk change in a package used by one or more of your products. |
Create a system to provide a alert/notification when new, not-yet-processed vulnerabilities are uncovered
The text was updated successfully, but these errors were encountered: