Alex Smirnoff

..that's because we frequently use severity 0 instead of severity 4. severity 4 is actually unused, which is not right. we should modify all scanner output parsers to reflect this...

I guess a one-line fix for nessus2ivil would be appropriate ;-) On Wed, Oct 1, 2014 at 1:44 PM, Frank Breedijk [email protected] wrote: > This only true for Nessus. Other...

Makes sense! But at the moment GUI thinks that 1 is High (critical is the same), 2 is medium, 3 is low, 4 is info and 5 is unassigned. And...

..as it is in the database: mysql> select \* from severity; +----+---------+------------------------------------------------------------------------------------------------------------------------------------+ | id | name | description | +----+---------+------------------------------------------------------------------------------------------------------------------------------------+ | 0 | Not set | No serverity has been...

And after 3 years this issue, which requires a few one-line fixes, is still there. I think i will take the liberty to spend just one day to fix it...

Not quite straightfoward thing to do. Since scan policies are stored scanner-side (for Nessus and OpenVAS, at least), you need to re-run complete scan against specified target. But it would...

update: checked xmlrpc protocol spec, it is possible and should not be very complicated

Gave it a second thought. The general idea is to keep findings forever, but add id or timestamp to each scan and insert with new ID instead of update. This...

I do not see any discussion regarding that, could you please provide more details when this feature is planned and what can I contribute?

[ark@puzzlebox seccubus]$ grep -r finding_history /opt/seccubus [ark@puzzlebox seccubus]$ ``` MariaDB [seccubus]> show tables; +-----------------------+ | Tables_in_seccubus | +-----------------------+ | attachments | | checkpoints | | config | | events |...