On Sat, 8 Feb 2003, Renaud Deraison wrote: > On Fri, Feb 07, 2003 at 11:17:36PM -0500, William Heinbockel wrote: > > This report can also perform verbose plugin reporting. For every test > > scheduled to run, it will tell you the plugin name, number, and whether > > the plugin found a vulnerability, ran successfully, or didn't run > > because one of it's dependencies was not satisfied. > > > And when you scan a class C, the client - server communication eats 40% > of the total bandwidth, right ? > > -- Renaud > Yes, that is why I'm configuring it as a Preference. The only thing that is sent over the wire, are the plugins that didn't run due to a dependency failure. This information would be really helpful when you are testing a hole class C for a specific vulnerability (for instance the Saphire worm). If a system is running potentially vulnerable software, and the test does not run, it would require the sysadmin to examine those machines. Currently, if a test is run, as long as no vulnerability is thrown, you assume that the test ran successfully and your system is okay.
This feature was only implemented for seeing the results of very few plugins (say one or two specific tests ran against the network). It is not meant to display the status of 1000 tests ran against a class C, since on average 90% of the tests will not run due to dependencies. Hopefully the database backend will eliminate the need for this. > > ---------------------- William Heinbockel Information Security Incident Response Assistant Co-op Risk & Safety Management Rochester Institute of Technology E-mail: [EMAIL PROTECTED]
