swbruce21
asked on
How to Limit Nessus plugins to checking a single port or a short list of explicit ports.
Some firewalls have a real-time countermeasure blacklisting the source IP of a scan after it hits 3 or so ports. If I know that 443 or 8080 are open and I want Nessus to check for vulnerabilities on those ports without tripping the blacklist, how can I limit Nessus to 443 and/or 8080. Limiting the "Scanning" built into Nessus does not seem limit the ports checked by the plugins. Other than setting up some external outbound packet filtering, is there a way to limit the Nessus plugins to a single port.
scaliouette
Nessus may be a free utility but I imagine that its specific to whatever the software was originally intended to do. Unless there are particular switches built into the application, you may need to contact the creator of this software.
I don't have my laptop in front of me... that is my hacking rig....
but, there is a file in nessus that details the default ports to scan... I believe it is called nessus-services.
I bet if you edit that file to only include what you want to scan, you would be good to go.
You could also use the user rules to only allow a certain nessus user to scan certain ports...
Most people never setup user rules, my self included, so you would have to research the exact rule syntax yourself....
but for sure nessus can do what you want.
but, there is a file in nessus that details the default ports to scan... I believe it is called nessus-services.
I bet if you edit that file to only include what you want to scan, you would be good to go.
You could also use the user rules to only allow a certain nessus user to scan certain ports...
Most people never setup user rules, my self included, so you would have to research the exact rule syntax yourself....
but for sure nessus can do what you want.
ASKER
I will do a test again but the scan setting only seems to control the preliminary scans, not the plugins.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guess there isn't a good answer to this question. The plugins test ports based on their own hard-wired design, so there is no simple way to confine all activity to a single port on the target. ( that's my conclusion at this time - it could be wrong )