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. |

| Subject: | Re: Access control rules |
|---|---|
| Date: | Wed, 19 Mar 2008 20:11:47 +0100 |
On Mar 19, 2008, at 6:22 PM, Mark Adams wrote:
According to the Nessus 3.2 news release (http://www.nessus.org/ news/) one of the new features is "Granular access to control rules to limit users to specific ports and audits". Does anyone know how to do this?
Basically you can write :
Global networks/host denies :
reject 192.168.2.0/24
Reject a given port on a given network :
reject 192.168.2.0/24:9100
You can reject a port range too :
reject 192.168.2.0/24:1-1024
And you can also forbid the use of some plugins :
plugin-reject 10330 plugin-reject 10000-11000
-- Renaud
_______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RHEL Kernel Security Hole Issue, Renaud Deraison (lists) |
|---|---|
| Next by Date: | Re: Nikto in Nessus Report, Yanyan Wang |
| Previous by Thread: | RE: Access control rules, Rushing, Derek |
| Next by Thread: | RHEL Kernel Security Hole Issue, Robert Fell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |