How to split CVE alerts by client as an MSSP
Tag each client's technologies, connect one destination per client and each one gets only its own notices, without seeing anyone else's stack, plus a monthly report for each.
What you need
- An account on the SOC or MSSP plan with each client's technologies added under Alerts.
- One destination per client: a Slack or Discord channel, or an endpoint in their system.
Step by step
Create the client
In the dashboard, open Clients, click New client, give it a name (such as client-acme, with lowercase letters, numbers, dots, underscores or hyphens) and pick its first technology.
Tag the technologies
Under Clients or Alerts, put the client's tag on each of its technologies. A technology shared by two clients carries both tags and notifies both.
Connect one destination per client
Under Alerts, register the client's destination and, in Client, select its tag. That destination gets only the notices for the client's technologies, and each notice carries only those.
Keep a general destination
The untagged destination gets everything, including CVEs and groups followed directly, which have no client. It is your SOC's channel.
Generate each client's monthly report
Under Clients, each one's Monthly report counts the alerts delivered to its destination, the CVEs in the KEV and the open CISA deadlines.