If you can't patch A for some reason, you'd still want to know about B. Also, what if B is of a higher severity than A? This probably doesn't happen too often, but could be a possibility.
Jamie Starkel On Wed, Feb 17, 2010 at 11:17 AM, Albert R. Campa <[email protected]> wrote: > What do you guys think of scanning and reporting of cumulative > vulnerabilities? > > For example. If you have vulnerability A that supercedes vulnerability > B. Nessus will report both A and B as vulnerable, but for patching > only Vulnerability A needs to be patched. So why report vulnerability > B? Should the scanner ingore superceded vulnerabilities? Is the only > plus to reporting both A and B is to have a history of old > vulnerabilities not patched? > > What about metrics? A and B might be vulnerable but only patch A needs > to be installed. > > > If an admin gets a vuln report with both A and B, can they easily > figure out oh, this is cumulative, so I only need to install A, or are > they going to try to install both. > > > want to get more opinions on this. > > > > __________________________________ > Albert R. Campa > _______________________________________________ > Pauldotcom mailing list > [email protected] > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > Main Web Site: http://pauldotcom.com >
_______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
