topic Deployment of configuration files in Deployment Architecture

Deployment of configuration files

I29851 — Tue, 30 Nov 2021 12:46:31 GMT

Last week one of our vulnerability scan found out that our universal forwarders were suspectable to TLS CRIME vulnerability. To fix this vulnerability we updated our server configuration file (toggled allowSslCompression from True to False). Now we want to update server configuration file on all the servers but we found that server configuration is system specific and we can’t just replace it on every server.

We are not using deployment server in our environment. Is there any other way wherein we can go and append server config file?

Thank you

Re: Deployment of configuration files

richgalloway — Tue, 30 Nov 2021 20:11:36 GMT

This Answer addresses the vulnerabilty: https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-shows-vulnerable-to-CVE-2012-4929-in-my-Nessus/td-p/29091 . It's a bit old, however.

As for how to deploy config files, this is why the Deployment Server exists. It allows a Splunk admin to make a few changes in one place and have the automatically propagate to deployment clients. The Cluster Manager the SHC deployer serve the same role for clustered indexers and search heads, respectively.

You can also use a third-party tool such as SCCM, Puppet, or Ansible.