Send security alerts to Slack, Teams or a SIEM
Have each new security alert posted to a chat channel or your security tools as signed JSON.
Besides the console and the emails to security admins, Adimone can post each new security alert to an address you choose: a Slack or Microsoft Teams incoming webhook, or the HTTP collector of your SIEM.
Set it up
- Create the receiving address: in Slack, an incoming webhook for the channel; in Teams, a workflow that accepts webhook requests; in a SIEM, an HTTP event collector.
- In the admin console, open Integrations and choose Set up on Security alert webhook.
- Paste the address. It is kept secret, since such addresses carry their own key.
- Pick the Lowest severity to send. Medium is the default; choose High to send only what needs someone now.
- Tick Switch it on after saving, write the reason and save. A test message is sent first; the webhook is switched on only if the receiver accepts it.
- Copy the Signing secret shown once, if your receiver checks signatures.
With two superadmins, the setup waits for the other one's approval; it is switched on when they approve. The signing secret made then is shown to nobody, so choose Make a new one next to it afterwards to get one to copy.
What is sent
Each alert is one POST with a JSON body. text is a one-line summary that Slack and Teams show as the message; alert has the details for tools: its id, rule and title, severity, the account id, address or business it is about, what the rule recorded, when it started and last fired, and a link to the alert in the console. Accounts are named by id only, never by name or email address, since the channel may be shared.
The Genesis-Event header says what the request is: alert.raised for an alert, test for the test message.
Check the signature
Each request carries a Genesis-Signature header of the form t=<unix seconds>,v1=<signature>, where the signature is the hex HMAC-SHA256, keyed with the signing secret, of the timestamp, a full stop and the raw body. A receiver that checks it should also refuse requests whose timestamp is more than five minutes old. The card shows the header's format to copy.
When the receiver is down
Deliveries are background jobs: a receiver that fails is tried again with growing pauses, and a delivery that keeps failing shows under Jobs as a failed admin.alert_webhook job, which an operator can run again. Alerts still show in the console and go out by email in the meantime.
To stop sending, choose Switch off on the card; it applies at once. If the address or the secret leaked, change the address or choose Make a new one next to the signing secret.