What are notifications?
Notifications let you receive alerts when scan results match specific conditions. Instead of checking every scan manually, you set up rules and only hear about what matters.How notifications work
1
Create a notification rule
Define what conditions should trigger an alert.
2
Choose a trigger type
Select what type of scan results to monitor (vulnerability, ports, scan status, etc.).
3
Set conditions
Specify the exact criteria (e.g., risk level is at least High).
4
Select destinations
Choose where to send the notification (email, Slack, webhook, etc.).
Trigger types
Notifications can be triggered based on different types of scan results:Condition examples
Vulnerability conditions
Rules that send findings to Jira can’t use the Diff condition.
Scan status conditions
Port Scanner conditions
Subdomains conditions
URL Fuzzer conditions
Password Auditor conditions
Domains conditions
Technology conditions
Notification destinations
Send to your account email or custom addresses.
Slack
Send to a Slack channel.
Microsoft Teams
Send to a Teams channel via webhook.
Discord
Send to a Discord channel via webhook.
Webhook
Send to any HTTP endpoint.
Nucleus
Send findings to Nucleus for vulnerability management.
Jira
Create a Jira ticket for each matching finding. Vulnerability trigger only.
Creating a notification
1
Go to Notifications
Click Notifications in the sidebar.
2
Add a notification
Click Add and enter a name.
3
Select a trigger type
Choose what to monitor, for example, Vulnerability or Port Scanner.
4
Set conditions
Add one or more conditions, for example, Risk level is at least High.
5
Select destinations
Under Notification actions, choose where to send alerts: your default email, additional addresses, or an integration like Slack, Teams, Discord, Webhook, Nucleus, or Jira.
6
Save
Click Save. The notification activates immediately.
Workspace scope
Notifications are scoped to your current workspace. Each workspace can have its own set of notification rules. The notifications configured on this page are applied to all scans running in the current workspace, whether started manually, scheduled, or via API. A notification will be sent if a scan result matches any of the defined notification rules in the workspace.Enabling and disabling
You can enable or disable notifications without deleting them:- Enabled: Notification will trigger when conditions match
- Disabled: Notification is saved but won’t trigger
Diff notifications
A diff notification tells you what changed between a finished scan and the previous scan of the same target. To get one, add the Diff condition (from previous scan) to a Vulnerability, Port Scanner or Subdomains rule. The rule fires only when something was added, removed or updated since the previous scan. A scan with no changes sends nothing.What counts as the previous scan
The previous scan is the most recent finished scan of the same target, run with the same tool, that started before the current one. For the Port Scanner, it must also use the same protocol (TCP or UDP). The scan type isn’t matched: if the previous scan was a Light scan and the current one is a Deep scan, many findings can show up as new. The first scan of a target has nothing to compare with, so it never sends a diff notification.What the message lists
Each message lists the changes in up to three groups. Groups with no changes are left out.
Each list shows up to 5 items, then “N more”. For findings, the limit applies to each risk level separately.
Findings you marked as False Positive, Ignored, Accepted or Fixed are left out of the comparison.
Where the changes appear
Email, Slack, Discord and Microsoft Teams messages include the list of changes. The email also shows when the previous scan ran and links to it, unless you use the White Label add-on. Webhooks and Nucleus get their usual payload, without the list of changes.Seeing every change
The product has no side-by-side view of two scans, so the notification is the only diff you get. To see everything that changed beyond the first 5 items, open the current scan and the previous one (the email links to it) and compare their results.Limitations
- Diff must be the only condition in its rule. You can’t combine it with conditions like Risk level, so create a separate rule for those.
- The Port Scanner Diff condition works only for Port Scanner scans.
- Rules that send findings to Jira can’t use Diff. They don’t need it: findings already sent to the same Jira project are skipped, so recurring scans don’t create duplicate tickets.
Best practices
Start with high-severity alerts
Start with high-severity alerts
Begin by setting up notifications for critical and high severity findings. Add more granular rules as needed.
Use meaningful names
Use meaningful names
Name notifications descriptively, for example “Critical vulns - Production”.
Combine conditions wisely
Combine conditions wisely
Use multiple conditions to reduce noise. For example, “Risk level at least High” AND “Finding name contains SQL”.
Use diff notifications
Use diff notifications
For scheduled scans, use diff notifications to alert only on changes since the previous scan instead of on every finding.