Ingestion Endpoint
Setting Up the Webhook
Detection Rule Webhook Action
- In Kibana, go to Security → Rules
- Edit the detection rule you want to forward
- Under Actions, add a Webhook action
- 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
- URL:
Connector Setup
If you haven’t created a webhook connector:- Go to Stack Management → Connectors
- Create a Webhook connector
- Set the URL and authentication headers
- 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 indicatorsuser.name,user.email— account indicatorsfile.hash.md5,file.hash.sha1,file.hash.sha256— file hash indicatorsurl.full,url.domain— URL and domain indicators- Custom field mappings against
raw_payload
Webhook Signature Verification
SetELASTIC_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.
