Configure real-time alerting and notifications for your perimeter
GitGuardian's real-time monitoring allows alerts to be sent immediately when an incident is detected or updated.
Configuring a notifier from your GitGuardian workspace allows you to push incident alerts to the channel of your choice (e.g Slack, PagerDuty...). These alerts will contain details about the incident such as the triggered detector and location (org and repository) without revealing the secrets detected or any other sensitive data, avoiding any further contribution to sprawling of secrets.
Incident types and integration scope
All GitGuardian's alerting integrations are designed to handle internal secret incidents detected within your integrated sources. This includes all the notification channels and issue tracking integrations listed below.
Custom webhooks are the exception: if your workspace and team have access to Public Monitoring, custom webhooks can also be configured to receive events related to public secret incidents detected on public repositories.
Available integrations
By default, GitGuardian will notify dashboard users via email for every incident. You can read more about email alerting here. You can also choose to integrate with other notification channels, GitGuardian currently supports:
-
Custom webhooks
Custom services can be written to listen in on GitGuardian's detection engine and programmatically treat detected incidents. Can handle internal and/or public secret incidents (if your team has access to Public Monitoring). -
PagerDuty
Send incidents as PagerDuty event notifications with the PagerDuty Integration. -
Splunk
Treat incidents as data with the Splunk Integration. -
Slack
The Slack integration allows you to be notified on your team's workspace in a channel of your choice. -
Discord
The Discord integration allows you to be notified on your team's discord server of your choice. -
Microsoft Teams
The Microsoft Teams integration allows you to be notified on your team's workspace in a channel of your choice.
