Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • For organizations migrating from library-based alerts to vulnerability-based alerts, the email of the user who performed the last change in the alert’s status will not appear in the UI or the exported reports for License and Compliance Alerts that were raised in the old library-based mode (before the migration).

  • When clicking on the Vulnerability Analysis > Reported Vulnerability widget, the Security Alerts: View by Library page is opened without being filtered for the selected data.

  • When clicking on the Vulnerability Analysis > Effective Vulnerability widget, the Security Alerts: View by Vulnerability page is opened without being filtered for the selected data.

  • The order of the vulnerabilities in Security Alerts: View By Library exported Excel isn't the same as the one in the UI view. 

  • While working with the Licensing & Compliance Alerts page on a laptop screen, the Library column might not appear. This can be addressed by zooming out in your browser.

  • If a source library has multiple source files with the same vulnerability, the security alerts for each of these vulnerability occurrences will all have the same alert UUID.

  • If multiple source files with the same name are scanned to the same project, and they have the same vulnerability, the security alerts for each of these vulnerability occurrences will all have the same alert UUID.

Library-based Alerts

  • When the same source library appears more than once with different source files, a discrepancy exists between the per-vulnerability alerts counter and the Vulnerability Report/Risk report.

...