Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Scan Troubleshooting How-to or Methodology

Subject: Scan Troubleshooting How-to or Methodology
Date: Wed, 5 Mar 2008 09:52:25 -0800
Hello,

I'm relatively new to Nessus troubleshooting and my question is 2 part:

1) I'm wondering what the best practices are for troubleshooting a scan.
For example, I have noticed people setting max_checks = 1.  Is there a
good how-to or methodology that others are successfully using?  I know I
can manually enable/disable plugins, but with so many plugins that seems
a bit old-school.  Isn't there some debugging that show exactly what is
being executed at what time, etc?

2) I would like to know exactly which plugins were executed against a
host.  This is the immediate problem I need to solve.  I enabled logging
and debugging, but I don't see all the plugins listed in the debug file
that ran.  For example, the MS SQL Server Brute Force plugin ran, but no
output or information was found in the debug file.

Any help greatly appreciated.

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

<Prev in Thread] Current Thread [Next in Thread>