Him to be able to scan his own host only. Nessusd has a rules system which allows you to restrict the hosts The next step is to add an admin user on this box so it can connect, create profiles, policies and launch # /opt/nessus/sbin/nessus-adduserĭo you want this user to be a Nessus 'admin' user ? (can upload plugins, etc.) (y/n) : y
If auto_update is set to 'yes' in nf, Nessus willĪnd yes the activation code in the example if a fake one for demonstration purposes only. Your Nessus installation is now up-to-date. Now fetching the newest plugin set from.
Your activation code has been registered properly - thank you. Once you have the activation code you can proceed to activate it on your Backtrack Machine running as root: # /opt/nessus/bin/nessus-fetch -register M4D0-EWWQ-1EZU-3KSN If you will be using a Home Feed you will have to go to and register for a Home Feed, you will receive your activation code to the email you provided. So one of the first thing you need to do if using a professional feed go to and log in and go in to Manage Activation Codes and get your professional feed activation code. So moving the VM from one host to another or the USB drive depending on how you configured Backtrack is more than likely to require re-activation of your copy of Nessus.
Do not try to activate by running it from the bootable DVD or from a USB Drive if you intend of using it on several physical machines because the registration process marries the activation to that specific host. The first step is to have Bactrack installed as a virtual machine on your pentest/audit rig or installed locally on the hard drive of the machine.
I would like to share how to activate your copy of Nessus in Backtrack and some of the caveats that are present when activating it depending of your setup. Before I had to always follow some weird procedures some times to get Nessus installed on the early versions of Backtrack and those procedures where always prone to breaking when I had to update to a latest version. Ever since I started working professionally in security Nessus has been part of my toolkit, once nessuscmd was out it became more integral in to my workflow because I could automate stuff for my customers. So I was super happy to see it included as part of Backtrack.
One of my favorite tools in my toolbox is the Vulnerability Scanner Nessus, in part because of it’s accuracy and because I’m part of one of the teams that works adding new cool stuff to it during the day.