Overview
Send Trellix Database Security (formerly McAfee Database Security) alerts to Callgoose SQIBS. Trellix alerts usually leave through Trellix ePO or a SIEM rather than a webhook of their own, so the simplest path is to forward the alert from the tool that collects it (ePO automatic response, your SIEM, or a syslog collector) as JSON to your SQIBS API endpoint. SQIBS opens an incident for each alert.
How it works
Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- Add a filter with these values (there is no built-in Trellix Database Security template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | (none) | Opens an incident for every forwarded alert while you capture the payload. |
- Choose the Priority for these incidents and click Save.
Your forwarder 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 and set the title to the rule or alert name.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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: Forward alerts to SQIBS
Use whichever of these you already run:
- SIEM: most SIEMs can call a webhook from a correlation rule or playbook. Create a rule for Trellix Database Security events and send the event as JSON to your SQIBS endpoint.
- Syslog collector: if Trellix sends syslog to a collector such as rsyslog or Fluent Bit, add an HTTP output that posts the matching events as JSON.
- Trellix ePO: use an automatic response that runs a registered executable or script which posts the event with
curl.
In each case, the URL is your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=trellixdb&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.
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.
- Trigger a low-risk rule on a test database, for example a denied login.
- 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 forwarding rule.
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 a privileged account runs an unexpected query, SQIBS can run a workflow that suspends the account and notifies the security team.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.