DNA scan for Linux server we got below error “ no matching host key found”

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

DNA scan for Linux server we got below error “ no matching host key found”

L4 Transporter

Hi All,

 

Performing DNA scan for linux machines for different OS versions of linux.

 

DNA version used : 8.3.0.6

 

getting below responses.

 

Operation System version could not be detected. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond - 7.9, 8.6,8.10

 

Operation System version could not be detected. Error: An established connection was aborted by the server.--- 8.10

 

Operation System version could not be detected. Error: An existing connection was forcibly closed by the remote host ---8.10

 

Operation System version could not be detected. Error: SSH Authentication Failure. Error message: Permission denied (password).--7.7

 

Also, need help to confirm any of these below modern host key algorithms supported by CyberArk?:

 

ssh-ed25519 

ecdsa-sha2-nistp256 

rsa-sha2-256 and rsa-sha2-512

-------------------------------------------

Can someone please help with the set of permissions[commands] that the account should have for scanning ESXI servers.

 

TIA,

2 REPLIES 2

L4 Transporter

Field_Content_versions_oct20__068Vy00001FYuoDIAT.png 

I checked the CyberArk DNA documentation and some community discussions — this behavior is actually pretty common with older DNA versions.

DNA 8.3.x has limitations with modern SSH configurations. Many newer Linux builds disable legacy SSH algorithms by default, and if the server only allows modern host key algorithms, the scanner may fail during the SSH handshake. That’s when you see errors like “no matching host key found”, connection aborts, or OS detection failures.

Also, the DNA documentation talks about SSH key discovery and compliance checks, but it doesn’t clearly state support for newer host key negotiation (like ed25519 or RSA SHA-2 variants). So even if the server is perfectly healthy, the scanner itself may not be able to agree on an algorithm.

This is different from authentication failures — in these cases the connection itself doesn’t complete because the crypto negotiation fails early.

From what others have seen, this usually happens in hardened environments where legacy algorithms are disabled.

 

If you’re on an older DNA build, compatibility with modern SSH hardening can be an issue. Either validate algorithm compatibility or consider using a newer supported version for better interoperability.

  • 57 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!