Nessus is just reporting the OS version, however that capability only works correctly if it can log into Windows and scan SMB shares (which it can't here). When it doesn't work, it just takes a guess based on some other behaviors it sees. In fact, it reports an array of possible OS versions. Not super helpful, really.
The problem for us now, is since 2003 is unsupported, we should not have it running any longer on our network (even in an array), and now that the Nessus result has been viewed by a security auditor, we have to prove its not 2003 :-/
So, I'm not looking for Nessus help per se, I'm looking for a VNX OS identification method. Any ideas?
Rainer_EMC
4 Operator
•
8.6K Posts
0
June 19th, 2019 06:00
I would suggest to look into the knowledgebase for the specific warning that Nessus is showing
steve217
3 Posts
0
June 19th, 2019 12:00
Nessus is just reporting the OS version, however that capability only works correctly if it can log into Windows and scan SMB shares (which it can't here). When it doesn't work, it just takes a guess based on some other behaviors it sees. In fact, it reports an array of possible OS versions. Not super helpful, really.
The problem for us now, is since 2003 is unsupported, we should not have it running any longer on our network (even in an array), and now that the Nessus result has been viewed by a security auditor, we have to prove its not 2003 :-/
So, I'm not looking for Nessus help per se, I'm looking for a VNX OS identification method. Any ideas?
ikar.us
5 Posts
0
August 27th, 2019 05:00
Ehm, what about just logging in and reading the Software Version info?
The underlying system isn't a Windows at all, the guess is totally wrong.