CNA Rules Revision Phase 2 - Week 8

["Adinolfi, Daniel R" <dadinolfi@mitre.org>]

Greetings,

 

We are continuing the second phase of the 2017 CNA Rules Revision process.

 

You can see the schedule of what issues we will be discussing each week on the Wiki section of our GitHub site:

 

<https://github.com/CVEProject/docs/wiki/CNA-Rules-Revision-Schedule-2017>

 

with the issues listed in the Issue tracker:

 

<https://github.com/CVEProject/docs/issues>.

 

The document from which we are starting all discussion, CNA Rules 1.1, is here:

 

<http://cve.mitre.org/cve/cna/CNA_Rules_v1.1.pdf>

 

The CURRENT NEW DRAFT, including the previous weeks' updates, is here:

 

<https://github.com/CVEProject/docs/blob/cna-documents/cna/CNA%20Rules/CNA%20Rules%20Development/CNA%20Rules%20v2.0week7.docx>

 

The section of the GitHub site where the rules suggestions were originally tracked is here:

 

<https://github.com/CVEProject/docs/tree/cna-documents/cna/CNA%20Rules/CNA%20Rules%20Development>

 

Each week, I will post a reminder to the CNA list of what issues we will be focusing on for that week.

 

Week 8

 

This week we will be discussing:

 

Week #8: September 25-30	Issue Number
Remove requirement to make vulnerabilities public (INC2)	11
Define what year of CVE ID (e.g. CVE-2017) should be used during an assignment.	24
Define how to handle overlapping assignments	47
Clarify that CVE IDs can be assigned to vulnerabilities that are already public	32
Define if and how CNAs assign CVE IDs to bundled third-party products.	30

 

You can add your thoughts or comments to the GitHub issue tracker directly. You can also discuss a particular issue on the cve-cna-list mailing list.

 

By the end of each week, the final language for any changes will be written. For any issues that are not resolved for that week, we will put a hold on those issues and move on to the next week's issues. The goal is to discuss the entire set of issues in the eight-week period of the review cycle. If there are outstanding issues at the end of the cycle, we can decide how to proceed as a group (including dropping the issue or setting a short deadline for resolving the issue after the review cycle).

 

Please let us know if you have any questions, and thank you in advance for your input into this process.

 

Thanks.

 

-Dan

_________________________

Daniel Adinolfi, CISSP

Lead Cybersecurity Engineer, The MITRE Corporation

CVE Communications and CNA Coordinator

Email: <dadinolfi@mitre.org>  Phone: 781-271-5774