Forum Discussion
Introducing Enhancements to VPR in Tenable Vulnerability Management!
Today, we launched enhancements to Vulnerability Priority Rating (VPR) in Tenable Vulnerability Management. These updates provide unmatched precision, AI-driven insights, and contextual understanding to help your security teams prioritize and remediate vulnerabilities more efficiently.
How this benefits you:
- Sharpen precision to focus on what matters most: While traditional CVSS scores classify 60% of CVEs as High or Critical, our original VPR reduced this to 3%. The enhanced VPR further refines this, helping your teams focus on just 1.6% of vulnerabilities that represent actual risk to your business. This is achieved by leveraging an even broader spectrum of threat intelligence and real-time data input used to predict near-term exploitation in the wild.
- Unlock AI-driven insights and explainability: Our new LLM-powered insights deliver instant clarity, helping you quickly understand why an exposure matters, how it has been weaponized by threat actors, and providing clear, actionable guidance for mitigation and risk reduction.
- Prioritize with industry and regional context: New metadata provides crucial context, helping you understand if a vulnerability is being targeted in your specific industry or geographic region.
- Leverage advanced querying & filtering: The enhanced VPR model is easily accessible for filtering and querying in the new Explore views, which display Assets and Findings data, enabling faster investigations and response workflows.
Both the original VPR and the enhanced VPR (referred to in-product as 'VPR (Beta)') will coexist for a period of time in Tenable Vulnerability Management, ensuring you can make a smooth transition. Future deprecation of the original VPR will be communicated in advance.
To learn more about the enhancements to VPR, see the solution overview and click-through demo.
For additional information, see our FAQ, release notes, and Scoring Explained help documentation.
3 Replies
- tsitcawichProduct Team
Thank you so much for flagging this. The Tenable team investigated, and this mapping issue has now been resolved.
- TM_SSJ4Connect Contributor III
It appears that some of the VPR (Beta) Key Driver CVE ID is not matching the vulnerability referenced for the plugin itself. I've found multiple but below is a Google Chrome Vulnerability (CVE-2024-5160) that has a Linux Kernel vulnerability (CVE-2019-13272) as the key driver.
- paul_jacobyConnect Contributor IV
Will this enhancement be added to Tenable.SC?