Notifications
HarborGuard turns scan and policy events into notifications and routes them to the channels you configure. Every notification is dispatched through a circuit-breaker per provider so a downstream outage does not block the rest of the platform.
The model has three pieces:
- Channels — a destination (email, Slack, Microsoft Teams, PagerDuty, OpsGenie, generic webhook). Each channel has provider-specific config and a list of events it subscribes to.
- Rules and events — the catalog of 12 event types you can subscribe to, and recipes for routing them by severity and digest mode.
- Webhooks — the request shape, signature scheme, and verification snippets if you build your own receiver.
Quick start
- Open Settings -> Notifications -> Add channel.
- Pick a type and fill in the provider-specific config.
- Subscribe the channel to one or more events (e.g.
critical_cve,sla_breach). - Click Test to send a probe notification.
- Repeat per environment — most teams have a high-signal channel (PagerDuty, Slack
#oncall) for criticals and a digest channel for the long tail.
Channels do their own filtering. PagerDuty channels automatically drop anything below HIGH severity even if subscribed to all events — pages should be load-bearing, not noisy.