This means that even though they can protect communications, even across multiple sites that you or trusted parties control, and are better than the default certificates that Splunk software provides, they are not as secure as those which you obtain from a third-party CA.
Because you sign these certificates yourself, third parties can't validate them. Additionally, you can create the certificates whenever you need and they are ready for use immediately after you create them, for as long as you need them. If you are not able to acquire certificates from a third party, or your Splunk platform deployment receives protection from firewalls or other network infrastructure, you can secure the contact points in the deployment by creating and signing TLS certificates yourself.Īs you are the certificate authority in this scenario, there is no cost to creating and signing certificates on your own. It's a Splunk best practice to use third-party TLS certs on the Splunk platform infrastructure that you manage. Splunk uses TLS certificates to protect Splunk Cloud Platform deployments and forwarders that connect to those deployments. Transport layer security (TLS) certificates that come from third parties are the most secure way to protect communications between your Splunk platform infrastructure from potential security breaches.
SPLUNK SSL CERTIFICATE HOW TO
How to create and sign your own TLS certificates
0 kommentar(er)
