Debug Log Reporting

The debug logging settings in Tenable Nessus control the output to the debug logging report. If the integration fails, enable debug log reporting (Tenable recommends level 3 or 4) and review the nutanix_collect.nasl~Nutanix Prism Central log file within the debugging log report.

What the Logs Contain

The debug logs record the full integration lifecycle for each scan, including:

• Configuration settings from the scan policy, with sensitive values masked.

• The authentication method used and whether authentication succeeded.

• The Nutanix API requests and the HTTP response status.

• Details on host(s), virtual machine, and cluster information collection.

• Any errors returned by the Nutanix API, including authentication failures.

Common reasons for a failed collection of hosts and virtual machines

• Authentication to the Nutanix API failed, so no data was retrieved. This can be due to incorrect username or password credentials.

• Verify SSL Certificate is enabled in the scan policy while the Nutanix server presents a self-signed certificate.

• The environment is a mixed-version deployment in which the REST API is unavailable on some hosts.

• The scanner cannot reach the Prism Central host over the network.

• The Nutanix Port value does not match the port the Prism Central host listens on (9440 by default).