Skip to content

Commit 83267a9

Browse files
Merge pull request #3069 from emote-tracking branch 'origin/content-rjr-3067' into test
2 parents 366d817 + ba6cddf commit 83267a9

2 files changed

Lines changed: 53 additions & 3 deletions

File tree

src/assets/data/news.json

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,55 @@
11
{
22
"currentNews": [
3+
{
4+
"id": 405,
5+
"newsType": "blog",
6+
"title": "Recognition for CNAs Actively Providing Vulnerability Data Enrichment for CVE Records",
7+
"urlKeywords": "CNA Enrichment Recognition List",
8+
"date": "2024-09-10",
9+
"author": {
10+
"name": "CVE Program",
11+
"organization": {
12+
"name": "CVE Program",
13+
"url": ""
14+
},
15+
"title": "",
16+
"bio": ""
17+
},
18+
"description": [
19+
{
20+
"contentnewsType": "paragraph",
21+
"content": "The CVE Program now publishes a “<a href='/About/Metrics#CNAEnrichmentRecognition'>CNA Enrichment Recognition List</a>” every two weeks on the <a href='/About/Metrics'>Metrics</a> page on the CVE website to recognize <a href='/ProgramOrganization/CNAs'>CVE Numbering Authorities (CNAs)</a> that are actively enriching their <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a> by adding <a href='https://www.first.org/cvss/' target='_blank'>Common Vulnerability Scoring System (CVSS)</a> and <a href='https://cwe.mitre.org/' target='_blank'>Common Weakness Enumeration (CWE&trade;) </a> information."
22+
},
23+
{
24+
"contentnewsType": "paragraph",
25+
"content": "<h3>Background</h3>"
26+
},
27+
{
28+
"contentnewsType": "paragraph",
29+
"content": "Getting more precise and quality vulnerability information in the hands of defenders and downstream customers on a timelier basis helps the cybersecurity community better address risks. Additional vulnerability-related information provides increased transparency, enables vulnerability root cause understanding, and helps prioritize vulnerability and incident response. Information standards and knowledge repositories like <a href='https://www.first.org/cvss/' target='_blank'>CVSS</a> and <a href='https://cwe.mitre.org/' target='_blank'>CWE</a>, among others, help provide a common language for this additional information."
30+
},
31+
{
32+
"contentnewsType": "paragraph",
33+
"content": "In April 2024, the CVE Program <a href='/Media/News/item/blog/2024/04/30/New-CVE-Record-Format-Enables-Additional-Data'>highlighted how its data format evolved</a> to better facilitate automation and data enrichment. This means that <a href='/ProgramOrganization/CNAs'>CNAs</a>, as the authoritative source of vulnerability information within their scopes, and those with access to the most reliable source for accurate determinations, can easily provide data enrichment directly to a CVE Record, as opposed to waiting for a third-party to do so in a less timely and potentially less accurate manner. As such, the CVE Program called on all CNAs to provide this enrichment to their CVE Records directly, and, in so doing, contribute more substantially to the vulnerability management process. Many CNAs answered that call."
34+
},
35+
{
36+
"contentnewsType": "paragraph",
37+
"content": "<h3>CNA Enrichment Recognition List</h3>"
38+
},
39+
{
40+
"contentnewsType": "paragraph",
41+
"content": "In recognition of CNAs providing enhanced vulnerability data in their CVE Records, the CVE Program will now publish a “<a href='/About/Metrics#CNAEnrichmentRecognition'>CNA Enrichment Recognition List</a>” every two weeks."
42+
},
43+
{
44+
"contentnewsType": "paragraph",
45+
"content": "CNAs will be added to the list if they provide <a href='https://www.first.org/cvss/' target='_blank'>CVSS</a> and <a href='https://cwe.mitre.org/' target='_blank'>CWE</a> information 98% of the time or more within the two-week period of their last published CVE Record. This being the first iteration of such a list, the criteria may be adjusted in the future. For more information about vulnerability information types like CVSS and CWE, see the <a href='/CVERecord/UserGuide'>CVE Record User Guide</a>."
46+
},
47+
{
48+
"contentnewsType": "paragraph",
49+
"content": "View the current CNA Enrichment Recognition List <a href='/About/Metrics#CNAEnrichmentRecognition'>here</a>."
50+
}
51+
]
52+
},
353
{
454
"id": 404,
555
"newsType": "news",

src/views/About/Metrics.vue

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -280,10 +280,10 @@
280280
This means that
281281
<router-link to="/ProgramOrganization/CNAs">CNAs</router-link>,
282282
as the authoritative source of vulnerability information within their scope, and those with access to the most reliable
283-
source for accurate determinations, can easily provide data enrichment directly to CVE as opposed to waiting
283+
source for accurate determinations, can easily provide data enrichment directly to a CVE Record, as opposed to waiting
284284
for a third-party to do so in a less timely and potentially less accurate manner. As such, the CVE Program called on all
285-
CNAs to provide this enrichment to CVE directly, and in so doing, contribute more substantially to the vulnerability
286-
management process. Many have answered that call.
285+
CNAs to provide this enrichment to their CVE Records directly, and, in so doing, contribute more substantially to the
286+
vulnerability management process. Many have answered that call.
287287
</p>
288288
<p>
289289
In recognition of these CNAs, the CVE Program publishes this “CNA Enrichment Recognition List” every two weeks. Currently,

0 commit comments

Comments
 (0)