Debug Log Reporting

Debug logs for the ARCON integration are attached to scan results as a Debugging Log Report plugin attachment. The log file is named <plugin-name>.nasl~Arcon. For example, ssh_settings.nasl~Arcon or logins.nasl~Arcon

The debug log records:

• Configuration values (host, port, authentication URL, engine URL, API user, username, and target type)

• Login success or failure, including any API error messages

• Credential retrieval success or failure per target

• Cache hits and misses (keyed by username + target IP + type)

• Escalation credential retrieval results

When troubleshooting, use the ~Arcon log rather than the target authentication log, as the target log only reflects whether the login to the scan target succeeded, not whether the ARCON credential retrieval succeeded.

Common Causes of Credentialed Check Failure

• The API user does not have permission to check out credentials for the target account in ARCON.

• The target's IP address does not match an account address registered in ARCON.

• The specified username does not exist in ARCON for the target system.

• The ARCON API is unreachable from the scanner.

• An incorrect or expired SSL certificate when Verify SSL Certificate is enabled.

• Mismatched Authentication URL or Engine URL (for example, using a Legacy URL with a Digital Vault deployment).

• The ARCON API response exceeded the read timeout — the integration uses an extended HTTP timeout but very large scans against a slow ARCON deployment may still be affected.