v1.11.0Latest
Notification rules for dependencies and container/IaC scans
Highlights
- Get alerted the moment a dependency or container scan finds something — no more waiting for a daily check
- Four new notification rule types covering npm/Docker dependencies and container, IaC, and Kubernetes scans
- "Notify only on new findings" so you hear about each vulnerability once, not on every scan
- Existing container scan notification settings are migrated into the same rules — all alerts in one place
New Features
- Dependency vulnerability alerts. Create a rule that fires when a dependency scan finds a CVE at or above a severity threshold (Critical / High / Medium / Low) in your npm or Docker projects. Filter by project, and choose to be alerted only about findings you haven't seen before.
- Outdated dependency alerts. Get notified when packages fall behind their latest release, with the major/minor/patch update level included.
- Container image vulnerability alerts. A rule that fires when a container image scan finds a CVE above your chosen severity. Filter by image.
- IaC / Kubernetes misconfiguration alerts. Be notified when an infrastructure-as-code or Kubernetes scan flags a misconfiguration above a severity threshold.
- Event-driven delivery. These new rules fire the instant a scan completes rather than on a fixed schedule, so security findings reach your channels (Slack, Email, Telegram, Discord, MS Teams, PagerDuty) right away.
Improvements
- Container and IaC scan notifications now run through the unified notification rules engine. Your existing container scan notification settings are automatically migrated into equivalent rules, so every alert — servers, dependencies, and containers — is configured and delivered the same way.
- Each scan rule supports a "notify only on new findings" toggle, with built-in deduplication so the same vulnerability doesn't alert you on every scan.
