Effects of Unsuppressing a Vulnerability for a Given Project

When you unsuppress a security vulnerability for a specific component version within a project, the effects of the vulnerability’s previous suppression are reversed. That is, once you unsuppress a vulnerability at the project level, it is once again counted on the dashboard for the project and in the Vulnerabilities bar graph for the previously impacted inventory item. Additionally, subsequently generated API responses now reflect the vulnerability.

Likewise, the actual vulnerability is again visible in the list of vulnerabilities on the Security Vulnerabilities window (which is opened when you click the Vulnerabilities bar graph for the previously impacted inventory item).

The following describes the additional impact that unsuppressing a security vulnerability for a specific component version at the project level has on other features of Code Insight:

•

Advanced Search on the Analysis Workbench, Project Inventory tab and Inventory View—When an inventory search is based the vulnerability name or severity, the results now include any inventory item that is associated with the unsuppressed vulnerability in the project.

•

Alerts—Any alert that was automatically closed in the project due to the previous vulnerability suppression is automatically reopened in the project. Additionally, open and closed alert counts are adjusted on the Project Inventory tab, in the Analysis Workbench, and on the Inventory view.

Note:If, after unsuppressing the vulnerability, you want to change the status or priority of the alert for the impacted inventory item in the project, see Managing Security Vulnerability Alerts.

•

Subsequent scans and rescans—Once a vulnerability is unsuppressed, it is reflected in the results of subsequent rescans and initial scans, whether incremental or full, on the project.