Scan Results Review

This section can help you interpret the results of your scans and debug failures.

Plugin Families and Plugins

The CyberArk Secrets Manager authentication is available for several different credential types, but in all cases the Privileged Access management (PAM) integration executes within the credential’s specific settings plugin, which is found in the Settings family.

The plugins that call the CyberArk Secrets Manager authentication are:

• Windows (SMB): logins.nasl

• SSH: ssh_settings.nasl

• Database: database_settings.nasl

• Nutanix: nutanix_settings.nasl

• VMware vCenter: vmware_vcenter_settings.nasl

• VMware ESXi: vmware_soap_settings.nasl

• SNMPv3: snmp_settings.nasl

Debug Log Reporting

To find debug logs specific to the CyberArk Secrets Manager, look for logs within the Debugging Log Report plugin output. The plugin output contains debugging logs for the Nessus plugins, including the respective settings plugins which use the CyberArk integration. You will see logs in the debug log reporting for the associated plugin with ~CyberArk Secrets Manager appended to it. For example, for SSH settings, debugging logs are found in ssh_settings.nasl~CyberArk.

The debug logs for CyberArk contain the details of how the settings plugin communicated with the PAM API. If an error occurred, its details are included in this log file. Errors may result in credentialed checks for the target failing. Common causes of errors include:

• Incorrect API key

• Incorrect value given for base URL, vault path or object ID

• Scanner unable to connect to CyberArk API

• Incorrect permissions