CBOM Documentation

CBOM Secure

  • Product Overview
    • Overview
    • Dashboard Interface
    • Dashboard Operations
    • Data Visualization
    • Overview
    • Host
    • Template
      • Networked Deployments
      • Cloud Deployments
      • Off-Grid Deployments
    • Discovery History
      • Tags
      • Tag Scope
      • Integrations
      • Cloud Servers
      • CycloneDX Export
    • Sensors Reference
    • Overview
    • Summary Report
    • PQC Report
    • AI Services
    • Source Code Visualizer
    • Key
    • Certificate
    • CipherSuites
    • Analysis
    • Policy Management
    • User Policy
    • Standard Policy
    • Overview
    • Cases
    • Criteria
    • Notification Format
    • Rules
      • Connections
      • Health
    • User Management
    • Roles & Permissions
    • Audit Trail
    • System Logs
    • Top Bar and User Menu
    • System Configuration
  • Login and Authentication
    • Introduction
      • Components
      • Data Flows
      • Execution Models
      • Incremental Scanning
      • Security Model
      • Topologies
      • Sizing Guide
      • HA and Scaling
      • Ports and Firewall
      • Prerequisites
      • Docker Compose
      • Native on Linux
      • Deployment Server
      • Install Troubleshooting
      • Validation Checklist
      • Managing Services
      • Logging
      • Certificates
      • Configuration
      • Backup and Recovery
      • Ops Troubleshooting
      • Methods
      • SAML 2.0 SSO
      • OIDC and Entra ID
      • Token Authentication
      • Password Policy
      • Sensor vs Connector
      • Sensor Guide Structure
      • Capability Matrix
      • GitHub Sensor
        • AWS
        • Azure
        • Google Cloud
        • Active Directory
        • LDAP Directories
        • AD CS
        • Thales Luna HSM
        • Entrust nShield HSM
        • HashiCorp Vault KMIP
        • Windows Cert Store
        • Linux Trust Store
        • MSSQL TDE
      • Roadmap
      • Integration Model
      • CrowdStrike
      • ServiceNow
      • ServiceNow and Jira Setup
      • Notification Engine
  • Administrative Guide
    • Glossary
    • Configuration Reference
    • Data Model Reference
    • API Reference
    • API Authentication
    • CycloneDX Export Specification
    • Risk and PQC Scoring
    • Built-in Standards
    • Widget Catalogue
    • AI Services Data Handling

Notifications

Notifications turns the cryptographic inventory into work someone owns. A rule watches for a condition — a weak algorithm in use, a key that fails a policy, a certificate close to expiry. When the condition is met, the engine opens a case and delivers it to the channels the rule names: the CBOM Secure in-app inbox, email, ServiceNow or Jira. The finding then has an owner and a state instead of a position on a dashboard.

The section is reached from Notifications in the left navigation menu. Opening the group lands on Cases.

The Pages in This Section

  • Cases: What the engine has raised, and the evidence behind each case. This is where findings are acknowledged, snoozed, waived or closed. See Cases.

  • Criteria: Reusable conditions over material fields, and the scopes composed from them. A rule refers to these instead of repeating its own conditions. See Criteria.

  • Notification Format: How a case reads when it is sent — which sections appear, in which order, and the wording of each. See Notification Format.

  • Rules: What the engine watches for, how often, and where it sends what it finds. See Rules.

  • Settings: The Connections a rule's channels deliver through, and the engine's Health.

Setting Up Notifications

The pages depend on one another, so set them up in this order:

  1. Connections — configure the server or credential for each external channel you will use. The in-app channel needs none.

  2. Criteria — define the conditions worth alerting on, or use the shipped ones.

  3. Notification Format — keep the shipped formats or adapt one to your house style.

  4. Rules — combine a match, a schedule and outputs, preview the effect, then enable the rule.

  5. Cases — work the queue as cases arrive.

For how the engine behaves at scale — idempotency, storm control and the scheduler — see Notification Engine in the CBOM Guide. For setting up the ServiceNow and Jira side of a connection, see ServiceNow and Jira Setup.

Each page is permission-controlled. A page you do not see in the menu has not been granted to your role; ask an administrator to review it on Roles & Permissions.

On this Page:
Support Privacy Policy Terms of Service

Copyright 2026 Encryption Consulting LLC. All rights reserved.