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: Securing nessusd

Subject: RE: Securing nessusd
Date: Thu, 14 Sep 2006 12:56:48 +0200
Another way to secure a nessus scanner is to completly disable 
login/password nessus accounts and use only 
key exchanges.
You can achieve this by removing all "hash" files under the users 
directory

Cordialement / Mit freundlichen GrÃÃen / Best regards, 
_____________________________________________
Patrice Arnal
ISS - DataCenter â E&S 
Mailto: patrice.arnal@alcatel.fr 
_____________________________________________



"Jim Hendrick" <jrhendri@maine.rr.com> 
Sent by: nessus-bounces@list.nessus.org
14/09/2006 12:44

To
<pderwael@webandco.be>, <nessus@list.nessus.org>
cc

Subject
RE: Securing nessusd






For your box, look at using iptables. 

Set up a simple rule to allow the hosts/networks you want to connect and
allow the rest to drop through to the (hopefully already existing) deny 
all.

Syntax is pretty straightforward and if you run it from the command line 
it
will not survive reboots so you can "undo" your changes.

Also look at iptables-save and iptables-restore to preserve your existing
state.

Later,
Jim

-----Original Message-----
From: nessus-bounces@list.nessus.org 
[mailto:nessus-bounces@list.nessus.org] On Behalf Of Patrick Derwael
Sent: Thursday, September 14, 2006 4:05 AM
To: nessus@list.nessus.org
Subject: Securing nessusd


Hi list,

I'm in a process of securing my Nessus scanner.
Currently, the scanner runs with the default startup options 
(-D -q), which makes it accessible by anyone. I want it to 
reject any connection attempt, except from 2 IPs (adding the 
-a option)

The scanner'IP (on a RedHat box) is x.y.z.218, and I'm 
running NessusWX on x.y.z.219. When I start the daemon with 
"nessusd -D -q -a x.y.z.218,x.y.z.219", it rejects every 
connection, including those from x.y.z.218/219.

Does that mean that -a only accepts one single IP, or am I 
doing something wrong ?????


-- 
Web and Co
Patrick Derwael
Rue Hubert Larock, 20
4280 Hannut
email: pderwael@webandco.be
http://www.webandco.be

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



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


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