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

Add "data source" as a column to vulnerabilities view #19907

Open
dherder opened this issue Jun 20, 2024 · 2 comments
Open

Add "data source" as a column to vulnerabilities view #19907

dherder opened this issue Jun 20, 2024 · 2 comments

Comments

@dherder
Copy link
Contributor

dherder commented Jun 20, 2024

Problem

As a vulnerability analyst, it is difficult to determine which data source is linked to vulnerabilities (CVEs) raised in Fleet. This is an important datapoint when determining whether or not a CVE might be a false positive. For example, if I investigate CVE-2332-73839 (fake) I'd first check NVD's linked listing of the CVE. By doing this, I'm still not sure if the CVE source is NVD or vulncheck. I would have to hit the public vulncheck api and correlate that with what I see in NVD.

This is a tedious process and makes it appear that Fleet is not transparent in the data backing the vulnerability detections.

The request is to add a column in the vulnerability views called "data source" that would be populated with either NVD or VulnCheck or any future potential data source, oval, etc.

@dherder dherder added :product Product Design department (shows up on 🦢 Drafting board) customer-denlea ~feature fest Will be reviewed at next Feature Fest labels Jun 20, 2024
@noahtalerman
Copy link
Member

@dherder when you get the chance can you please describe the exact workflow that inspired this feature request. Something about false positives?

It could be bug.

It could also be documented clearly. There's specific rule for each type of software.

@dherder
Copy link
Contributor Author

dherder commented Jun 20, 2024

@noahtalerman I raised #19920 to investigate the actual false positive, but by doing that, further proved that we need to show the data source within the UI and API

@noahtalerman noahtalerman removed the :product Product Design department (shows up on 🦢 Drafting board) label Jun 21, 2024
@noahtalerman noahtalerman removed the ~feature fest Will be reviewed at next Feature Fest label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants