How to receive CVE alerts by webhook in your system and verify the signature (HMAC)
Get your stack's CVEs in a JSON POST signed with HMAC-SHA256, straight into the SIEM, SOAR or ticketing system, with the same identifier on every attempt so nothing is processed twice.
What you need
- A Vexday account on the SOC or MSSP plan with technologies added under Alerts.
- A public https address in your system, on port 443 or 8443, that accepts JSON POSTs.
Step by step
Register the endpoint
Under Alerts, in the Destinations section, pick JSON endpoint, paste your system's URL and click Register. An internal network address, a private IP or a port other than 443 and 8443 is refused.
Store the secret
On the endpoint card, click Show and copy the secret into your system. You use it to verify the signature; Generate a new secret invalidates the old one immediately.
Verify the signature
Each POST carries the X-Vexday-Signature header. Recompute the HMAC-SHA256 of "t.body" with the secret, over the raw body bytes, before parsing the JSON, compare in constant time and reject a t more than five minutes off.
X-Vexday-Event: cve.alerts X-Vexday-Delivery: 4bf933c7-c07a-4a45-a1b0-8729d2eebc8e X-Vexday-Signature: t=1762178700,v1=<HMAC-SHA256 hex>
The verification code in Python and Node, with the JSON example →Answer fast and skip repeats
Answer with a 2xx code as soon as it arrives and process it afterwards. X-Vexday-Delivery is the same on every attempt: skip a delivery you already processed. Without a 2xx, Vexday retries over a few hours, and a 410 turns the endpoint off.
Test it
Click Test: the endpoint gets a signed ping event, and the dashboard shows what it answered and how fast. Deliveries keeps the history of every attempt.