Notifications, Slack, Teams and webhooks
A policy event nobody sees is one nobody fixes. Dwaar tells people where they already look: the bell in the console, their inbox, a Slack or Teams channel, or a system of yours that takes a webhook. Nothing goes to a channel until someone connects it and adds a rule.
What Dwaar tells you about
| Group | Events |
|---|---|
| Policies | A policy event opened or reopened, a policy event resolved, a fix SLA due soon or breached, a policy ready to enforce |
| Exceptions | Requested, approved or rejected, ending soon or ended |
| Findings | New critical findings on a scanned version, one message per scan and resource |
| Operations | A scan failed, a discovery failed, a notification connection went into error |
| Vendors | A vendor submitted its security assessment |
You only ever hear about what you can see. An event belongs to the organization of what it is about, and Dwaar applies your access when it builds your feed and your email.
In the console and by email
The bell shows your feed. In Settings, then Notifications, each event has two switches: in the feed, and by email.
Email is sent with care for your inbox: critical events arrive at once, and everything else is gathered into one digest a day. Without an email setup on your Dwaar deployment, the feed and your channels still work.
Send events to a channel
Channels are integrations. Connect one under Integrations, in the ticketing and chat category, then add routing rules on its Routing tab.
Each connection's form has its setup guide beside it, and saving needs a passing Test connection, which posts a sample message.
Slack
Use an incoming webhook. In Slack, create an app with Incoming Webhooks turned on and add a webhook to the channel you want. Paste its URL into Webhook URL.
One connection posts to one channel. To use two channels, add two connections. Dwaar only accepts https://hooks.slack.com/services/... URLs.
Microsoft Teams
Use a Teams workflow that posts to a channel when a webhook request is received, and paste its HTTP URL into the connect form. Dwaar posts an Adaptive Card.
Office 365 connector URLs (*.webhook.office.com) and older Logic Apps URLs (*.logic.azure.com) are refused: Microsoft retired those connectors, and the form says what to use instead.
Generic webhook
Give an Endpoint URL (https, port 443, no query string) and a Signing secret of at least 32 characters, or a whsec_ secret. Put no token in the URL: every request is signed, and people who can read the connection see its URL. Dwaar sends one POST per event, with a JSON body:
{
"type": "policy_violation",
"id": "the event id",
"occurredAt": "2026-11-12T09:00:00Z",
"orgId": "the organization id",
"version": 1,
"data": {
"title": "…",
"body": "…",
"url": "a link into the console",
"severity": "high",
"attributes": {}
}
}
Fields are only ever added, so ignore the ones you do not know. A connection test sends "type": "test".
Every request is signed the Standard Webhooks way, so most Standard Webhooks libraries verify it as is. The headers are webhook-id (the event id, the same on every retry, so use it to drop duplicates), webhook-timestamp (Unix seconds) and webhook-signature. To verify one by hand:
import base64, hashlib, hmac
def signature(secret: str, webhook_id: str, timestamp: str, body: bytes) -> str:
# A whsec_ secret's key is the base64 after the prefix; any other secret is used as it is.
key = base64.b64decode(secret[6:]) if secret.startswith("whsec_") else secret.encode()
mac = hmac.new(key, f"{webhook_id}.{timestamp}.".encode() + body, hashlib.sha256)
return "v1," + base64.b64encode(mac.digest()).decode()
# Compare with the webhook-signature header in constant time, and refuse old timestamps.
Dwaar follows no redirects. Answer with any 2xx to accept an event.
Routing rules
A rule sends one kind of event to one connection. On the connection's Routing tab, choose New routing rule, then pick the event and, if you want to narrow it, Organizations, Products and a Minimum severity. Leave them empty for everything the connection's organization can see.
- Every enabled rule that matches delivers, but one connection gets an event once.
- Slack and Teams messages wait two minutes and group up to ten events of a rule into one message, so a busy scan does not flood the channel.
- A policy event takes three lines: Policy event and the policy's name, then For control with the control, then On resource with the resource, such as
acme/payments-api. - Webhook events are sent one by one, at once.
- Send test message on the Routing tab posts a sample through the connection now.
When delivery fails
Dwaar retries a refused or failed delivery for about a day, waiting longer each time and respecting the receiver's Retry-After. A redirect, a not-found or another permanent refusal is not retried.
After five deliveries in a row fail for good, the connection shows as in error, and the people who follow connections are told. The connection's Activity tab lists each delivery, retry and failure with the reason. The next successful delivery clears the error.
Messages carry names, counts and a link. They never carry secrets, code or a finding's evidence, and the webhook URL itself is stored sealed like any other credential.
Try this next
Connect a Slack channel your team already reads, add one rule for Policy event with a minimum severity of high, and press Send test message. Then move one policy from observe to audit and watch the channel.