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: how to run attacks using nessus

Subject: Re: how to run attacks using nessus
Date: Wed, 09 May 2007 10:33:22 -0400
Girish wrote:
Hello Ron,

That was an excellent link.
Please tell me one more thing, like if I have to scan all the protocols
over
TCP of a host behind the firewall from external world, should I have a
policy for allowing all TCP traffic in my firewall?
I hope am correct. Please correct me if I am wrong. I can proceed soon.


Typically, you should perform a full scan from outside your firewall to
 an internal system and analyze the results. Performing a full port scan
should find allowed access to the internal systems.

Although out of scope for this mailing list, things you should consider:

- the firewall might allow access to a port closed on your target host.
If this is against policy, you might not find this with a basic scan.

- you should audit what is logged by the firewall. If your policy is to
log all blocked connections, you should see logs for your scan.

- don't forget to consider filtering that may be in place by the host, a
network device and the firewall.

Ron

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

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