Yes flaws from this past Tuesday. I have the direct feed plug-in, so I know i got the latest plugins. What i meant by everything looked good is that it was actually detecting the plugin ID vulnerability on the systems Nessus was scanning. Althought Microsoft categorized MS07-004 as a CRITICAL (High Priority), Nessus Plugin ID 24000 only detects it as a Medium Warning. But still it was detecting the medium status. According to the nessusd logs, the scan was successful and there were no errors. The reason I chose that subject line was because the only time I have seem something similar to this, is when you specifically tell your nessus client not to enable plugin dependency. In my case I am. I am just trying to look for causes in which my Nessus client would skip looking at the plugins, maybe because of authentication (which i double-checked), or some other dependency... Thanks. - amit
________________________________ From: [EMAIL PROTECTED] on behalf of George A. Theall Sent: Thu 1/11/2007 7:54 PM To: [email protected] Subject: Re: Plugin Dependency Not Working... On Thu, Jan 11, 2007 at 05:39:51PM -0500, Lad, Amit wrote: > Situation: I ran a full scan on my servers for the 3 latest > vulnerabilities that came out this week. Are you talking about the flaws Microsoft released patches for last Tuesday? > Everything works and looks > fine. What do you mean exactly? > Today when I re-ran the exact same scans/sessions, the scans are > not detecting any holes/warnings. I cross-checked some systems and the > system shows that the patch has not been applied, but Nessus doesn't > even recognize it. What do the nessusd logs say? Does your choice of subject line reflect an error you're seeing? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
