You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add the assigning CNA to the required information for an entry submission #12
GOAL: Track who reserved what CVE IDs.
CHANGE: Should the original reservation entity or reservation chain be added to required data?
OUTCOME: Regardless of the assigner, the entire Sub CNA/Root CNA chain of CVE ID reservations will be included in each CVE entry.
changed the title [-]Add the assigning CNA in the required information for a submission[/-][+]Add the assigning CNA to the required information for an entry submission[/+]on Jul 21, 2017
Suggestion: Make [ASSIGNINGCNA] a required field. Add [ASSIGNINGCNA] to Appendix B including this description:
The [ASSIGNING CNA]: field should include the name of the assigning CNA. CNAs should use a consistent name to facilitate searches for CVE IDs that originate from them.
Activity
[-]Add the assigning CNA in the required information for a submission[/-][+]Add the assigning CNA to the required information for an entry submission[/+]kurtseifried commentedon Aug 22, 2017
+1. DWF includes the actual CVE Mentor that assigned it (e.g. an individual like "bobsmith@some.tld" or "security@example.org" where security@example.org is then expected to keep internal records).
dadinolfi commentedon Oct 5, 2017
Suggestion: Make [ASSIGNINGCNA] a required field. Add [ASSIGNINGCNA] to Appendix B including this description:
The [ASSIGNING CNA]: field should include the name of the assigning CNA. CNAs should use a consistent name to facilitate searches for CVE IDs that originate from them.
Update automation-transition.md
Update automation-announcements.md