Security

Send Trivy alerts to on-call with CallHeim.

Vulnerability scan reports from the Trivy CLI, sent to a webhook. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

trivyAqua Securitysource names also accepted: aqua-trivy, trivy-operator

Needs a forwarder

Trivy does not post to CallHeim on its own for this. You set up a forwarder, rule or script that sends the event to your CallHeim URL; the setup steps show what to send.

Setting it up

Run the Trivy CLI with JSON output in your pipeline and POST the report to your CallHeim integration URL. The snippet is for that CLI report. Trivy Operator’s webhook broadcast sends its Kubernetes report objects, a different shape that this mapping does not read.

Create an Integration in CallHeim and choose Trivy from the Catalog to get its ingest URL, and use that URL as the target of your forwarder. CallHeim’s ingest URL takes a JSON request body. The snippet beside this shows the request it expects, with {{WEBHOOK_URL}} replaced by your real URL.

Trivy cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.

CallHeim includes a payload mapping for Trivy’s webhook format.

Trivy documentation →

Setup snippettrivy
# CI step: scan with the Trivy CLI, then POST the JSON report
trivy image --format json --output report.json <image>
curl -X POST "{{WEBHOOK_URL}}" \
  -H 'content-type: application/json' \
  --data @report.json
# Body includes {ArtifactName, Results:[{Vulnerabilities:[{Severity}]}]}.
# CallHeim accepts bodies up to 256 KiB: add --severity HIGH,CRITICAL to keep the report small.
Check Trivy’s current documentation for the exact fields.

After it arrives

What CallHeim does with Trivy alerts.

A repeat of the same finding attaches to the incident already open for it, and an Orchestration Rule can route findings by severity, title or any payload field to the team that owns them.

CallHeim maps Trivy’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point Trivy at CallHeim and see what it does with your alerts.

Start on the free trial, connect Trivy and send a test alert to see the incident it opens.