Alerts & Schedules
Alerts & Schedules
Section titled “Alerts & Schedules”The Alerts page manages alert rules that trigger on cryptographic risk events, and scan schedules that automate sensor execution.

Alert Rules
Section titled “Alert Rules”Alert rules define conditions that trigger notifications when new assets are discovered or existing assets change state.
Creating an Alert Rule
Section titled “Creating an Alert Rule”- Navigate to Alerts → Create Rule
- Define the trigger condition
- Set notification method
- Activate the rule
Trigger Conditions
Section titled “Trigger Conditions”| Condition | Description |
|---|---|
| Risk level threshold | Alert when assets at CRITICAL or HIGH risk are discovered |
| New asset discovered | Alert on any new crypto asset |
| Lifecycle state change | Alert when an asset moves to compromised/revoked |
| Certificate expiring | Alert when certificates approach expiration |
| Policy violation | Alert when new assets fail compliance evaluation |
Example Rule
Section titled “Example Rule”Name: Critical Risk AlertCondition: quantumRiskLevel = CRITICALAction: Send email to admin@company.com
Notifications
Section titled “Notifications”When an alert triggers, notifications are sent via email (when SMTP is configured).
Email Configuration
Section titled “Email Configuration”Email alerts require SMTP settings in the API environment:
CBOM_ALERT_EMAIL_ENABLED=trueCBOM_SMTP_HOST=smtp.gmail.comCBOM_SMTP_PORT=587CBOM_SMTP_USERNAME=alerts@company.comCBOM_SMTP_PASSWORD=app-passwordCBOM_ALERT_EMAIL_TO=security-team@company.comScan Schedules
Section titled “Scan Schedules”Schedule automated sensor scans to run at regular intervals.
Creating a Schedule
Section titled “Creating a Schedule”- Navigate to Alerts → Schedules tab
- Click Create Schedule
- Select the sensor and scanner configuration
- Set the cron expression or interval
- Activate
Schedule Configuration
Section titled “Schedule Configuration”| Field | Description |
|---|---|
| Name | Schedule identifier |
| Sensor | Which sensor to trigger |
| Scanner Config | Which scanner configuration to use |
| Frequency | Cron expression or simple interval |
| Enabled | Active/inactive toggle |
Common Schedules
Section titled “Common Schedules”# Nightly endpoint scanName: Nightly TLS ScanCron: 0 2 * * *Scanner: https-endpoint
# Weekly full filesystem scanName: Weekly Filesystem ScanCron: 0 4 * * 0Scanner: filesystem
# Hourly certificate expiry checkName: Cert Expiry MonitorCron: 0 * * * *Scanner: https-endpoint
Alert History
Section titled “Alert History”View past alert triggers:
- When the alert fired
- Which rule triggered
- Which asset(s) caused it
- Whether notification was sent successfully
Related
Section titled “Related”- Sensors — Sensor management and manual scan triggers
- Inventory — View assets that triggered alerts
- Compliance — Policy violations that can trigger alerts
- API Deployment — SMTP configuration for email alerts