Specifications

Copyright © 2015. Tenable Network Security, Inc. All rights reserved. Tenable Network Security and Nessus are registered trademarks of Tenable Network Security, Inc.
68
throttle_scan
Throttle scan when CPU is overloaded.
use_kernel_congestion_
detection
Use Linux’s TCP congestion messages to scale back scan activity as required.
www_logfile
Location where the Nessus Web Server (user interface) log is stored.
xmlrpc_idle_session_
timeout
XMLRPC Idle Session Timeout in minutes. (0 for no timeout).
xmlrpc_listen_port
Port for the Nessus Web Server to listen to (new XMLRPC protocol).
By default, report_crashes is set to “yes”. Information related to a crash in Nessus will be sent to Tenable to help
debug issues and provide the highest quality software possible. No personal or system-identifying information is sent to
Tenable. This setting may be set to “no” by a Nessus admin user.
Configuring Nessus with Custom SSL Certificate
The default installation of Nessus uses a self-signed SSL certificate. When first using the web interface to access the
Nessus scanner, your web browser will display an error indicating the certificate is not trusted:
To avoid browser warnings, a custom SSL certificate specific to your organization can be used. During the installation,
Nessus creates two files that make up the certificate: servercert.pem and serverkey.pem. These files must be
replaced with certificate files generated by your organization or a trusted Certificate Authority (CA).
Before replacing the certificate files, stop the Nessus server. Replace the two files and re-start the Nessus server.
Subsequent connections to the scanner should not display an error if the certificate was generated by a trusted CA.