Forwarding to Splunk
Splunk event forwards originates from specific IPs, such as 22.214.171.124 for US -East. For the full list of outbound IPs in other regions, 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 Splunk Event Forwarding
To forward event data to Splunk:
Settingsmodule of the Sysdig Secure UI, navigate to the
Splunkfrom 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.
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, refer to the Splunk documentation.
Data to send: Currently, Sysdig only supports sending policy events.
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.
Savebutton to save the integration.
Here is an example of how policy events forwarded from Sysdig Secure is displayed on Splunk:
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.