Skip to content
Explore msspMSSP/MDR overview
MSSP/MDR · For MSSPs and MDR providers

Run every customer's security on one platform.
Keep each one's context.

Add customers without adding consoles. Imperum gives MSSPs and MDR providers one multi-tenant platform for the process, technology, people and scale behind the service.

Tenant context across alerts, cases, connectors and reports1,400+ connectorsOn-premises, cloud, hybrid or air-gapped
Start with onboarding

Onboard a customer in five steps.From architecture to daily operations.

Start with the architecture, then onboard the customer, connect its tools, set up the team and run the service.

  1. 01Architecture

    Decide where each customer runs: your shared platform, or a remote dedicated instance on a sensitive customer's site.

  2. 02Customer

    Tenant, frameworks and SLA targets, set in one onboarding form.

  3. 03Technology

    Connect tools with a profile per customer, a VPN route where needed and pooled API keys.

  4. 04Team

    Assign dedicated or pooled analysts and add the customer contacts Virtus can call.

  5. 05Operate

    Alerts, cases, reports and dashboards for each customer.

01 - Process

Set up each customer's service.Frameworks, targets and reports follow the customer.

Onboard a customer as its own tenant, then choose the frameworks, SLA targets, reports and dashboards its service needs.

Reports › Create AI ReportSample data
Describe the report a customer needs, pick focus areas and frameworks, and Virtus generates a template from that tenant's data.
02 - Technology

Connect each customer's tools.Deploy a connector once. Configure it per customer.

Choose from 1,400+ connectors and 26,000+ connector actions. Deploy a connector once, then set credentials, VPN route and deployment location per customer.

Marketplace › Configure › Tenant ProfilesSample data
One connector, a separate credential and configuration profile per customer.

Tenant Profiles

Deploy a connector once. Each customer gets its own profile with credentials and endpoint.

Marketplace › Configure › Tenant Profiles

Shared connector routing

Route tickets from one Sentinel, QRadar, ServiceNow, FortiSIEM or Sophos connector into each customer's tenant by a field value.

Marketplace › Configure › Multi-tenant Routing

VPN profiles for connectors

Reach customer tools behind a VPN. Assign a VPN profile to that customer's tenant profile.

Settings › VPN Profiles

Remote dedicated instances

Serve sensitive customers from a headless Imperum on their site, linked to your main platform. Deploy connectors locally or to that instance.

Multi-Tenant › Remote Dedicated Instances

API key pool

Pool VirusTotal keys. Imperum switches keys at the limit you set or when VirusTotal returns a rate-limit response.

Connector › API Key Pool

Tenant isolation

On shared instances, tenant context scopes supported views, API operations and connector credentials. Full database isolation needs a dedicated instance.

Onboarding › Plan & Compliance

Self-Service Portal

Customize each customer's Self-Service Portal for requests, permitted cases, your service catalog and approvals, without access to the platform.

Settings › Self-Service Portal

Access control and audit log

Scope roles to tenants. Track who did what, who is signed in, their location and time on the platform.

Settings › Access Control, Audit Log

Tenant Administrator

Let a customer's own admin manage users, roles and settings in their tenants. Your other customers stay out of view.

Access Control › Roles

Single sign-on and directory

Use SAML or OIDC SSO per customer or across your tenant tree. LDAP or Active Directory connects one directory for the platform.

Settings › Integrations › SSO, LDAP

APIs, MCP and SIEM forwarding

Use the Platform and Reporting APIs and Imperum's MCP server. The MCP Gateway also connects external MCP servers. Forward platform events to your SIEM.

Settings › Integrations; MCP Gateway
03 - People

Run a large team around the clock.Shifts, skills and presence in one place.

See who is on shift and what they are working on, plan coverage across time zones, coach junior analysts and bring the customer's people in when a case escalates.

Settings › Roster › Teams & ShiftsSample data
Shifts per team and time zone, with analysts and Virtus agents on the same shift.

Dedicated or pooled analysts

Dedicate analysts to a customer or serve it from your shared pool.

Onboarding › Users & RBAC; Access Control

Team presence and chat

See who is on shift and what analysts are working on. Send direct messages, chat per case and mirror case chat to Microsoft Teams both ways.

My Space; case › Chat

Case Router and Prioritizer

Prioritizer scores each case. Router ranks analysts by skills, case history and workload, and can add a machine learning model trained on closed cases.

Case Router

Magister

Pair junior analysts with mentors. In an active mentorship, a case the junior proposes to close goes to the mentor for review before it closes.

Autonomous › Magister

Roster

Plan shifts by team and time zone with analysts and Virtus agents together. Import Microsoft Teams Shifts.

Settings › Roster

Follow-the-Sun Coverage

Map teams and shifts across time zones. On cloud deployments, a world map shows where analysts are connected from now.

Roster › Follow-the-Sun Coverage

Shift handoff

Hand open cases to the next shift with handoff notes. The case list shows who handed each case over.

My Space › Shift Handoff

Availability and HR Sync

Auto routing skips unavailable analysts, including those away or on leave. HR Sync imports approved leave from HR tools such as BambooHR.

Status menu; Roster › HR Sync

Analyst VPN

Enroll remote analysts in the platform's built-in WireGuard VPN, with no separate VPN concentrator to buy. Each downloads their own configuration.

Roster › VPN

Customer team and Virtus calls

Name a customer's contacts per case stage. Virtus calls them by voice or emails them. On a call they can acknowledge, ask for a callback or hear a brief.

Onboarding › Customer Team

War Room

Share a War Room magic link so the customer works with your team on the case without access to the platform.

Case › War Room
04 - Scalability

Be ready when a customer is under attack.Availability tiers and auto-tuning.

An attack on one customer can bring a surge of alerts. Choose the availability tier your deployment supports, and when Imperum controls its host, auto-tuning recommends or applies more resources as load rises.

Settings › High Availability › What each tier survivesSample data
What each tier survives, as the product states it.

High availability

Run a single node, a warm standby on a second host, or single-host HA that fails over by itself. Warm standby is not offered for MSSP deployments yet.

Settings › High Availability

Auto-tuning

When Imperum controls its host, auto-tuning recommends more CPU and memory as load rises, or applies it. On Kubernetes it also adds storage and replicas.

Health & Troubleshooting › Auto-Tuning

Questions from MSSPs and MDR providers.

1How does Imperum support MSSPs and MDR providers?

Multi-tenant operations give providers customer-scoped views, connector profiles and onboarding workflows. Authorized operators can work across their permitted customer scope, while the self-service portal offers customer access to requests and cases. Configure tenant permissions and customer workflows to match the service you deliver, and confirm the required modules in your license.

2Is The Portal the same thing as the customer portal?

The Portal is a product edition whose default modules include multi-tenant operations, Case Router and Case Prioritizer. The self-service customer portal is a separate feature for submitting requests and following permitted cases. Distinguish the edition you license from the customer-facing access and workflows you configure.

3How is each customer’s data kept apart?

Multi-tenant mode uses tenant context to scope supported views, API operations and connector credentials. Customer profiles let you configure separate service connections. Authorized provider operators and administrators can access the customer scope assigned to them. Confirm the required data boundary, permissions and deployment arrangement for each customer during architecture review.

4Can each customer have its own case response targets?

Yes. You can configure case time budgets by priority and lifecycle phase, with customer overrides and inheritance from a parent tenant. A rule-specific target takes precedence; otherwise the tenant setting or global default applies. These are workflow targets for tracking your service, not a promise of response times from Imperum.

5Can a provider also use Imperum’s AI triage?

AI agents belong to the Autonomous SOC and SecOps Platform product defaults; they are not part of The Portal’s default module set. If you want AI triage alongside provider operations, discuss a license that covers both capabilities, then configure the relevant integrations and triage rules. The enabled modules on your license determine access.

6Can one playbook be deployed to several customers?

Yes. An authorized operator can deploy an enabled, validated playbook to selected tenants. Deployment creates a tenant-specific copy and records its relationship to the source.

A deployment can be removed from one tenant without removing the source playbook or another tenant’s copy. Check each tenant’s connector setup, permissions and approval configuration before putting the workflow into use.

7Does Imperum replace our SIEM or EDR?

Imperum can work alongside an existing SIEM or EDR through configured integrations. Those connections can supply alerts and make supported actions available to investigations and playbooks. Coverage depends on the connector, credentials and configuration, so validate the tools and workflows you want to retain.

Have any other questions? Talk to our team

Bring every customer
onto one platform.

Bring one customer's tools and alerts. See its tenant, the workflows licensed for your service and the customer's front door on your own use case.

Open on YouTube

Film · 1:00

Imperum AI Fabric

One minute on the AI Fabric appliance: the agents, Agent Studio, routing, pools, Veil and token metering.