A Make workflow that uses Apify. NexGenData has no official Make app — you run a public-data Apify actor inside Make through Make’s official Apify integration, on a schedule, with your own Apify token.
The problem: new vulnerabilities drop faster than teams can triage
Hundreds of CVEs publish weekly, but only a few matter to your stack — the ones affecting your vendors, especially anything on CISA’s Known Exploited Vulnerabilities (KEV) list or with a high EPSS exploit-probability. Watching feeds by hand is noisy and slow. A scheduled Make scenario filters to what’s relevant and alerts your team in Slack the moment it lands.
Who this is for
Security, IT, and platform/dev teams who want vendor- and product-specific vulnerability alerts without monitoring raw feeds.
The Make workflow
- Schedule trigger — run a few times a day.
- Run an Actor — Apify “Run an Actor” → CVE Vulnerability Monitor (NVD + CISA KEV + EPSS), with your vendors/products in the Input JSON.
- Get Dataset Items — pull CVE ID, CVSS, CISA KEV flag, EPSS, summary.
- Filter / dedupe — keep only KEV = true OR CVSS ≥ 9 (your threshold); drop CVEs already seen.
- Send to destination — Slack alert, email, Google Sheets log, or a webhook into your ticketing tool.
Sample input (vendor watchlist)
| vendor | product |
|---|---|
| fortinet | fortios |
| microsoft | windows |
| apache | struts |
Sample output (KEV-filtered alerts)
| cve_id | vendor | cvss | cisa_kev | epss | summary |
|---|---|---|---|---|---|
| CVE-2026-12345 | fortinet | 9.8 | true | 0.91 | Pre-auth RCE in SSL-VPN (exploited) |
| CVE-2026-30021 | apache | 9.1 | true | 0.77 | OGNL injection RCE |
Illustrative sample.
Run it on a schedule
Scheduled runs give your team a tuned vulnerability feed: only CVEs that hit your vendors and cross your severity/KEV threshold reach Slack — deduped, so no repeat noise.
Try it
Run the CVE Vulnerability Monitor →
Browse more: Cybersecurity & Domain Intelligence cluster
More Make workflows
FAQ
What sources does it use? The actor combines NVD (CVE data), CISA KEV (known-exploited list), and EPSS (exploit-probability scoring).
How do I cut the noise? Filter on KEV = true or a CVSS/EPSS threshold, and dedupe by CVE ID so each alert fires once.
Is this an official Make app? No — it’s a Make workflow using Make’s official Apify integration with your own Apify token.