Notifications, ITSM and SIEM

Send alerts to email, Teams, Slack and signed webhooks, raise tickets in Jira and ServiceNow, and forward events to Splunk and Sentinel.

Updated 29 October 2026

Online version, always current: https://cloudvision360.com/docs/platform/notifications-itsm-siem/

Route what the platform finds to the places your team already works.

Notification channels

In CloudVision360, open Admin → Notifications & ITSM (Channels, Delivery log, and ITSM & SIEM) and add one or more channels:

  • Email (SMTP) — digests and individual alerts.
  • Microsoft Teams and Slack — post to a channel via an incoming webhook.
  • Signed webhooks — HTTP POST to your own endpoint, signed with HMAC-SHA256 so you can verify the payload came from CloudVision360.

Choose which events each channel receives (new high-risk findings, budget warnings, remediation results, scan completion) and the severity threshold.

ITSM: Jira and ServiceNow

Connect Jira or ServiceNow to turn findings into tickets. CloudVision360 creates the ticket, links it to the finding, and reads it back when it is closed so the finding and the ticket stay in step. Configure the project, issue type and field mapping in Settings → Integrations → ITSM.

SIEM forwarding

Forward findings and audit events to your SIEM:

  • Splunk via the HTTP Event Collector (supply the HEC URL and token).
  • Microsoft Sentinel via log forwarding.

Customer-supplied URLs are guarded

Webhook, ITSM and SIEM URLs are called through an SSRF-guarded client, so a misconfigured or malicious URL cannot be used to reach internal addresses. Private network ranges are blocked unless an administrator explicitly allows them.