MSSP Multi-Tenancy lets a security provider see across many customers today. Fleet Command Roadmap will let a single customer see across their own branches. Both build on tenant-scoped identities, bounded summary publishing and role-based views. The difference is who logs in, which tenants they are assigned and which actions they may take.
Customers run Edg3 across many branches and want one console. Security providers run Edg3 across many customers and want one console too. Same problem statement, different audience. So we are building two surfaces on top of one engine: the MSSP console is available by invitation, and Fleet Command is on the roadmap.
A single organisation runs Edg3 across multiple sites: head office, datacentres, remote offices. The customer’s own SOC team will log into one dashboard, hosted in their Edg3 cloud tenant, and see every branch.
A managed security services provider operates Edg3 for many independent customers. Their analysts log into a dedicated console and work within their assigned customer scope.
Customer telemetry stays on its own tenant data path. Bounded summaries and approval items are published to the partner surface with an explicit tenant identifier and analyst scope. Detailed access follows an authorised drill-down path rather than a shared raw-data lake.
This illustrative organisation runs Edg3 in three places. London is the primary site. Cape Town is a datacentre. Sydney is a remote site. Each supported branch detects locally, can isolate a qualifying ransomware verdict locally on Windows hosts, then publishes a bounded summary up to London on a configured schedule. The Head of Security in London opens one dashboard and sees the configured fleet view.
Edge agents · dedicated tenant · local detection · hosts the Fleet Command Dashboard
Edge agents · dedicated tenant · local detection · publishes to London
Edge agents · dedicated tenant · local detection · publishes to London
One dashboard. Three branches at a glance. “London is fine, Cape Town has a SCADA spike, Sydney’s compliance score dipped overnight.” No more flipping between three separate consoles to get the picture, no per-site logins, no stitch-it-together emails between branch SOC analysts.
In this illustrative scenario, an MSSP runs Edg3 for twelve independent customers across finance,
health, retail, energy, ICS and maritime. Each customer has its own dedicated cloud instance and
its own data. Apex’s analysts log into mssp.edg3.io
and filter within the customer assignments authorised for their session.
One console. The portfolio view lists every customer the analyst is assigned to, with each customer’s health and open approvals, and the approval queue filters to one customer at a time. Selecting several customers to re-scope the whole console, folding an acquired MSSP’s customers in under a parent partner, and delegating a subset of customers to another analyst are on the roadmap. Roadmap
The MSSP surface does not merge every customer’s raw telemetry into one shared partner database. Each customer keeps its own tenant data path. The partner console receives bounded summaries, approval items and audit events carrying an explicit tenant_id.
Partner-side queue and summary records carry a tenant_id. The queue and portfolio views return only the customers assigned to the analyst. The example below illustrates the scoped partner view; it is not a shared raw-event lake.
| tenant_id | event_time | host | rule_id | severity |
|---|---|---|---|---|
| tenant_a | 03:31:18 | acm-dc-01 | T1003.001 | critical |
| tenant_b | 03:31:42 | bcn-edr-09 | T1110.003 | medium |
| tenant_a | 03:32:05 | fin-jump-04 | T1059.001 | high |
| tenant_c | 03:32:14 | cob-fw-01 | T1071.001 | low |
| tenant_d | 03:32:51 | dlt-scada-7 | T0809 | high |
| tenant_a | 03:33:09 | acm-dc-01 | T1003.001 | critical |
| tenant_b | 03:33:20 | ehr-app-22 | T1110.003 | medium |
| tenant_e | 03:33:48 | ret-pos-12 | T1486 | critical |
tenant_id = 'b'tenant_id IN ('a','b','c')Customer telemetry stays on its own tenant data path. The partner surface combines only the bounded records required for authorised cross-customer operations and scopes its queue and portfolio views to each analyst’s assigned customers.
Fleet and MSSP surfaces reuse the same tenant identity, summary and authorisation concepts while preserving the distinct customer and provider boundaries.
| Building block | Fleet Command Roadmap | MSSP Multi-Tenancy |
|---|---|---|
| Dedicated instance per tenant | Each branch runs its own Edge instance. | Each customer runs its own Edge instance. |
| Periodic summary publishing | Branches publish bounded summaries on a configured cadence. | Customers publish bounded partner summaries on a configured cadence. |
| Logical tenant grouping (‘scope’) | A fleet = a customer’s set of branches. | A scope = an analyst’s set of customers. |
| Per-tenant activation | Fleet Command switched on when a new branch is provisioned into a fleet. | MSSP console set up per provider during invitation-only onboarding. |
| Forward-compatible identifiers | Records stamped with branch_id and fleet_id. | Partner records retain tenant_id and partner-scope metadata. |
Fleet Command is a customer-funded view of the customer’s own estate. MSSP Multi-Tenancy is a provider-funded view of many customers’ estates. Same engine, different audience, console, scope, hierarchy and authentication.
| Dimension | Fleet Command Roadmap | MSSP Multi-Tenancy |
|---|---|---|
| Primary audience | The customer’s own SOC team. | The provider’s analysts. |
| Console location | In the customer’s primary Edg3 cloud tenant. | Dedicated provider URL, e.g. mssp.edg3.io. |
| Scope model | Fixed. A fleet’s branches are its branches. | Filtered within the analyst’s assigned tenant set. |
| Hierarchy | Flat. One customer to many branches. | Flat today: one provider, many customers. Parent and delegated partner scopes are on the roadmap. Roadmap |
| Login & access control | Customer’s existing SOC login. | Provider login with per-customer ACLs. |
Today an operator session receives an authorised set of tenant identifiers. Parent and delegated partner views are on the roadmap; the example below illustrates the planned model.
The parent view would receive the authorised union of {a..h}, and delegated views would stay bounded to their assigned sets. Parent and sub-partner relationships are not available yet.