I recently ran a Nessus scan against a Solaris i386 server.  (please don't explain how solaris doesn't run on i386 boxes when I am currently running it, rather please go to the sun site and read up on it.)  The problem is that after I ran the scan I got a load of security issues regarding a service that normally isn't running.

Here's an excerpt from the log

Jan 28 13:03:57 server last message repeated 401 times
Jan 28 13:03:58 server inetd[201]: [ID 858011 daemon.warning] /usr/lib/fs/ufs/ufsd: Hangup


Now we've gone in and commented out the ufsd on this box and re run the inetd.

Here's my issue.  How do I determine within Nessus configuration (client side) which one of the plugins may have been responsible for this?  I know I can go to the nessus site and get the code for these plugins but how do I determine which plugin might be affecting the system I'm running the scan against?

I know I could possibly run an analyzer at the same time I'm running the scan but that might take a lot of paperwork.  (authorization etc.)

Frank Kenisky IV, CISSP, CISA
Information Technology Security Specialist
210-301-6433
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to