Patrick Emsweller, Cisco Systems, Inc.
Kent Landfield, McAfee
Beverly Alvarez, Lenovo Group Ltd.
Scott Moore, IBM
Lisa Olson, Microsoft
Kathleen Noble, Intel
Takayuki Uchiyama, Panasonic Corporation
David Waltermire, National Institute of Standards and Technology (NIST)
Members of MITRE CVE Team in Attendance
2:15 – 2:30: Working Groups
2:30 – 2:45: Root CNA Update
2:45 – 3:00: Dispute Process – Tod Beardsley
3:00 – 3:10: CVE Global Summit – Beverly Alvarez
3:10 – 3:25: CVE Global Summit Agenda – Tod Beardsley
3:25 – 3:55: Open Discussion
§ CNA Coordination Working Group (CNACWG): Tod Beardsley
§ The group reviewed the draft agenda.
§ Draft dispute process has been prepared by CNACWG, and the Board agreed that we should press ahead with discussing this proposal at the CNA Summit.
§ Tod presented the CVE dispute procedure process for the Board’s feedback. Tod explained at the last CNA Summit, the current dispute process was not transparent; CNAs expressed that the dispute process should documented and is an official process that CNAs can reference as needed.
Tod will follow up with Yves Younan & Madison Oliver about the dispute process proposal so they can include an introduction explaining the purpose
of the proposal, why is was developed, and the problem it is trying to solve.
a. Outreach OCWG for most of this section (noted otherwise).
i. Localization – should start in the QWG for guidance, then to the AWG for implementation.
ii. Upstream producers –
1. CNA Recruitment
iii. Downstream users –
iv. Related Projects
1. Vulnerability Description
3. Product identification and management
b. Metrics – CVE Board
i. Community metrics (Public metrics)
ii. CNA specific metrics
iii. Program performance (Report card)
c. Knowledge capture/transfer - CVE Board
i. Record Working Group meetings
1. Where to store the recordings?
ii. Issue tracking
iii. Storage of WG materials – SharePoint site (CVE CNA site)
a. Program Structure SPWG
b. Roles, responsibilities, and requirements SPWG
i. Disclosure Policies
1. Non-vendor CNAs
a. Add new non-vendor CNAs is on hold until the Board can come to an agreement on the requirements for this type of CNA
2. Root CNA shopping
3. Assigning CVE IDs to vulnerabilities in a non-CNA vendor’s product
c. Coverage – CVE Board
i. What’s in, What’s out
ii. End of life
iii. Software as a service
v. Open source software
i. Operationalizing Root CNAs - SPWG
ii. For new CNAs - CNACWG
iii. How to supply refreshers CVE Board/CNACWG
i. CNA Process – Front Door or Back Door: How should CNAs communicate with each other, and how would that information be managed?
iii. Scope statement best practices
iv. Rules Violations
i. Prevent duplicates
ii. Information requirements
4. Split problem types in to vuln. type, root cause, or impact
5. Don’t require references
iii. Should the description match the separate metadata fields
4. CVE List - QWG
a. Formats (all different formats) – CVE Board
i. How can the download formats be updated or retired?
b. CVE Tagging
i. Helps filtering
ii. How to identify the categories we need
iii. Should the tagging be attached to the product or the vulnerability?
iv. Could we leverage a product listing the CVE User Registry?
v. Can it be automated?
vi. EOL tagging
CVE_Board_Meeting_ 19 February 2020 FINAL.pdf (564K) Download Attachment
|Free forum by Nabble||Edit this page|