- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
01-17-2024 10:39 AM
When performing a NESSUS scan of FW1, errors return:
Remote host was not identified as a known device or operating system and the execution of "uname -a" failed.
NESSUS returned the following error:
Enter old password:
This NESSUS scan works on three other FWs successfully
Plugin: ssh_get_info.nasl (#12634)
Plugin: no_local_checks_credentials.nasl (#110723)
The credentials have been validated within the scan policy... and works on three other FWs.
01-19-2024 11:53 AM
Hi @MichStrickland ,
I would check FW1 administrators and verify the Nessus scanner account is present and update the credentials to what is expected on the other firewalls.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!