Skip to main content
Exploit Maturity
Updated over a week ago

About

The Exploit Maturity indicator enhances the existing exploitable tag by providing a detailed analysis of the industry’s confidence level regarding known exploits. This addition allows you to make better-informed decisions based on the maturity level of the exploit.

Highlights:

  • A detailed breakdown of the confidence level in existing exploits based on CVEs and internal Threat Intelligence (TI), introducing various maturity levels, such as mature and unproven.

  • Access and search within our Analytics platform, vulnerability details card, and filter vulnerabilities across pages based on exploit maturity levels using the Magic Search filter.

  • Get a temporal and adjusted scoring reflecting real-time threat intelligence.

Exploit Maturity Confidence Levels

  • Mature: An exploit that has been extensively tested and proven to reliably exploit a vulnerability across various environments and conditions.

  • POC: An exploit that has been demonstrated to exploit a vulnerability in a controlled environment but may not yet be fully reliable or stable.

  • Unproven: An exploit that is theoretical or has been proposed but has not been demonstrated or tested in any meaningful way.

  • None: Indicates that no known exploit exists for the vulnerability at the current time.

Where in the UI?

Exploit Maturity levels are reflected in the following:

Hover over the maturity level presented in the vulnerability card to understand the meaning of each level better.

Click on the Threat Intelligence tab > Vulcan Threats Sources to learn about the CVE sources the Vulcan Platform ingested the exploit maturity level from.

Magic Search filters across the Vulnerabilities and Assets pages

The filter condition is: Vulnerability > Maturity Rank > is / is not / is empty > continue selection from the available drop-down menu.

The filter condition is: Vulnerability > Maturity Rank > is / is not / is empty > continue selection from the available drop-down menu.

For example, you can utilize the availability of this filter in playbooks to prioritize and run remediation campaigns/playbooks on Mature exploitable vulnerabilities.

FAQs

If, for example, a CVE is labeled as "POC" in some sources and "Mature" in others, which maturity level tag does Vulcan use?

Vulcan uses the highest maturity level available from the sources and applies it as the Exploit Maturity level for that vulnerability. In this case, it would be "Mature".

Did this answer your question?