How to update SecureRecon to v. 5 on Nessus servers

Article:HOWTO31171  |  Created: 2010-08-11  |  Updated: 2012-07-24  |  Article URL http://www.symantec.com/docs/HOWTO31171
Article Type
How To



To upgrade your installation of SecureRecon to version 5, follow these steps:

1.  Suspend vulnerability scanning in the Risk Automation Suite Portal

Module Management -> Vulnerablity -> Scan Scheduling, click "Suspend Vulnerability Scanning". Reset any active scans listed in the vulnerability scan queue.

2. Log on to the linux server that hosts Nessus.
3. Transfer the new SecureRecon file(s) to the linux server.
4. Run the commands "killall securerecon", "killall nessusd", "killall nessus" to stop the current services.
5. Copy the SecureRecon folder to a new folder named securerecon.old
6. Copy the new SecureRecon files into the /securerecon folder, overwriting the old files.
7. Run the command "chmod 700 securerecon" to set the SecureRecon file permissions to execute mode.
8. Recreate the symlinks
a. ln -s /opt/nessus/bin/nessus nessus
b. ln -s /opt/nessus/sbin/nessus-service nessusd
          c. ln -s /opt/nessus/sbin/nessus-update-plugins nessus-update-plugins
9. Run ./SecureRecon -r <ip or name of portal> <regisration user> <password>
10. Run ./SecureRecon -s
Defaults-
config file location - /opt/nessus/etc/nessus
plugin location - /opt/nessus/lib/nessus/plugins
port - 1241

Modify the startsr script to run in the background
1. cd /root
2. cp startsr startsr.old
3. Open startsr with vi or nano or another text editor
4.Modify the line that starts with sh -c to sh -c "/<SecureRecon folder>/SecureRecon &" >> dev/null 2>&1  
5. Run startsr
 
Verify the SecureRecon service is running "ps ef | grep securerecon"
Log in to the portal and go to Portal Administration >> Scanner Management, activate the new SecureRecon scanner and verify that it is checking-in.
 
It may take a few minutes for the client to report in since it updates first, wait 10 minutes or so if it doesn't immediately check in.


Article URL http://www.symantec.com/docs/HOWTO31171


Terms of use for this information are found in Legal Notices