CyberTwin
Notifications

Slack + Microsoft Teams.

Native delivery, no relay: add a Slack or Teams endpoint in webhook settings, paste your channel's incoming-webhook URL, and every qualifying event — including “a previously-proven control reopened” — arrives as a formatted channel message with a link back into CyberTwin. Setup takes ~2 minutes per channel.

Slack — native, two steps

  1. In Slack, install the Incoming Webhooks app and create a webhook for the target channel. Copy the hooks.slack.com URL.
  2. In /settings/webhooks, add an endpoint with kind Slack channel, paste the URL, and pick your severity floor. Done — no relay, no JSON mapping.

Events arrive as a formatted Block Kit message: headline (e.g. “🚨 A previously-proven control reopened”), the finding title and description, severity + labels (your PROVEN/MODELED provenance travels with it), and an Open in CyberTwin button.

Microsoft Teams — native, two steps

  1. In Teams, add an Incoming Webhook (or a Workflows “post to channel when a webhook request is received” flow) on the target channel. Copy the URL.
  2. In /settings/webhooks, add an endpoint with kind Microsoft Teams, paste the URL, and pick your severity floor.

Events arrive as a MessageCard — severity-colored, title + description, the same labels, and an Open in CyberTwin action.

What about interactive apps?

Fully interactive Slack + Teams apps (mark in-progress, mark remediated, request re-verify from the message itself) land alongside the bidirectional Jira/ServiceNow integration. Native channel delivery above works today.

Need a different channel?

The webhook payload format is fully documented at /docs/api. Anything that accepts an HTTP POST + can verify HMAC works.

SlackTeamsPagerDutyOpsgenieDiscordGeneric SIEM