Overview

Send Falco runtime security alerts to Callgoose SQIBS. Falcosidekick forwards each Falco event to your SQIBS API endpoint with its webhook output. SQIBS opens an incident for events at the priorities you choose, titled with the rule that fired.

You need
Falco with Falcosidekick (Kubernetes or Linux), and a SQIBS API token
Setup time
About 15 minutes
Result
Falco alerts open SQIBS incidents

How it works

Falco
Alert fires
A rule detects suspicious activity.
Falco
Sends a webhook
Falcosidekick posts the event 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 rule.

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 Falco template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "priority" Critical Opens an incident for critical events.
Trigger "priority" Error A second filter for errors (optional). Add more for Warning, Alert or Emergency.
Title from "rule" Becomes the incident title.
Description from "output" Falco's full message becomes the description.
  1. Choose the Priority for these incidents and click Save.

Falco events have no resolved state, so close the incident in SQIBS after you investigate. To keep noise down, set Falcosidekick's minimum priority as well.

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: Send Falco events to SQIBS with Falcosidekick

  1. Store the token where Falcosidekick can read it, as a header value:
Bearer <your-token>

Put that line in /etc/falcosidekick/secrets/webhook/authorization (or mount it from a Kubernetes secret). 2. Add the webhook output to the Falcosidekick configuration:

outputs:
  webhook:
    host: https://<your-endpoint>
    endpoint: /sqibs-api/v1/process
    headers:
      Authorization:
        files:
          - /etc/falcosidekick/secrets/webhook/authorization

Replace <your-endpoint> with your SQIBS endpoint host. See how to get the endpoint URL. 3. Restart Falcosidekick so it loads the output. If you install with the Falco Helm chart, set the same values under falcosidekick.config.

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 test rule, for example by opening a shell in a container (kubectl exec -it <pod> -- sh).
  2. In SQIBS, a new incident opens. The Falco event looks like this (shortened):
{
  "output": "Notice A shell was spawned in a container with an attached terminal (user=root container=payment-api-7d9 shell=sh)",
  "priority": "Notice",
  "rule": "Terminal shell in container",
  "time": "2026-11-22T10:15:00.000000000Z",
  "source": "syscall",
  "hostname": "node-2",
  "output_fields": {
    "container.name": "payment-api-7d9",
    "k8s.ns.name": "default",
    "user.name": "root"
  },
  "tags": [
    "container",
    "shell",
    "mitre_execution"
  ]
}
  1. This example is priority Notice; with the filters above only Critical and Error events open incidents. Add a filter for Notice while you test.

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 Falcosidekick configuration.

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 Falco reports a shell spawned in a production container, SQIBS can run a workflow that isolates the pod with a network policy and captures its details 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: