Skip to main content
Microsoft Sentinel is an Azure-native cloud SIEM. Calseta receives Sentinel alerts via webhook, normalizes them to the agent-native schema, and enriches all extracted indicators.

Ingestion Endpoint

Setting Up the Webhook

  1. In the Azure portal, create a new Logic App
  2. Add a trigger: When Azure Sentinel alert is triggered
  3. Add an action: HTTP POST
    • URL: https://your-calseta-host/v1/ingest/sentinel
    • Headers: Authorization: Bearer cai_your_api_key
    • Body: Select the full alert JSON from the trigger output
  4. Enable the Logic App

Option 2: Automation Rule

  1. In Sentinel, go to AutomationAutomation rules
  2. Create a new rule with conditions matching the alerts you want to forward
  3. Add an action: Run playbook (use a Logic App with the HTTP POST action above)

Payload Format

Calseta expects the standard Sentinel alert JSON structure. Key fields mapped during normalization:

Severity Mapping

Indicator Extraction

The Sentinel plugin extracts indicators from:
  • properties.entities — Sentinel’s parsed entities (IPs, accounts, hosts, file hashes)
  • Alert description and custom fields via system normalized-field mappings
  • Custom per-source field mappings you define against raw_payload

Webhook Signature Verification

Set SENTINEL_WEBHOOK_SECRET in your .env file to enable signature verification. Configure the same secret in your Logic App’s HTTP action.

Example Payload

Rate Limits

Sentinel Logic Apps can fire rapidly during alert storms. Calseta handles this via rate limiting — configure RATE_LIMIT_INGEST_PER_MINUTE if you need to adjust the default.

API Reference

See Ingest Alert for the full endpoint documentation.