Forwarding to Splunk
Event forwards originate from region-specific IPs. For the full list of outbound IPs by region, see SaaS Regions and IP Ranges. Update your firewall and allow inbound requests from these IP addresses to enable Sysdig to handle Splunk event forwarding.
Configure Standard Event Forwarding
To forward event data to Splunk:
Log in to Sysdig Secure as Admin and go to Profile > Settings > Event Forwarding.
Click +Add Integration and choose Splunk from the drop-down menu.
Configure the required options:
Integration Name: Define an integration name.
URL: Define the URL of the Splunk service. This is the HTTP Event Collector that forwards the events to a Splunk deployment. Be sure to use the format
Token: This is the token that Sysdig uses to authenticate the connection to the HTTP Event Collector. This token is created when you create the Splunk Event Collector.
Optional: Configure additional Splunk parameters (Index, Source, Source Type) as desired.
Certificate: If you have configured Certificates Management tool, you can select one of your uploaded certs here.
Index: The index where events are stored. Specify the Index if you have selected one while configuring the HTTP Event Collector.
Source Type: Identifies the data structure of the event. For more information, see Source Type.
For more information on these parameters, see the Splunk documentation.
If left empty, each data type will have a source type. See Appendix: Data Categories Mapped to Source Types for details.
Data to Send: Select from the drop-down the types of Sysdig data that should be forwarded. The available list depends on the Sysdig features and products you have enabled.
Select whether or not you want to allow insecure connections (i.e. invalid or self-signed certificate on the receiving side).
Toggle the enable switch as necessary. Remember that you will need to “Test Integration” with the button below before enabling the integration.
Here is an example of how policy events forwarded from Sysdig Secure are displayed on Splunk:
Configure Agent Local Forwarding
Review the configuration steps and use the following parameters for this integration.
|SPLUNK||ServiceToken||yes||string||HTTP Event Collector Token|
|SPLUNK||ServiceURL||yes||string||URL of the Splunk instance|
|SPLUNK||Index||no||string||index to send data to. If unspecified, it will be used the index specified on the HTTP Event Collector configuration on Splunk.|
|SPLUNK||ServiceType||no||string||tcp, udp||tcp||protocol, tcp or udp (case insensitive)|
|SPLUNK||insecure||no||bool||true||Doesn’t verify TLS certificate|
Reference: Data Categories Mapped to Source Types
|Sysdig Data Type||Splunk Source Type|
|Policy Events (Legacy)||SysdigPolicy|
|Sysdig Platform Audit||SysdigSecureEvents|
|Benchmark Events (Legacy)||SysdigSecureEvents|
|Secure events compliance (Legacy)||SysdigSecureEvents|
|Host Vulnerabilities (Legacy)||SysdigSecureEvents|
|Runtime Policy Events||SysdigSecureEvents|
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.