Skip to main content
Splunk Lantern

Adding compliance data to syslog data in stream


When routing data from Splunk Connect for Syslog (SC4S), you may need to add fields for compliance. For example, you may need tag data that come from the PCI zone. SC4S can attach indexed fields to matching events as they are processed. This is achieved by editing the configuration files that work in unison to identify and enrich the events:

  • compliance_meta_by_source.csv, located in /opt/sc4s/local/context, and contains a “key” that is referenced in the log path for each data source 
  • compliance_meta_by_source.conf, located in /opt/sc4s/local/context, and contains the filter to match events

The example edits below creates a filter called "f_pcidata" that matches to the subnet and adds the fields "compliance", "datacentre", and "country" to every event that matches.


f_pcidata,,"New Zealand"


filter f_pcidata {

Next steps

These additional Splunk resources might help you understand and implement this use case:

Finally, you might be interested in other processes associated with the Understanding best practices for Splunk Connect for Syslog use case.