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]

Re: Port range for targets

Subject: Re: Port range for targets
Date: Thu, 7 Jun 2007 10:02:01 +0200

On Jun 7, 2007, at 2:50 AM, jason stallings wrote:

Is there a way to give a port range for each target in the external targets file...
is there a way at all?

No, you'd need to do a different scan for each target.

However, with the Nessus 3.1.x beta, what you can do is to define rules to forbid some ports for some targets -- that is, you end up sharing the same global port range but deny some ports to some hosts.

For instance, you could set the port range to 1-65535 and then poke some holes in that for every host in nessusd.rules :


# Forbid connecting on ports > 1024 for the 192.168.2.0/24 subnet reject 192.168.2.0/24:1024-65535

# Forbid connecting on port 80 on your router
reject 192.168.2.1:80

# Always reject connecting on port 9100
reject 0.0.0.0/0:9100


etc...

Note that if you modify nessusd.rules, you'll need to restart nessusd for the changes to take effect.



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

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