Security

Send GCP Security Command Center alerts to on-call with CallHeim.

GCP Security Command Center findings, forwarded by a small relay you build that unwraps the Pub/Sub push envelope. 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.

securitycommandcenterGoogle Cloudsource names also accepted: gcp-scc, scc, security-command-center

Needs a forwarder

GCP Security Command Center 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

Export findings to a Pub/Sub topic, then have a small relay (for example a Cloud Function) decode the Pub/Sub push envelope and POST the unwrapped finding JSON to your CallHeim URL.

Create an Integration in CallHeim and choose GCP Security Command Center 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.

GCP Security Command Center 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 GCP Security Command Center’s webhook format.

GCP Security Command Center documentation →

Setup snippetsecuritycommandcenter
# SCC → Notifications → export findings to a Pub/Sub topic.
# A real Pub/Sub push wraps the finding as base64 in message.data — CallHeim reads an
# unwrapped {finding:{...}} body, so point the push subscription at a small relay
# (for example a Cloud Function) that decodes the message and POSTs the result to {{WEBHOOK_URL}}.
Check GCP Security Command Center’s current documentation for the exact fields.

After it arrives

What CallHeim does with GCP Security Command Center 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 GCP Security Command Center’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 →

If GCP Security Command Center sends a recovery notification, CallHeim records it against the incident.

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 GCP Security Command Center at CallHeim and see what it does with your alerts.

Start on the free trial, connect GCP Security Command Center and send a test alert to see the incident it opens.