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

CVE way forward and purpose related questions #2

Open
sei-vsarvepalli opened this issue Aug 24, 2023 · 1 comment
Open

CVE way forward and purpose related questions #2

sei-vsarvepalli opened this issue Aug 24, 2023 · 1 comment

Comments

@sei-vsarvepalli
Copy link

I am writing this to capture what came up from a CVE QWG discussion on Best Practices for CVE . @andrewpollock has raised some questions I think falls in the SPWG lane. Quoting Andrew's concerns - here.

These may already be discussed/addressed in SPWG and expected to be part of the newer documentation. But I want to make sure it is documented here and SPWG is aware of these concerns. I am happy to facilitate this discussion as time and resources permit.

What is the intention of a CVE record?
What is the utility of a CVE record that conveys a defaultStatus of
"unknown"?
Who is a CVE record for?
Basically, I'm asking about how fitness for purpose is determined.
More broadly, what is the purpose of the CVE Program (given it's ultimately
a collection of CVE records)
Who are its customers?
What are their needs?
How is the CVE Program's success at meeting their needs being evaluated?
I can refer myself to the CVE Program's mission statement: "Identify,
define, and catalog publicly disclosed cybersecurity vulnerabilities."
This statement doesn't seem to be touching on the "for who?" or "and then
what?" or really, the "why?"

@zmanion
Copy link
Collaborator

zmanion commented Oct 1, 2023

Keeping my response/current opinion handy CVEProject/cve-schema#241 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants