For security operations

Route security alerts to the right analyst with rules your team can read.

Security is the largest source category in the catalog. CallHeim routes and escalates detections with rules you can read.

The sources

25 security sources — the largest category here.

Each alert source has a payload mapping for that tool’s webhook format and its own setup guide.

All 25 security sources →

Data stays inside

Where detection data goes.

No incident data is sent to an external language model, and CallHeim does not train any model on your incidents. Severity suggestions and related-incident insights are rule-based code running inside CallHeim’s own AWS environment.

See how suggestions work →See where your data goes →

Triage

A severity suggestion you can put in a runbook

Detection engineering already lives on rules you can read. CallHeim’s suggestions are keyword rules with the matched terms shown, so you can write them into a runbook.

How the incident record works →

What a suggestion looks like

CallHeim suggests a severity from a fixed keyword ruleset plus your own resolved incidents, shows the matched terms, and a person applies it. Suggestions never change severity or page anyone.

The incident itself carries the severity your source sent, mapped to P1 through P5.

Noise

Repeats join the open incident instead of paging again.

A scanner that reports the same finding once an hour attaches to the incident that is still open instead of paging again: at any age when the tool sends its own finding id, within 24 hours when only the title identifies it. Resolve the incident and the next report opens a new one.

  • A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident.
  • A series that changes state 4 times in 600 seconds attaches to its open incident instead of paging again.
  • Near-identical titles from the same source and service group at a similarity of 0.6. Title grouping can be switched off for your organization.

See the full noise reduction rules →

Controls

For the team that will review this.

  • Reads and writes are scoped by the API authorization rule to the caller’s organization, or to the caller’s own user for personal records, and custom operations enforce the organization in server-side code. CallHeim is multi-tenant on a shared database.
  • E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication.
  • The audit log is append-only: no client can modify or delete an entry.
  • Audit records are copied daily to an S3 Object Lock archive (governance mode) with a 7-year retention lock, held by CallHeim. An audit-log export downloads straight to your device, and CallHeim keeps no copy of it.

Read the full security page →

CallHeim

Put a rule you can read between your alerts and your on-call.

Start a 14-day trial, connect one alert source and send yourself a test page.