Overview

Send Calico Enterprise and Calico Cloud security events to Callgoose SQIBS. A webhook with generic JSON output posts each security event to your SQIBS API endpoint. SQIBS opens an incident for each event.

You need
Calico Enterprise or Calico Cloud with access to the web console, and a SQIBS API token
Setup time
About 10 minutes
Result
Calico security events open SQIBS incidents

How it works

Tigera Calico
Alert fires
Calico raises a security event, for example a suspicious flow.
Tigera Calico
Sends a webhook
Through a generic JSON webhook.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Each event opens an incident.

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 Tigera Calico template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (none) No key, so every security event opens an incident.
  1. Choose the Priority for these incidents and click Save.

Send one test event, then use the JSON key creator to set Incident title from to the event's description key and, if you want, a trigger key for the severities you page on. Calico does not send a resolve for security events; close the incident when it is handled.

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 Calico

  1. In the Calico web console, select Activity > Webhooks and click Create your first webhook (or Create Webhook).
  2. Enter a name, choose the Event types to send, and under Type choose Generic JSON.
  3. Enter your SQIBS endpoint as the URL and click Create Webhook:
https://<your-endpoint>/sqibs-api/v1/process?from=calico&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.

  1. Generate a test security event, or wait for one.
  2. In SQIBS, a new incident opens. Use its payload (from the API log) to set the title and description keys.

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 Calico 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 Calico reports a pod talking to a known malicious address, SQIBS can run a workflow that applies a quarantine network policy to that pod.

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: