Notifications
Vulinder delivers scan completions, newly discovered vulnerabilities, threat news, and runtime events as notifications. This document explains how to see notifications inside the app. Configuring delivery to external channels (Slack, Discord) is covered in Notification channels.
Permissions
Creating or editing notification settings requires an administrator or manager role. Regular members can view notifications but cannot change the settings.
Where to see them
- Header notification bell : The bell icon at the top of the screen shows the number of unread notifications. Click it to see recent notifications.
- [Unified notifications] : See notifications from across the entire organization on one screen. Each notification also shows which service it came from.
- Per-service [Security alerts] : Open a specific service to see only the notifications limited to that service.
Notification severity
Notifications are split into two levels.
- Info : News about normal progress, such as a scan completing.
- Important : News that needs your attention, such as a scan failure, a confirmed real-world exploit, or a runtime security event.
What becomes a notification
| Notification | When |
|---|---|
| Scan completed / failed | When an analysis finishes or fails |
| New vulnerability | When a rescan finds an item that was not present before |
| Threat news | When a component you own is confirmed as actively exploited (KEV) (Security news) |
| Runtime event | When a runtime security event is detected on a server (Runtime monitoring) |
Marking as read
Notifications you have seen are marked as read and removed from the unread count on the header bell.
Related documents
- Notification channels : Get notifications on Slack and Discord
- Security news : The basis for threat news
- SLA : Remediation deadlines by severity