Overview

Send IBM Guardium database security alerts to Callgoose SQIBS. IBM Guardium Data Security Center can send alerts to a webhook; point it at your SQIBS API endpoint and SQIBS opens an incident for each alert, so your security team is paged and an approved response workflow can start.

You need
IBM Guardium Data Security Center with permission to configure alert integrations, and a SQIBS API token
Setup time
About 15 minutes
Result
Guardium alerts open SQIBS incidents

How it works

IBM Guardium
Alert fires
A policy or anomaly alert fires.
IBM Guardium
Sends a webhook
Through a webhook integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the alert.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in IBM Guardium template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (none) Opens an incident for every alert while you capture the payload.
  1. Choose the Priority for these incidents and click Save.

IBM Guardium does not publish a fixed payload for this, so build the filter from the first real message: send a test, open it in the API log, and copy the keys with the JSON key creator. Then replace the catch-all with a key that only alerts carry (for example the severity field with Critical), and set Incident title from to the alert name field. Guardium alerts are events, not states, so close the incident in SQIBS when the investigation is done.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Add the webhook in IBM Guardium

  1. In Guardium Data Security Center, open the integrations settings and add a webhook integration for alerts.
  2. Set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=guardium&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. If the integration asks for authentication, choose none (the token is in the URL), or add the header Authorization: Bearer <your-token> and drop &token= from the URL.
  2. Choose the alert policies or severities to send, save, and send a test alert.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Send a test alert from the integration, or trigger a low-risk policy rule.
  2. In SQIBS, a new incident opens. Copy its keys into the filter with the JSON key creator.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Guardium webhook.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when Guardium reports repeated failed logins on a database account, SQIBS can run a workflow that locks the account and collects the source addresses for the security team.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: