|
23 | 23 | professionals use CVE Records to ensure they are discussing the same issue, and to coordinate their efforts to prioritize |
24 | 24 | and address the vulnerabilities. |
25 | 25 | </p> |
| 26 | + <div class="cve-white-bg-gray-border-container"> |
| 27 | + <h3 class="title mt-4">CVE Lightning Talk</h3> |
| 28 | + <figure class ="image is-16by9"> <!-- video --> |
| 29 | + <iframe class="has-ratio" width="560" height="315" src="https://www.youtube.com/embed/W4T2n_2m7WA?si=sOjmg4IfeHeBEgVp" frameborder="0" allowfullscreen> |
| 30 | + </iframe> |
| 31 | + </figure> |
| 32 | + <p> |
| 33 | + Provides a high-level overview of the CVE Program, what a CVE Record is and how |
| 34 | + it enables two or more people or tools to refer to a vulnerability and know they are talking about the |
| 35 | + same thing, and an introduction to how and why to become a CVE Numbering Authority (CNA) partner. |
| 36 | + </p> |
| 37 | + </div> |
26 | 38 | <div class="cve-white-bg-gray-border-container"> |
27 | 39 | <h3 class="title mt-4">Podcast - The Value of Assigning CVEs</h3> |
28 | 40 | <figure class ="image is-16by9"> <!-- podcast --> |
29 | 41 | <iframe class="has-ratio" width="560" height="315" src="https://www.youtube.com/embed/aT6BjbZS22w" frameborder="0" allowfullscreen> |
30 | 42 | </iframe> |
31 | 43 | </figure> |
32 | 44 | <p> |
33 | | - Shannon Sabens of <a href='https://www.crowdstrike.com/' target='_blank'>CrowdStrike</a> chats with Madison Oliver of |
34 | | - <a href='https://securitylab.github.com/' target='_blank'>GitHub Security Lab</a> about how and why CVEs are assigned, the value |
35 | | - of CVEs in vulnerability management, responsible coordination of vulnerability disclosures, the importance of comprehensiveness |
36 | | - in security advisories, and why there is no stigma in a CVE. In addition, <a href='/ProgramOrganization/CNAs'>CVE Numbering |
37 | | - Authority (CNA)</a> scopes, disclosure policies, turnaround times, and more are discussed in general, as are GitHub’s specific |
38 | | - CNA processes and how it helps open source projects hosted on GitHub with their CVEs and advisories. |
| 45 | + Learn how and why CVEs are assigned, the value of CVEs in vulnerability management, responsible coordination of |
| 46 | + vulnerability disclosures, the importance of comprehensiveness in security advisories, and why there is no stigma |
| 47 | + in a CVE. In addition, CVE Numbering Authority (CNA) scopes, disclosure policies, turnaround times, and more |
| 48 | + are discussed in general, as are GitHub’s specific CNA processes and how it helps open source projects hosted |
| 49 | + on GitHub with their CVEs and advisories. |
39 | 50 | </p> |
40 | 51 | </div> |
41 | 52 | <div class="cve-white-bg-gray-border-container"> |
|
44 | 55 | <iframe class="has-ratio" width="560" height="315" src="https://www.youtube.com/embed/OQB2w71JmLE" frameborder="0" allowfullscreen> |
45 | 56 | </iframe> |
46 | 57 | </figure> |
47 | | - <a href='/ProgramOrganization/Board'>CVE Board</a> members Tod Beardsley, Shannon Sabens, and Kent Landfield provide |
48 | | - the truth and facts about the following myths about the CVE Program: |
| 58 | + Learn the truth and facts about the following myths about the CVE Program: |
49 | 59 | <ul> |
50 | 60 | <li class="cve-list-no-bullet">Myth #1: The CVE Program is run entirely by the MITRE Corporation.</li> |
51 | 61 | <li class="cve-list-no-bullet"> Myth #2: The CVE Program is controlled by software vendors.</li> |
|
60 | 70 | </iframe> |
61 | 71 | </figure> |
62 | 72 | <p> |
63 | | - Shannon Sabens of |
64 | | - <a href='https://www.crowdstrike.com/' target='_blank'>CrowdStrike</a> |
65 | | - chats with Julia Turkevich of the |
66 | | - <a href='https://www.cisa.gov/about/divisions-offices/cybersecurity-division' target='_blank'> |
67 | | - U.S. Cybersecurity and Infrastructure Security Agency (CISA)</a> |
68 | | - about the myths and facts of partnering with the CVE Program as a |
69 | | - <router-link to="/ProgramOrganization/CNAs">CVE Numbering Authority</router-link> (CNA): |
| 73 | + Learn the myths and facts of partnering with the CVE Program as a CVE Numbering Authority (CNA): |
70 | 74 | </p> |
71 | 75 | <ul> |
72 | 76 | <li class="cve-list-no-bullet">Myth #1: Only a specific category of software vendors can become CNAs.</li> |
|
86 | 90 | </iframe> |
87 | 91 | </figure> |
88 | 92 | <p> |
89 | | - The following truths and facts about the <a href='/ProgramOrganization/CNAs'>CVE Numbering Authority (CNA)</a> partner onboarding |
| 93 | + The following truths and facts about the CVE Numbering Authority (CNA) partner onboarding |
90 | 94 | process are discussed: duration and complexity of the onboarding process; the fact that there is no fee to |
91 | | - participate; ease of incorporating assigning |
92 | | - <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE Identifiers (CVE IDs)</a> |
93 | | - and publishing <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a> |
| 95 | + participate; ease of incorporating assigning CVE Identifiers (CVE IDs) and publishing CVE Records |
94 | 96 | into an organization’s existing coordinated vulnerability disclosure (CVD) processes; availability of automated |
95 | | - tools for CNAs; the <a href='/AllResources/CveServices#CveRecordFormat'>CVE JSON Record format</a> and available |
96 | | - guidance; role of <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRoot'>Roots</a> and |
97 | | - <a href='/ResourcesSupport/Glossary?activeTerm=glossaryTLRoot'>Top-Level Roots</a> and how they help CNAs; importance of |
98 | | - CNAs determining their own <a href='/ResourcesSupport/Glossary?activeTerm=glossaryScope'>scopes</a>; disclosure policies; |
99 | | - the community aspect of being a CNA and the availability of peer support; the value of CNAs participating in one or more |
100 | | - <a href='/ProgramOrganization/WorkingGroups'>CVE Working Groups</a>, especially the |
101 | | - <a href='/ProgramOrganization/WorkingGroups#CNAOrganizationOfPeersCOOP'>CNA Organization of Peers (COOP)</a>; and more. |
| 97 | + tools for CNAs; the CVE JSON Record formatand available guidance; role of Roots and Top-Level Roots and how they help CNAs; |
| 98 | + importance of CNAs determining their own scopes; disclosure policies; the community aspect of being a CNA and the |
| 99 | + availability of peer support; the value of CNAs participating in one or more CVE Working Groups, especially the |
| 100 | + CNA Organization of Peers (COOP); and more. |
102 | 101 | </p> |
103 | 102 | </div> |
104 | 103 | <div class="cve-white-bg-gray-border-container"> |
|
109 | 108 | </figure> |
110 | 109 | <p> |
111 | 110 | Learn how |
112 | | - <a href='/ProgramOrganization/CNAs'>CVE Numbering Authority (CNA)</a> |
| 111 | + CVE Numbering Authority (CNA) |
113 | 112 | partners — ranging from large to small organizations, proprietary and open source products or projects, disparate business |
114 | | - sectors, and different geographic locations — are overseen and supported within the |
115 | | - <a href='/'>CVE Program</a> |
116 | | - by “<a href='/ResourcesSupport/Glossary?activeTerm=glossaryTLRoot'>Top-Level Roots</a>” |
117 | | - and “<a href='/ResourcesSupport/Glossary?activeTerm=glossaryRoot'>Roots</a>.” |
118 | | - Topics include the roles and responsibilities of the two different types of Roots; how their work benefits the CNAs |
| 113 | + sectors, and different geographic locations — are overseen and supported within the CVE Program by “Top-Level Roots” |
| 114 | + and “Roots.” Topics include the roles and responsibilities of the two different types of Roots; how their work benefits the CNAs |
119 | 115 | under their care; how they recruit new CNA partners, including suggestions for addressing upper management concerns if a CNA |
120 | 116 | prospect organization is hesitant to partner as a CNA; how they work with and support their CNAs over time; how the |
121 | 117 | “Council of Roots” works together to enhance and help improve the program overall; and much more. All current CVE Program |
|
0 commit comments