Hi, I’m trying to use Splunk as a log aggregation solution, and eventually as a SIEM. I have three industrial plants that are completely air-gapped, with no permanent internet access. The idea is to deploy a syslog server at each plant to collect logs locally and then forward them to a central Splunk installation. Any component or software will be: downloaded or installed during a temporary internet connection (via a cellular modem), then moved into a fully air-gapped production environment. I’ve reviewed SC4S (Splunk Connect for Syslog) through the official Splunk documentation and several videos. In theory, it looks like a very powerful and well-designed solution. However, in practice, I find the documentation quite difficult to follow, especially when considering: an air-gapped environment, no internet connectivity, and very large log volumes (high EPS / high throughput). My main questions are: From a practical and low-complexity perspective: Is it better to use SC4S, or to simply deploy syslog-ng or rsyslog (open-source solutions) on Linux servers at each plant and forward logs to the central Splunk instance? Best deployment model for an air-gapped industrial environment: SC4S standalone at each site? Simple syslog collectors with forwarding? Which option is more stable and easier to operate long term? Given a preference for open-source solutions: Is relying on syslog-ng / rsyslog considered a professionally acceptable approach with Splunk? Or has SC4S effectively become the best practice that should not be avoided? From an operating system perspective: Which is better suited for handling very large volumes of log data? Ubuntu Server CentOS / Rocky Linux / AlmaLinux Which is more stable and easier to maintain in a 24/7 production environment? The end goal: A stable solution Simple to operate Capable of handling very large data volumes Suitable for air-gapped industrial environments Without introducing excessive operational complexity I’m trying to find a balance between simplicity and best practices. I want to use Splunk correctly, but at the same time avoid introducing operational complexity that exceeds the team’s current capabilities. Any advice or real-world experience would be greatly appreciated.
... View more