I have a group of Windows 2012 R2 servers that keep getting "hits" on Nessus scans via ID 57582 & 51192 both regarding self-signed certs and ports 3389& 1433 RDP and SQL respectively
57582=SSL Self-Signed Certificate
51192=SSL Certificate Cannot Be Trusted
Can anyone give me a link on how to resolve these vulnerabilities: I found the below blurb during a search, but not enough info to resolve:
"DP (Port 3389) generates self-signing certificates by default. This will actually keep auto-generating these self-signed certs. I cannot find the Microsoft link we used to fix this, but I remember it. If the server is already issued a compliant certificate, you have to add it to the certificate store on the server, more specifically the private key tab. Once we did that, it leveraged the issued cert. and stopped auto-generating the self-signed ones and all the vulnerabilities went away. If you search for something like that, I am sure it will come up. We found it on the Microsoft Social TechNet forums, if that helps." "SQL (Port 1433) has a self-signed certificate created by the default installation, but can be configured as well."
Please help, Jim