Skip to main content
Elastic Security is the SIEM capability built into the Elastic Stack. Calseta receives Elastic alerts via webhook actions and normalizes them for agent consumption.

Ingestion Endpoint

Setting Up the Webhook

Detection Rule Webhook Action

  1. In Kibana, go to SecurityRules
  2. Edit the detection rule you want to forward
  3. Under Actions, add a Webhook action
  4. Configure:
    • URL: https://your-calseta-host/v1/ingest/elastic
    • Method: POST
    • Headers: Authorization: Bearer cai_your_api_key
    • Body: Use the default alert JSON template

Connector Setup

If you haven’t created a webhook connector:
  1. Go to Stack ManagementConnectors
  2. Create a Webhook connector
  3. Set the URL and authentication headers
  4. Reference this connector in your detection rule actions

Payload Format

Calseta expects the standard Elastic Security alert format. Key field mappings:

Severity Mapping

Indicator Extraction

The Elastic plugin extracts indicators from:
  • source.ip, destination.ip — network indicators
  • user.name, user.email — account indicators
  • file.hash.md5, file.hash.sha1, file.hash.sha256 — file hash indicators
  • url.full, url.domain — URL and domain indicators
  • Custom field mappings against raw_payload

Webhook Signature Verification

Set ELASTIC_WEBHOOK_SECRET in your .env file. Configure the same secret in the Elastic webhook connector’s authentication settings.

Example Payload

Elastic Security has evolved its alert schema across versions. Calseta handles both the legacy signal.* format and the newer kibana.alert.* format.

API Reference

See Ingest Alert for the full endpoint documentation.