Skip to main content
xorlab’s multi-tenancy capabilities allow service providers to protect and manage multiple organizations from a single interface by sharing computing resources. This simplifies operations by offering unified management, streamlining the efficiency of security analysts, and reducing operational costs.

Prerequisites

Multi-tenancy support should work with all existing integration option. See Integration.

Initial setup

For setup instructions, refer to Multi-Tenancy Configuration

Tenant Selection in the UI

A tenant selection box is available at the top of the toolbar. It controls which tenant’s data or configuration is displayed:
  • Saved Searches, Campaigns, and Lists: Filter by a single tenant or show items active across all tenants.
  • Messages, Quarantine, Reports, etc.: Show data belonging to specific tenants or across all tenants.
  • Note: “All Tenants” in the filter shows shared configurations, not a merged view of all individual tenant configurations.

Tenant Aware Features

With ongoing improvements to multi-tenancy support, more features are now tenant-aware, allowing configuration and data to be assigned either to specific tenants or shared across all tenants.

Campaigns and Saved Searches

Campaigns and Saved Searches are tenant-aware.
  • Campaigns or Saved Searches created by a Tenant-Restricted User apply only within that tenant’s environment.
  • Campaigns or Saved Searches created by a Global User apply globally unless assigned to a specific tenant.

Lists

Lists, such as VIP lists and blocklists, can be tenant-specific or shared globally. This ensures sensitive entries stay within the correct tenant, while shared lists support cross-tenant use cases.

Local Reputation

Local domain reputation is tracked per tenant to prevent cross-tenant influence. Reputation scores reflect only the behavior observed within each tenant environment.

Dynamic Rules

Dynamic RuleLists can be defined per tenant, allowing tailored rule sets for each organization. Global rule lists remain available for shared use cases.

Custom Rules

Custom rules can be created for individual tenants in the Expert Editor under: /activeguard/core/rule_sets/<tenant name>. Important: Do not rename or move tenant directories in the Expert Editor. This will disrupt rule processing.

Quarantine Notifications

Quarantine notifications support tenant-specific configurations. You can define a per-tenant authenticationBackend in guarded_tenants.yml to ensure notification emails contain correct URLs to each tenant’s self-service portal.

Limitations and Known Issues

Abuse Mailbox

The Reporting Integration, or “Abuse Mailbox”, is still shared across all tenants. A single email address is used for reporting. However, reported messages remain isolated per tenant and are not visible to others. It’s also possible to customize the Quaranantine Notification Template for each tenant.

Case Isolation for M365

Multi-tenancy support is not yet supported for Case Isolation for M365.