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

Criteria

Criteria are reusable conditions over the fields of a cryptographic material — "RSA key shorter than 2048 bits", "certificate signed with SHA-1". A scope is built from criteria you already have, combined with and, or and not. Both are written once and then chosen by name in a rule, so a change to one condition reaches every rule that uses it.

Criteria and scopes share one list and one numbering, NS- followed by a number. These notification scopes are a different thing from the tag scopes used by dashboards, which select by tag rather than by material field.

The page is reached from Notifications > Criteria in the left navigation menu.

Viewing Criteria and Scopes

CBOM Secure Notifications — Criteria

The pills above the table show All, only Criteria, or only Scopes.

  • Type: Criteria or Scope.

  • Name: The name rules and other scopes refer to, with its identifier beneath.

  • What it selects: For a criterion, the kind of material it applies to. For a scope, how many others it names.

  • Used by: How many rules (or, for a scope, other scopes) refer to it.

  • Enabled: Whether it can be used.

  • Actions: Edit and Delete.

Creating Criteria or a Scope

Click New criteria. One editor creates either kind, depending on which section you fill in:

CBOM Secure Notifications — New criteria
  • Name: Required and unique. Scopes quote it by name, so choose one that reads well in an expression.

  • Description: Optional.

  • 1 — Fields on the material: Choose a Doc type, then Add condition for each test. Join conditions with $and, $or and $not, and group them with parentheses. Filling in only this section saves a Criteria.

  • 2 — Combine conditions you already have: Use Add scope to pick existing criteria or scopes, choose Match any of these or Match all of these, and set each one to Include or Exclude. Anything here saves a Scope.

  • Enabled: Whether rules may use it.

Conditions compare a field with a value using:

  • Equality: is, is not, is any of, is none of.

  • Size: is less than, is at most, is more than, is at least.

  • Lists: contains all of, has exactly N entries.

  • Other: is present, matches a pattern.

Edit as JSON shows the condition as a filter document, for anyone more comfortable writing it directly. Edit as text… does the same for a scope's expression. Save, and the editor reports how many materials the item selects today. A scope that names no conditions matches every material, and the editor warns you about it.

Editing and Deleting

Renaming a criterion updates the scopes that refer to it. An item that a rule or another scope still uses cannot be deleted. The Still in use message lists what uses it, so you can remove those references first.

Viewing this page needs the notification criteria permission; creating, editing and deleting needs the manage permission, held by administrators and managers.

On this Page:
Support Privacy Policy Terms of Service

Copyright 2026 Encryption Consulting LLC. All rights reserved.