Overview

Send Imperva database security alerts to Callgoose SQIBS. Point an Imperva alert action that posts JSON (webhook or HTTP) 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
Imperva Data Security Fabric (DSF) or Database Activity Monitoring with permission to manage alert actions, and a SQIBS API token
Setup time
About 15 minutes
Result
Imperva alerts open SQIBS incidents

How it works

Imperva
Alert fires
A security policy raises an alert.
Imperva
Sends a webhook
An alert action posts JSON to SQIBS.
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 Imperva 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.

Imperva 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 filter on the severity field (one filter per severity you page on) and set the title to the alert or policy name.

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 alert action in Imperva

  1. In Imperva, open the alert or playbook settings for the policy you want in SQIBS and add an action that sends a webhook (HTTP POST with a JSON body).
  2. Set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=imperva&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 you can shape the body, include at least the alert name, severity, a unique alert ID and the database or server, in plain JSON keys.
  2. Save the action, attach it to the policy, and send a test.

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. Trigger a low-risk policy rule on a test database, or use the action's test option.
  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 Imperva action.

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 Imperva reports a SQL injection attempt against a database, SQIBS can run a workflow that blocks the source address at the firewall and notifies 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: