-
Notifications
You must be signed in to change notification settings - Fork 0
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
glvd: implement minimum viable triage feature #127
Comments
changes the view sourcepackagecve so that it always returns the full list of cves so the client can filter for resolved. This is maybe not great from a performance point of view, and it can be optimized later, but currently this seems to be what we need for the UI. Part of gardenlinux/glvd#127
Implements the following features: - Allow viewing both resolved and unresolved issues in cve by distribution list - Display of cve context in cve details Part of gardenlinux/glvd#127
related: gardenlinux/glvd-contrib@d815419 |
Related work: Add a wrapper script to run the triage more easily: |
Local test setup |
API to query cve details with context (triage information): gardenlinux/glvd-api#68 |
Setup minimal test data gardenlinux/glvd-api#69 |
Show triage info in a table, view more information like the distribution id gardenlinux/glvd-api#70 |
Better test setup for triage process gardenlinux/glvd-triage-cli#1 |
Show last modified and ingested date |
Closing as completed. We have a minimum triage feature, further development will be reflected in separate issues. |
for glvd, we need a way to set a state for cves that hides them from the default view
there are many old cves that are technically vulnerable, but in practice they are either fixed or not considered as an actual vulnerability.
we need some sort of triage feature. this requires changes to the database, and it requires some sort of writable api (so far our api is read-only on purpose to avoid having to deal with authn/authz)
The text was updated successfully, but these errors were encountered: