https://community.splunk.com/t5/Getting-Data-In/Qualys-scan-detecting-various-SSL-certificate-vulnerabilities/m-p/424379#M74461 <P>Our Qualys report detected various SSL certificate vulnerabilities for any devices using Splunk universal forwarder via 8090. We have deployment server configured to push configuration to servers running Splunk agent. After doing some research it appears we need to create a certificate on the deployment server and distribute to any server running Splunk agent. I'm curious to know which certificates I need to distribute. I was able to create self-sign certificates on the deployment server. I would like to resolve vulnerabilities detected by Qualys. I found the following documentation that cert authentication is not recommended for deployment and clients. - <A href="https://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Securingyourdeploymentserverandclients">https://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Securingyourdeploymentserverandclients</A> </P> <P>Additional information:<BR /> <A href="http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Howtoself-signcertificates">http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Howtoself-signcertificates</A> <BR /> <A href="http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/HowtoprepareyoursignedcertificatesforSplunk">http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/HowtoprepareyoursignedcertificatesforSplunk</A> </P> <P>Qualys Vulnerabilities:<BR /> • X.509 Certificate SHA1 Signature Collision Vulnerability<BR /><BR /> • SSL Certificate - Self-Signed Certificate<BR /><BR /> • SSL Certificate - Expired<BR /><BR /> • SSL Certificate - Subject Common Name Does Not Match Server FQDN<BR /><BR /> • SSL Certificate - Signature Verification Failed Vulnerability<BR /><BR /> • HTTP Security Header Not Detected </P> Wed, 30 May 2018 17:28:31 GMT afamuyiwa 2018-05-30T17:28:31Z https://community.splunk.com/t5/Getting-Data-In/Qualys-scan-detecting-various-SSL-certificate-vulnerabilities/m-p/424379#M74461 <P>Our Qualys report detected various SSL certificate vulnerabilities for any devices using Splunk universal forwarder via 8090. We have deployment server configured to push configuration to servers running Splunk agent. After doing some research it appears we need to create a certificate on the deployment server and distribute to any server running Splunk agent. I'm curious to know which certificates I need to distribute. I was able to create self-sign certificates on the deployment server. I would like to resolve vulnerabilities detected by Qualys. I found the following documentation that cert authentication is not recommended for deployment and clients. - <A href="https://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Securingyourdeploymentserverandclients">https://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Securingyourdeploymentserverandclients</A> </P> <P>Additional information:<BR /> <A href="http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Howtoself-signcertificates">http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/Howtoself-signcertificates</A> <BR /> <A href="http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/HowtoprepareyoursignedcertificatesforSplunk">http://docs.splunk.com/Documentation/Splunk/7.1.0/Security/HowtoprepareyoursignedcertificatesforSplunk</A> </P> <P>Qualys Vulnerabilities:<BR /> • X.509 Certificate SHA1 Signature Collision Vulnerability<BR /><BR /> • SSL Certificate - Self-Signed Certificate<BR /><BR /> • SSL Certificate - Expired<BR /><BR /> • SSL Certificate - Subject Common Name Does Not Match Server FQDN<BR /><BR /> • SSL Certificate - Signature Verification Failed Vulnerability<BR /><BR /> • HTTP Security Header Not Detected </P> Wed, 30 May 2018 17:28:31 GMT https://community.splunk.com/t5/Getting-Data-In/Qualys-scan-detecting-various-SSL-certificate-vulnerabilities/m-p/424379#M74461 afamuyiwa 2018-05-30T17:28:31Z