Fwd: managing scan reports + launching nessus script

this is useful, especially for small scans as you will always need more or
less raw tool output.
Raw tool output for large scans is however in my experience on large
networks with similar tools unreadable and unmanageable.

my ,02:
you therefore need database output primarily.
you then need to confirm the (OS) type of the devices as the automatic
recognition may imperfect, you need to find out their location, then you
need to identify the owner of the devices and the team(s) responsible for
getting each of them fixed
you can now generate a table with this information and link it to the
database (via IP address)

This way you can decide what to fix (how), whom you need to inform about it,
who does what and when you need to get it done

The raw output is then useful to these expert teams who need to find out
what the tool actually reported/believed was the problem.

A J Caruana

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus