Cthulhu

I may be #4 - remains to be seen.  We're taking bi-weekly vuln scan results to populate a metrics dashboard.  Some CVEs (vulns) have recurred on unique hosts due to using an older VM image that contains the vuln, or occasionally spinning up/shutting down a container image that contains the vuln.  We're tracking those as separate instances (x days between first and last scan vuln is present), and having a way to tag each instance will be helpful.  We have 80+ hosts and the accumulated scans are >300k rows and growing.  Power BI Desktop and PowerShell have been instrumental in making use/sense of the data. Powershell is used to extract the scan info from the xml .nessus file, reduce the data to the desired columns and metric info, then compare the previous scan to the current scan and output a file that contains flags for remediated CVEs.  Those files are used by Power BI to slice, dice & display the data.