Wednesday, October 12, 2022

Vulnerability Management - Authentication not attempted

Your vulnerability scan did not find as many vulnerabilities as you were expecting in a normal authenticated scan? Even when credentials provided were correct. And then you are checking scan results and did not find any results for failed authentication as well. And then you start to scratch your head? Just kidding !!

So .. What to do now? Check whether the scanner was able to enumerate OS or not .. Why so? Because, if a scanner is not able to enumerate OS then it will not know what kind of device it is dealing with and hence will not attempt authentication itself (NO authentication attempted means NO failure logs). Check whether ports such as 445 or 22 were blocked (445 --> Windows and 22 --> Linux). So if you don't find any failure logs then it does NOT mean that authentication was successful. In this case you will not get any results for successful authentication either.

So .. If you want to get an idea about an environment, check "Critical" and "High" vulnerabilities. If you want to get an idea about the scan itself, check "Informational" findings. Don't underestimate the power of a [common man !!] .. oops .. I meant "Informational" findings.

This is one common scenario among other possible scenarios.

Happy Learning !!

No comments:

Post a Comment

Vulnerability Management - Understanding vulnerability posture

Understanding the vulnerability posture of an organisation at a basic level helps you drive remediation efforts. So, I don't know what t...