Add an interactive Sankey diagram to vulnerability dashboard

[alexmitchelliii]

Goal

Add a quickly digestible view of an organization's vulnerable software that highlights the magnitude of risk based on different metrics shown in an interactive way that allows users to quickly select different categories of vulnerabilities and filter down to a granular list of those vulnerabilities and hosts containing them to initiate a remediation workflow.

Context

• This request was inspired by a LinkedIn post showing a Sankey diagram image that enables filtering by various characteristics.

• The way the chart works is that you can click on one of the segments, e.g. "CVSS 9-10" and then it will zoom in only on that segment. It will still show which "branches" come out of that segment. It will also update the total counts shown in the various parentheses.

• We can achieve similar outcome by allowing filtering and counting in the vulnerability dashboard's table without doing the chart.

Additional resources

1. A medium article referencing building Sankey diagrams here
2. And a link to the code referenced in that article here

Solution

• Allow user to filter by the attributes in the vulnerability table of the dashboard
• Include total counts that dynamically adjusts based on the filtering

[mikermcneil]

I think this should go to CX, so that @rachaelshaw remains the consistent designer. (Every issue goes to one product group.)

[zayhanlon]

@alexmitchelliii Did this come from our prospect or just a nice to have?

Please let us know if this is an official ask. Otherwise, we’re de-prioritizing this issue because it’s not likely to be worked on in the next 6 weeks. Please feel free to bring it back in a future product feature requests meeting.

[alexmitchelliii]

It's a nice to have.

[zayhanlon]

@alexmitchelliii So there's a really limited version plugin of this that's possible to do in the dashboard (not super pretty), but it is not possible to make it interactive, which means we're not really providing new information or functionality. We've decided to deprioritize the issue for now, but please let us know if it comes up again!