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]

nessus 3.0 and hping in scan, inconsistent results

Subject: nessus 3.0 and hping in scan, inconsistent results
Date: Fri, 16 Dec 2005 18:19:46 -0500
This is the scenario; I use hping to perform my host enumeration. I use
select tcp and udp ports. This way I will potentially find hosts behind
firewalls. I then use nmap for service identification. I then feed the
nmap results into nessus using the nmap nasl wrapper. In the nessus
config I disabled all other port scanning options other than the nmap
nasl wrapper. I get back proper nessus results for hosts that are not
behind a firewall. For hosts that are behind a firewall I get back
nothing from nessus. The report says that the host is not even up???? If
nmap comes back with port 80 and 22 open on a host that is behind a
firewall, why would nessus come back with a blank report that says the
host is not alive? Why isn't it running the port 80 and 22 pluggins
against that host?

 

Daniel Pinsky, CISSP, CCSE

 

 

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>