Tenable Security Center

Collect Diagnostics File

Use this section when troubleshooting software crashes, service failures, or installation errors.

To collect a diagnostics file for Tenable Security Center:

1. In the left navigation, click System > Diagnostics.

   The Diagnostics page appears.

   

2. In the Diagnostics File section, click Create Diagnostics File.

   The page updates with configuration options.

3. In the General section, if you want to omit IP addresses from the file, enable Strip IPs from Chapters.

4. In the Chapters section, enable the chapters you want to include.

5. Click Generate File.

6. Click Download Diagnostics File.

7. Submit the debug.zip file to your support case.

Collect Debugging Logs

Use this section when troubleshooting software crashes, service failures, or installation errors.

To collect debugging logs for Tenable Security Center:

1. In the left navigation, click System > Diagnostics.

   The Diagnostics page appears.

2. In the Debugging Logs section, select the debugging logs Tenable Support asked you to enable.

   

3. Click Save Debug Settings.

4. Reproduce the issue.

5. In the Download Debugging Logs section, click Collect Log Files.

6. Click Download Debug File.

7. Submit the file to your support case, then disable the debugging logs.

Troubleshooting Tenable Security Center Agent Scans

Tenable Security Center cannot run diagnostic Agent scans directly. Because the agent scans are imported as final results, the granular debugging data required for troubleshooting (Plugin Debugging and Audit Trails) is stripped out before it reaches Tenable Security Center.

To troubleshoot issues such as false positives or authentication failures on a Tenable Security Center agent target, you must reproduce the scan on a platform that supports direct agent control ( Tenable Nessus Manager or Tenable One Vulnerability Management).

To reproduce the scan:

1. Note the IP address or hostname and the specific policy settings causing the issue in Tenable Security Center.

2. Log in to the Tenable Nessus Manager or Tenable One Vulnerability Management instance where the agent reports.

3. Follow the steps in Tenable Agents for Tenable Agents to enable Include Audit Trail Data and Include KB Data in the Tenable Nessus Manager settings.

4. Create a scan policy on the Tenable Nessus Manager that matches the settings in Tenable Security Center and run it against the target agent.

5. Once the scan completes, follow the steps in Tenable Agents for Tenable Agents to export the Tenable Nessus DB directly from the Tenable Nessus Manager.

6. Send this Tenable Nessus DB to Tenable Support. The DB contains the diagnostic data that Tenable Security Center could not capture.