Webhooks: alerts straight into Teams, Slack or your SIEM
Instead of reading e-mails, new findings and changes appear where your team already works – in the channel, the ticketing system or the SIEM.
- New finding
- Signed message
- Teams, Slack, SIEM
- Team reacts
Events and content
| Event | Trigger | Fields (JSON format) |
|---|---|---|
findings.new | new or reopened findings from the chosen severity (critical, high, medium); accepted risks excluded | domain, findings[] with id, severity, category, check, title, asset, url |
dns.changed | change to NS, MX, SPF, DMARC, CAA or addresses of an own domain | domain, changes[] with kind, field, from, to |
subdomain.new | newly found subdomain | domain, subdomains[] with name, source |
watch.changed | change to a watched domain | changes[] with domain, kind, from, to |
test | “Send test” button | envelope only |
Each JSON message also contains v (version 1), event, webhook (ID), sent_at (UTC, ISO 8601) and summary. Headers: X-EAM-Event, X-EAM-Timestamp, X-EAM-Signature, User-Agent: eam.ch-webhook/1. Teams receives an Adaptive Card (version 1.4), Slack a text with links (text).
Signature
X-EAM-Signature = "sha256=" + HMAC-SHA256(secret, X-EAM-Timestamp + "." + body). Verify with a constant-time comparison and reject messages older than 5 minutes (replay protection). Compute over the unmodified body as received. The secret is shown once on creation and stored encrypted at eam.ch.
Delivery
- Queue processed by the regular background run; 10-second timeout, success on HTTP 2xx.
- Retries after 5, 15, 60 and 240 minutes (at most 5 attempts); after 10 consecutive failures the webhook is switched off and the main users are informed by e-mail.
- The same message may arrive more than once (at-least-once delivery): detect duplicates by
webhookandsent_ator by content.
Abuse protection (SSRF)
Only https on port 443; the name must resolve publicly – private, local and reserved addresses (RFC 1918, loopback, link-local, carrier-grade NAT 100.64/10); a host name is required instead of an IP address are blocked. The connection is pinned to the checked address (no second lookup, protection against DNS rebinding), redirects are not followed and the response is limited to 64 KB.
Reference: Swiss ICT minimum standard DE.CM and RS.CO, ISO/IEC 27001:2022 A 5.24–5.26 (information security incident management), NIS2 Art. 21(2)(b).
In short
- Webhooks report new findings and changes immediately to Teams, Slack or your own systems.
- The messages contain no personal data; JSON messages are signed.
- Keep a webhook address secret like a password.
- Set up under Account → Webhooks, then “Send test”.
Check it yourself
Commands to verify on Linux or macOS. Replace ihre-domain.ch with your domain and only check your own systems.
printf '%s.%s' "$TS" "$BODY" | openssl dgst -sha256 -hmac "$GEHEIMNIS"