Secure and protect your Splunk Enterprise deployment network

Splunk Enterprise is designed to run on a trusted network, with limited or no access from the outside world. It is not designed to operate directly on the Internet without protections in place, such as a web application firewall (WAF), load balancer, or virtual private network (VPN).

Run Splunk Enterprise on a trusted network

In nearly all cases, run Splunk Enterprise deployments inside of a trusted network, in accordance with the security policy of your organization.

  • If you must expose your Splunk Enterprise deployment to the internet, consider deploying multiple redundant instances behind a web application firewall or load balancer
  • Limit external access through a VPN
  • Institute protections against distributed denial-of-service (DDoS) attacks and use services like rate limiting to reduce the number of requests that reach the deployment

Maintain stability on and accessibility to your Splunk Enterprise deployment

If Splunk Enterprise runs inside a trusted network, and you have provided network infrastructure to shield the deployment from potentially malicious outside actors, you can ensure the instance runs stably and as you expect by providing the environment with the computing infrastructure it needs to perform the workload that your organization requires. This includes, but is not limited to the following:

The Capacity Planning Manual has information on how Splunk Enterprise works with various reference computing hardware architectures and provides information on best practice for scaling the environment based on your specific workload needs.