Forwarding to IBM QRadar
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 event forwarding.
Configure Standard Integration
To forward event data to IBM QRadar:
Log in to Sysdig Secure as Admin and go to Profile > Settings > Event Forwarding.
Click +Add Integration and choose IBM QRadar from the drop-down menu.
Although QRadar receives Syslog messages, it uses LEEF format. Using Syslog as the source type will potentially generate incompatible messages with IBM QRadar.
Configure the required options:
Integration Name: Define an integration name.
Address: Specify the DNS address of the QRadar installation endpoint.
Port: TCP Port to send data. 514 is the default
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.
Allow insecure connections: Toggle on if 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.
Configure Agent Local Forwarding
Review the configuration steps and use the following parameters for this integration.
|QRADAR||address||yes||string||DNS name or IP of the QRadar instance|
|QRADAR||port||yes||int||Port exposed to receive Syslog events. 6514 or 514 by default.|
|QRADAR||insecure||no||bool||false||Doesn’t verify TLS certificate|
See IBM Documentation for information on log sources.
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.