The Security Industry Depends on NVD

The Security Industry Depends on NVD

The National Vulnerability Database (NVD) is utilized in some capacity by nearly every security product and program worldwide. However, in recent weeks, it has halted the publication of new information crucial for these organizations to protect themselves against emerging threats.

Over the past month, the security industry has experienced the impact on this critical resource, specifically the sharp reduction in CVE publication and enrichment, e.g., missing common platform enumerations (CPEs) which inform the public of which products and versions are affected by the Common Vulnerability Enumeration (CVE).

The origins of the NIST’s NVD trace back to 1999 as a reliable source of critical information on software vulnerabilities.. The NVD enriches vulnerability information provided by Mitre’s CVE Program, which identifies, defines, and catalogs publicly disclosed cybersecurity vulnerabilities. The information enhanced by NIST includes critical details such as vulnerability severity (CVSS Metrics), associated products (CPEs), and Common Software Weaknesses (CWEs) that aid  security practitioners and developers and serves as an audit function for Vulnerability Management programs. 

Recently, the NVD paused analyzing and enriching vulnerability information from Mitre, causing a ripple effect in the security industry and organizations worldwide. The halt has also limited visibility into vulnerability severity, which is broadly used to prioritize vulnerabilities using tools such as FIRST’s Exploit Prediction Scoring System (EPSS) and many other proprietary Risk Scoring systems. The world relies on NIST's NVD enrichment to identify vulnerable products within their environment, to measure severity, criticality, risk and impacts on their IT infrastructure, software and business-critical applications.

Credit: xkcd.com for template

Headwinds Facing the NVD

Exponential Rise in New Vulnerabilities:

The NVD has processed and analyzed hundreds of thousands of CVEs, with the volume continuing to rise steadily each year. Human analysis is integral to processing CVEs, and the pause is likely due to limited resources to handle the exponential growth in CVE issuance.

NVD Resource Allocation:

With multiple projects and limited resources, tough decisions on prioritization are inevitable. While it's not apparent to the public why CVE enrichment has paused, it's evident that those at NIST are facing difficult decisions to ensure the program's sustainability.

NIST Budget Cuts:

Experiencing its first budget cut in over a decade. The NVD program might have faced resource cuts amid broader budgetary constraints. Reference: https://ww2.aip.org/fyi/budget-tracker

Supporting NIST NVD: How You Can Help?

Despite the silence surrounding NIST NVD, there's likely a significant reason behind this. As a scientific organization, NIST tends to remain focused on its mission. Therefore, it's essential for the community to advocate for the critical importance of NVD and ensure its adequate resourcing.

Encouraging the security community to show support for NIST NVD and its pivotal role in the cybersecurity ecosystem is crucial. Individuals can take action by reaching out to their senators and emphasizing the significance of NIST NVD.

Help Contribute to a letter to congress being drafted by Dan Lorenc: https://docs.google.com/document/d/1y6JXhh52b1OMxLMQyl_WH0R2-85iYEBzjSm_fhv8-GY/edit?usp=sharing

Call Your Senator:

https://www.senate.gov/senators/senators-contact.htm

Alex Armasu

Founder & CEO, Group 8 Security Solutions Inc. DBA Machine Learning Intelligence

6mo

Thanks for putting this up!

Olivier Debré

Consultant en sécurité de l'information (« cybersécurité ») chez Excube

7mo

I listened yesterday to the excellent podcast by Kurt Seifried and Josh Bressers. #NVD mentionned in several #NIST SP 800 series document. Hence, problem without NVD. Answer: at least 12 of them. 1. SP 800-30 Rev. 1: Guide for Conducting Risk Assessments 2. SP 800-40 Rev. 3: Guide to Enterprise Patch Management Technologies 3. SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations 4. SP 800-137: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations 5. SP 800-150: Guide to Cybersecurity Incident Handling 6. SP 800-160 Volume 1: Systems Security Engineering: Fundamentals of Systems Security Engineering 7. SP 800-171 Rev. 2: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations 8. SP 800-190: Application Container Security Guide 9. SP 800-198: Guide to the Application of System Security Engineering 10. SP 800-204A: Building Secure Microservices-based Applications Using Service-Mesh Architecture 11. SP 800-211: Security Policy for Container Images 12. SP 800-228: Guide for Cybersecurity Event Recovery https://opensourcesecurity.io/2024/03/17/episode-420-whats-going-on-at-nvd/

Olivier Debré

Consultant en sécurité de l'information (« cybersécurité ») chez Excube

7mo

I guess there's another probable consequence to be concerned about: the Known Exploited Vulnerabilities #KEV catalogue by the Cybersecurity and Infrastructure Security Agency #CISA hasn't been updated since March 7, namely 13 days, which is seldom. More than 10 days between two successive #CVE additions to the #KEV has been encountered only 15 times, on a total of 1088 CVEs (among which 288 were published on day one, November 3, 2021.

  • No alternative text description for this image
Jean-Baptiste Maillet

Embedded OSS cybersecurity

7mo

Am I the only one contemplating the idea of making myself a t-shirt with this tweaked XKCD meme? 🤔 That could even be a (very) small, (very) short term alternative business plan for some NVD users.

To view or add a comment, sign in

Explore topics