Target Credential Status by Authentication Protocol - No Credentials Provided

info Nessus Plugin ID 110723


Nessus was able to find common ports used for local checks, however, no credentials were provided in the scan policy.


Nessus was not able to successfully authenticate directly to the remote target on an available authentication protocol. Nessus was able to connect to the remote port and identify that the service running on the port supports an authentication protocol, but Nessus failed to authenticate to the remote service using the provided credentials. There may have been a protocol failure that prevented authentication from being attempted or all of the provided credentials for the authentication protocol may be invalid. See plugin output for error details.

Please note the following :

- This plugin reports per protocol, so it is possible for valid credentials to be provided for one protocol and not another. For example, authentication may succeed via SSH but fail via SMB, while no credentials were provided for an available SNMP service.

- Providing valid credentials for all available authentication protocols may improve scan coverage, but the value of successful authentication for a given protocol may vary from target to target depending upon what data (if any) is gathered from the target via that protocol. For example, successful authentication via SSH is more valuable for Linux targets than for Windows targets, and likewise successful authentication via SMB is more valuable for Windows targets than for Linux targets.

Plugin Details

Severity: Info

ID: 110723

File Name: no_local_checks_credentials.nasl

Version: 1.19

Type: summary

Family: Settings

Published: 6/27/2018

Updated: 2/13/2023

Reference Information

IAVB: 0001-B-0504