Administrator
|
Want to send it to the community yourself? The list is CWE Research Discussion [hidden email] and just make sure to cc [hidden email] -- Alec J. Summers Cyber Solutions Innovation Center Group Leader, Software Assurance Research & Practice Cyber Security Engineer, Lead O: (781) 271-6970 C: (781) 496-8426 –––––––––––––––––––––––––––––––––––– MITRE - Solving Problems for a Safer World From: Rushi B Purohit <[hidden email]> Hi Alec, I just realized that we never actually sent an e-mail via the research list. Here is what I think will be sufficient to share today: The CWE team heard from the community about difficulty in navigating the CWE corpus to identify specific, desired information. As part of a longer effort, the CWE team has produced an initial guidance materials which will help the community identify the root cause CWE entry for the respective CVE records. Guidance for mapping vulnerabilities to weaknesses is now available on the “CVE → CWE Mapping Guidance” page on the CWE website. Vendors and researchers can use this guidance to better align vulnerabilities (CVE Records) to their respective, underlying weaknesses (CWE entries). This guidance is informed by two years of experience in analyzing and mapping thousands of CVE Records in the NIST’s National Vulnerability Database (NVD) to CWEs for calculating the annual CWE Top 25 list. By aligning CVE Records to the most applicable CWE Entries, the community will be in a better position to mitigate or eliminate their associated operational risk most effectively. The new guidance provides an overview of CWE, a section of helpful resources with a refresher on CWE Entry structure, and offers five different mapping methodologies that can be used on the CWE website to help identify appropriate weakness mappings for CVE Records:
A mapping quick-tips, mapping cheat sheet, and mapping examples are also included. Please [hidden email] with any comments or concerns about this guidance. We look forward to hearing from you! Thank you, Rushi Purohit |
Free forum by Nabble | Edit this page |