Skip to content

Integrations

CBOM integrates with your existing toolchain to embed cryptographic visibility into the workflows your teams already use — ticketing, alerting, CI/CD, SIEM, and supply chain security.

hidden Integration ecosystem diagram showing CBOM connected to CI/CD, SIEM, ticketing, and communication tools


IntegrationCategoryStatusDescription
JiraTicketing & Workflow🔜 Coming SoonAuto-create tickets for violations and expiring certs
ServiceNowTicketing & Workflow🔜 Coming SoonCMDB sync and incident creation
SlackCommunication🔜 Coming SoonReal-time alerts to Slack channels
Microsoft TeamsCommunication🔜 Coming SoonAlerts via Teams webhooks or Power Automate
EmailCommunication✅ AvailableBuilt-in email notifications for alerts and reports
CI/CD PipelinesCI/CD🔜 Coming SoonFail builds on crypto policy violations
Splunk / SIEMSIEM & Monitoring🔜 Coming SoonForward events to Splunk, Elastic, or Datadog
ServiceNow CMDBCMDB & Asset Management🔜 Coming SoonSync crypto assets as Configuration Items
SBOM ToolchainStandards & Compliance✅ AvailableCycloneDX BOM-Link for SBOM↔CBOM linking

Automatically create and track remediation work when CBOM detects issues.

  • Jira — Create tickets with full context: asset details, violation reason, remediation steps
  • ServiceNow — Incidents and change requests integrated with your ITSM workflow

Keep security teams informed in real time.

  • Slack — Channel notifications for cert expiry, violations, and scan results
  • Microsoft Teams — Webhook-based alerts for Microsoft 365 environments
  • Email — Built-in SMTP notifications (available now)

Shift-left crypto compliance by catching issues before they reach production.

Feed crypto events into your security operations center.

  • Splunk / SIEM — HEC, syslog, or API-based event forwarding to any SIEM

Maintain accurate crypto asset records in your enterprise CMDB.

  • ServiceNow CMDB — Sync crypto assets as CIs with relationships to servers and applications

Connect CBOM to the broader software supply chain security ecosystem.

  • SBOM Toolchain — CycloneDX v1.6 export with BOM-Link for SBOM integration

All integrations use the CBOM event system. When something happens (asset discovered, policy violated, cert expiring), CBOM emits an event. Integrations subscribe to events and route them to external systems.

┌─────────────┐ ┌──────────────┐ ┌─────────────────┐
│ CBOM Core │────▶│ Event Engine │────▶│ Integrations │
│ (Sensors, │ │ (Subscribe, │ │ (Slack, Jira, │
│ Policies) │ │ Filter) │ │ SIEM, CI/CD) │
└─────────────┘ └──────────────┘ └─────────────────┘

These events can trigger any integration:

EventDescription
cert_expiry_warningCertificate approaching expiration (30/14/7 day thresholds)
cert_expiredCertificate has expired
new_critical_assetNew asset discovered with CRITICAL quantum risk
policy_violationAsset violates an active compliance policy
risk_level_changedAsset risk classification changed
scan_failureSensor scan failed or timed out
lifecycle_state_changedAsset moved to a new lifecycle state
compromised_assetAsset marked as compromised
new_asset_discoveredAny new asset added to inventory

  • Dashboard — View integration status
  • Policies — Define rules that trigger integration events
  • API Reference — Build custom integrations via REST API