A scan takes 90 to 120 minutes to complete. If a Critical finding — a leaked API key, an exposed database, a subdomain takeover — is detected in the first 10 minutes of a scan, waiting for the full report to arrive means your team is unaware of a serious exposure for another hour.
VeilScan fires Slack alerts for Critical and High findings as soon as they are detected and verified, not when the full scan report is ready. For security-sensitive environments, this can be the difference between a finding being contained quickly and a finding sitting unnoticed until someone checks their email.
Each Slack alert contains:
The alert is designed to give your team enough context to begin triage immediately, without waiting for the full report.
#security-alerts or #engineering).The full setup takes under 60 seconds. The integration works with any Slack workspace and any channel — you can route different domain alerts to different channels using multiple webhook URLs if needed.
Slack alerts are available on Starter, Core, and Pro plans. The free plan does not include Slack integration. See all plans for a full comparison.
For teams that want faster response to critical findings, the Pro plan includes weekly scans — reducing the window between a vulnerability being introduced and being detected, and sending alerts more frequently.
See: Continuous Monitoring feature · Documentation: Connecting Slack
Slack alerts are sent for new Critical and High findings only. Medium and Low findings appear in your dashboard and email report. If you want Slack notifications for all findings, contact hello@veilscan.net to discuss your use case.
Each VeilScan account supports one Slack webhook configuration. If you need alerts in multiple channels, you can configure your Slack workspace to forward messages from one channel to another. Enterprise multi-webhook support is on the roadmap — contact hello@veilscan.net if this is a priority for your team.
If the webhook fails to deliver (e.g. the webhook URL is revoked in Slack), VeilScan logs the failed delivery attempt. The finding still appears in your dashboard and email report. You can update the webhook URL in Settings at any time. Use the Test Integration button to verify the connection is active.