Getting Data In

Default Splunk Enterprise or Splunk Univeral Forwarder Config: Safe for Use in DMZ?

SplunkPersonal
Path Finder

Hello,

There are a number of use cases where it is valuable for Splunk to process data from clients that are outside the network. For instance, Sysmon combined with a Splunk Universal Forwarder on the client is a useful way to gather valuable forensics data from systems that are more vulnerable because they are outside the perimeter defenses. But forwarding this data requires either a Splunk Enterprise Server or a Splunk Universal Forwarder being accessible outside the network.

I had a question about the default configurations for a Splunk Enterprise Server and Splunk Universal Forwarder. If I install Splunk on a Server OS that is properly hardened, are the default configurations for Splunk Enterprise and a Splunk Universal Forwarder sufficiently hardened for those instances of Splunk to run in the DMZ where it is easier for malicious actors to attempt to exploit them? Or are there aspects of the default configurations that assume the servers will not be easily accessible outside a secured perimeter?

Thanks for any input you can offer.

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...