Alerts

How to get CVE alerts in Slack or Discord

Add the technologies you use and get the CVEs that affect them in the team's channel: critical ones right away, the rest in a daily digest.

  • Who it's forFor SOCs, MSSPs and infrastructure teams.
  • PlanSOC and MSSP plans
  • Timeabout 10 min

What you need

  • A Vexday account on the SOC or MSSP plan.
  • Permission to create a webhook: in Slack, an app with Incoming Webhooks; in Discord, the server settings.

Step by step

  1. Add the technologies

    In the dashboard, open Alerts, search for each product or package you use (FortiOS, Exchange, express…) and click Add. The CVEs that already exist become the baseline: you only get what changes from now on.

  2. Create the webhook in the channel

    In Slack: api.slack.com/apps → create an app → Incoming Webhooks → turn it on → Add New Webhook to Workspace → pick the channel and copy the URL. In Discord: Server Settings → Integrations → Webhooks → New Webhook → pick the channel → Copy Webhook URL.

  3. Register the destination

    Under Destinations, pick Slack or Discord, paste the URL and click Register. The URL is the channel's credential: Vexday stores it encrypted and shows only the beginning.

  4. Test the channel

    Click Test: the channel gets a message saying it will receive the alerts. If it does not arrive, the dashboard shows what the service answered.

  5. Tune the criticality and the digest

    Pick the criticality model: Default, or Active exploitation only for high-volume vendors. Whatever does not go out right away goes into the daily digest, at the time and time zone you choose on the destination.

Something went wrong?

The URL is not acceptedIn Slack, use an Incoming Webhook URL (hooks.slack.com/services/…): the Workflow one has another format. In Discord, the URL starts with discord.com/api/webhooks/.
The destination shows as offThe webhook was deleted in Slack or Discord. Create another one, register the new URL and remove the old destination.
Too many alerts arrivedSwitch the model to Active exploitation only or set a cap on immediate alerts per day: past it, the most severe still go out right away and the rest goes into the digest.

Frequently asked questions

Can I send each client to its own channel?

Yes: put the client's tag on the technologies, such as client-acme, and select that tag on the destination. The alerts-by-client guide shows the steps.

What if the team uses another system, such as a SIEM or Jira?

Use the JSON endpoint: Vexday sends a signed POST (HMAC-SHA256) to your system's address, which checks the signature and decides what to do. For Jira, the n8n guide has a ready-made workflow that opens and updates one ticket per CVE.

How fast does the alert arrive?

Vexday matches new and changed CVEs against your list in a round every 15 minutes. Critical ones go out in the same round.

Keep going