Multitenancy
Objective
This article describes how to configure and administer multi-tenancy in UTM Stack through federation services or data source groups. It also explains how to filter alerts, logs, and SaaS integrations by tenant so every client's data stays orderly and simple to handle.
1. Select the Suitable Multi-Tenancy Method
Determine which multi-tenancy model fits your environment:
Federation Service: For administering several dedicated UTM Stack servers through a single centralized interface.
Single Server with Data Source Groups: For smaller clients, or when dedicated servers are not needed.
Determine if clients require a separate server instance, on-premises hosting, or centralized administration across multiple environments.
2. Leverage Federation Service to Centrally Manage Multiple Servers
When every client has a dedicated UTM Stack server, use the federation service. Link all client servers into a single centralized management layer to deliver one pane of glass for monitoring and administering multiple environments. Make sure each server is registered correctly and reachable from the federation console.
3. Set Up One Data Source Group per Client
Within UTM Stack, set up a distinct data source group for each client (for example, Client A, Client B). Choose clear, consistent names so team members can identify the right client group quickly. Keep each group assigned to a single client only to prevent data mixing.
4. Attach Each Data Source to the Appropriate Client Group
Open the data source or device that you need to assign.
Choose the correct client group for the asset.
Click Apply Group to save the assignment.
Verify that the asset is now part of the right group.
5. Check Assets Inside the Assigned Group
Navigate to the Assets area. Access the applicable asset group to verify the assigned devices are listed there. If an asset is absent, check the group assignment again and reapply it.
6. Use Data Source Groups to Filter Alerts by Client
Open the Alerts view. Use the data source groups shown on the left to filter alerts. Select the target client group to see only alerts tied to that client, cutting noise and sharpening focus.
7. Keep Client Context in Events and Log Explorer
After selecting a client in Alerts, move to Events or Log Explorer. Ensure the client context remains active. This enables incident investigation without needing to switch tenants manually.
8. Set Up Multi-Tenancy for SaaS Integrations
When connecting SaaS platforms (for example, Microsoft 365), create one tenant connection for each client's SaaS environment. Link UTM Stack to every client's SaaS infrastructure separately and confirm each connection is assigned to the correct customer.
9. Use the Dashboard to Filter SaaS Tenants
Use the dashboard tenant selector to move between connected SaaS tenants. Make sure the dashboard refreshes to display only that client's SaaS data for quick comparisons or troubleshooting.
Cautionary Notes
Avoid Data Mixing: Avoid assigning several clients to one data source group unless that is intentional.
Double-check Names: Before making changes, check the names of tenants and groups to avoid misrouting.
Verify Context: After switching views, always confirm the selected context to ensure you are investigating the correct client.
Isolation: If clients need strict data isolation, choose dedicated servers with federation instead of a shared server model.
Tips for Efficiency
Naming Conventions: Use consistent naming for groups and tenants to speed up filtering.
Onboarding: Establish groups and tenants as part of the initial onboarding process.
Mapping: Keep a simple documentation mapping that links client name to data source group and SaaS tenant.
Training: Teach team members to always check the selected group before they review logs or alerts.