ForumsHelpBest practice for setting up AlertMonitor across multiple client tenants?

Best practice for setting up AlertMonitor across multiple client tenants?

ZeroTrust_Hannah 12/13/2025 USER

New MSP here, onboarding our first 5 clients into AlertMonitor. What's the recommended way to separate clients? Separate sites? Tags? Different agent groups?

Want to make sure technicians can only see their assigned clients and not cross-pollinate data.

SE
SecurityTrainer_Rosa12/13/2025

Use Sites for each client — that's the primary isolation boundary. Then use role-based access to limit technician visibility to specific sites. We manage 40+ clients this way and it works well.

IN
Incident_Cmdr_Tanya12/14/2025

Agree on sites. Also set up alert routing per site so the right technician group gets notified. Nothing worse than getting 3AM alerts for a client that isn't yours.

PH
PhysSec_Marcus12/15/2025

Pro tip: create a naming convention early. We use [CLIENT]-[LOCATION]-[TYPE] for device names. Makes global search incredibly powerful. e.g., ACME-DAL-DC01.

DA
DarkWeb_Monitor_Eve12/15/2025

One more thing — set up separate One Time Share policies per client. You don't want a tech accidentally sharing a client's admin password link with the wrong client contact.

Verified Access Required

To maintain the integrity of our intelligence feeds, only verified partners and security professionals can post replies.

Request Access

Thread Stats

Created12/13/2025
Last Active12/15/2025
Replies4
Views1,158