Integrating IBM QRadar SIEM
This integration enables the Delinea Platform to forward JSON-formatted event logs to IBM QRadar SIEM using HTTPS webhooks. Logs are received by QRadar through an HTTP Receiver log source and parsed using a Universal DSM and Log Source Extension (LSX), allowing administrators to search and review Delinea Platform events in QRadar.
Benefits
This integration offers the following benefits:
-
Forwards Delinea Platform events to IBM QRadar SIEM.
-
Enables parsing of Delinea webhook JSON payloads in QRadar.
-
Allows searching of Delinea events by event name, username, and related fields.
Prerequisites
The integration of IBM Qradar SIEM with the Delinea Platform requires that the following requirements be met:
Delinea Platform
-
The Delinea Platform is properly provisioned and configured in your environment.
-
You have administrator permissions for managing webhooks in the Delinea Platform.
IBM QRadar
-
You have a QRadar instance with permissions to create incoming webhooks.
-
Admin access to the QRadar Console
-
HTTP Receiver log source capability (port open, TLS if required)
-
Access to DSM Editor and Log Source Extension (LSX)
Configuration
To enable the integration between IBM QRadar SIEM and the Delinea Platform, complete the following steps.
Step 1: Create an HTTP Receiver Log Source in QRadar
-
Log in to the QRadar Console.
-
Navigate to Admin > Log Sources > Add.
-
Configure the log source with the following settings:
-
Log Source Type: Universal DSM
-
Protocol: HTTP Receiver
-
Port: 12435 (example)
-
Method: POST
-
Coalescing: Off
-
-
Save the log source.
-
Copy the generated REST endpoint, for example: https://<qradar-ip>:12435.
Step 2: Configure a Webhook in the Delinea Platform
-
In the Delinea Platform, navigate to Settings > General settings > Webhooks.
-
Click Create Webhook.
-
On the Create Webhook page, complete the following fields:
-
Name: Forward to IBM QRadar SIEM
-
Target: Paste the webhook URL copied from IBM QRadar SIEM
-
Description: Optional (for example, “Forwards audit events to IBM QRadar SIEM”)
-
Webhook State: Enabled
-
-
Under Triggers, select the service(s) and event levels (Info, Warning, Error) to forward.
-
(Optional) If authentication is required, add a custom header:
-
Key: Authorization
-
Value: Bearer
-
-
Click Save to complete the configuration.
Step 3: Validate Event Data
-
In the Delinea Platform, go to Settings > General settings > Webhooks.
-
Select the QRadar webhook.
-
Click View Webhook Logs.
-
Select a log entry and click View Payload.
Example Delinea Webhook Payload
{
"event_type": "SecretAccessed",
"service": "Secret Management",
"level": "info",
"details": {
"user": "frank",
"secret_id": "A1B2C3",
"timestamp": "2025-09-16T16:55:00Z"
}
}
This payload is sent to QRadar via the HTTP Receiver and parsed using a Universal DSM with a Log Source Extension (LSX).
Step 4: Create and Configure a Log Source Extension (LSX)
Create the Log Source Extension
-
In QRadar, navigate to Admin > Log Source Extensions > Create.
-
Select Universal DSM.
-
Choose JSON as the file type.
-
Upload a sample Delinea webhook JSON payload.
-
Save the LSX.
Map JSON Fields to QRadar Properties
Example field mapping:
| Delinea JSON Field | QRadar Field |
|---|---|
| eventType | Event Name |
| user | Username |
| secretId | Object |
| timestamp | Start Time |
Assign the LSX to the Log Source
-
Navigate to Admin >Log Sources.
-
Edit the HTTP Receiver log source.
-
Assign the LSX.
-
Deploy the changes.
Verification
To verify that the integration works:
-
In the Delinea Platform, click Verify Webhook or trigger an event.
-
In QRadar, navigate to Log Activity > Search.
-
Search by Event Name or Username.
-
Confirm that:
-
Events are received in QRadar.
-
JSON fields are parsed correctly.
-
Fields are searchable.
-
Troubleshooting
The following table provides troubleshooting guidance for common issues you may encounter when integrating the Delinea Platform with IBM Qradar SIEM.
|
Issue |
Cause |
Solution |
|---|---|---|
|
Events not arriving |
Firewall or port issue, incorrect webhook URL |
Check firewall settings, verify QRadar HTTP Receiver port, confirm webhook URL |
|
JSON not parsed |
LSX not assigned or deployed, mismatched JSON structure |
Ensure LSX is assigned and deployed, validate JSON matches LSX sample |
|
TLS / certificate issues |
Untrusted or missing certificate |
Import a trusted certificate into QRadar, use HTTPS if required |
|
Event duplication |
Coalescing enabled |
Disable coalescing for the HTTP Receiver log source |