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

Show epss fields as columns in Vulnerability Audit view #1126

Open
2 tasks done
valentijnscholten opened this issue Jan 2, 2025 · 1 comment
Open
2 tasks done

Show epss fields as columns in Vulnerability Audit view #1126

valentijnscholten opened this issue Jan 2, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@valentijnscholten
Copy link
Contributor

valentijnscholten commented Jan 2, 2025

Current Behavior

The Vulnerability Audit view shows all vulnerabilities, but there is no EPSS columns.

Proposed Behavior

Add an (optional?) column to display the EPSS values of a vulnerability. This will help when triaging / deduplication of vulnerablities.

I noticed the EPSS values are not yet present in the API response.

@rbt-mm Do you think this is feasible? It's been a while since I looked at the datamodel, so I am not sure. I am actually impressed that we can now finally sort on affectedProjects for vulnerabilities :-)

Checklist

@valentijnscholten valentijnscholten added the enhancement New feature or request label Jan 2, 2025
@rbt-mm
Copy link
Contributor

rbt-mm commented Jan 7, 2025

As far as I remember, the EPSS values are already contained in the data of the vulnerabilities that the backend is sending to the Vulnerability Audit View. Atleast for the Vulnerabilities By Occurrence tab. So this column should be relatively easy to add in the frontend (adding sorting and filtering via EPSS may take some more time).

For the other tab, the Grouped Vulnerabilities, the EPSS values are currently not included in the data model, but this is something which should be possible to add by just copying and slightly adjusting the logic from the data model used for the other tab. Afterwards the values would just need to be added to the frontend as well.

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
Development

No branches or pull requests

2 participants