Alex Kuchta

@akajeremy *.nessus files can be generated for two types of scans within ACAS: 1. **Vulnerability Scans:** These are the scans that contain *non-compliance* plugins and provide feedback as to a...

@Zeluha please take a look at #172 - I think that the comment that I just posted should answer your question!

@CyberSecDef is correct, this is not necessarily a Vulnerator issue. However, that doesn't mean that I am not addressing it :). One of the items that I have built into...

@MichaelM00 I never coded it into the previous versions to handle the severity override values (along with a handful of others). I'll ensure that all values are handled in upcoming...

@ibjohn is there any reason that filtering does not suit your needs? And on which reports would you want the color coding to be?

@CyberSecDef @ibjohn I can definitely look into creating some coloring options... The question is, how do we want coloring done? - Status? - Finding Type? - Mitigation populated? - ???...

@CyberSecDef I need to learn to be clearer in my conveyance of thoughts... I was thinking of highlighting Status based on the text (e.g. green for "Completed", grey for "Not...

@flickerfly Sorry for the delayed response! At a high level, @lazious is correct - the current focus of Vulnerator (as it's currently designed) is to take the plethora of data...

@holmesbt I have actually already worked this into the next release - the intention is to generate a separate PPS report, which I think will provide more insight than adding...

@IvanDrag0 thank you for the report! It looks like you are using the latest code, which is still very much in flux. I've been working on some additional database changes,...