Multi-tenant NAC for MSSPs
Multi-tenant NAC is network access control where one platform serves several customers or business units, each in a segregated policy domain under a unified policy framework. The S3M platform has a native multi-tenant architecture for MSSPs and can be deployed on-premises, as SaaS, or through MSSP partners.
Managed security service providers (MSSPs) run security for many customers at once. That makes network access control (NAC) a different problem than it is for a single enterprise: the platform has to keep each customer separate and still let the provider manage the service as a whole. This post explains what multi-tenant NAC is, what S3M Security says about its multi-tenant architecture, and what to check before you build a managed NAC service on it.
What is multi-tenant NAC?
NAC decides which users and devices may connect to a network and what they may reach, typically using IEEE 802.1X and RADIUS to check identity and device status before granting access. In a multi-tenant design, one platform serves several tenants, such as customers or business units, and keeps each tenant's configuration separate from the others.
S3M describes its version as segregated policy domains that let service providers and large enterprises manage multiple business units under a unified policy framework. The platform FAQ extends the same idea to customers: the architecture supports managing multiple business units or customers under a unified security framework. The full description is on the S3M Hybrid Enterprise Network Security Platform page.
Why do MSSPs need multi-tenant NAC?
An MSSP operates security on behalf of its customers, and every customer brings its own users, devices, sites and rules. Without multi-tenancy, the provider ends up running a separate NAC deployment for each customer, with separate policies to keep up to date. A multi-tenant platform brings those customers under one framework while keeping their policy domains apart.
The architecture matters here. S3M's own comparison sets legacy NAC and cloud-only NAC against its platform on three points that affect a managed service:
| Capability | Legacy NAC | Cloud-only NAC | S3M |
|---|---|---|---|
| Deployment | Hardware-bound, on-prem only | Cloud-only, no on-prem option | On-prem + SaaS + MSSP |
| MSSP-ready architecture | Bolt-on | Limited multi-tenancy | Native multi-tenant |
| Regulatory deployment | On-prem only | Cloud only | Customer-chosen |
Based on public vendor documentation as of 2026.
What does "native multi-tenant" mean in the S3M platform?
S3M's partner page calls the platform MSSP-ready, with a native multi-tenant architecture. S3M's platform and partner pages point to three building blocks:
- Segregated policy domains. Policy domains are kept separate, so service providers and large enterprises can manage multiple business units or customers under one policy framework.
- A single policy engine. At the center sits a unified policy engine that evaluates identity, posture, role and contextual signals in real time. It applies dynamic VLAN and ACL assignment and real-time Change of Authorization (CoA) rather than relying only on static VLAN mapping.
- One platform for several controls. NAC, endpoint, guest WiFi and private APN sit under one policy engine, which S3M describes as one contract and one console for your customer.
How can an MSSP deploy S3M?
S3M says its unified platform can be deployed on-prem, as SaaS or via MSSP partners. For partners, that means delivering S3M on-premises, as SaaS or as a multi-tenant managed service for their customers. S3M positions the options by need: on-prem for regulated environments, SaaS for distributed teams, and your MSSP practice as the third route, with no hardware lock-in.
On-prem and hybrid deployments support virtual appliances, clustered architectures and distributed enforcement nodes across branch and core environments. S3M also lists regulatory deployment as customer-chosen, as the table above shows.
What does ConnGuard NAC add to a managed service?
ConnGuard NAC is S3M's enterprise NAC platform. It continuously validates user identity, device posture and contextual risk before granting access. Several of its capabilities matter to a provider running access control for other organizations:
- Managed and unmanaged devices. Agent-based posture validation covers managed endpoints. Agentless profiling, using DHCP fingerprinting, MAC profiling and behavioral analysis, classifies IoT systems, printers, contractor and BYOD devices without software installation.
- Open standards. ConnGuard is built on IEEE 802.1X, RADIUS, SNMP and REST APIs, so policy can be enforced consistently without requiring infrastructure replacement.
- Firewall and SIEM integration. It shares user identity and session context with firewalls, and it is compatible with SIEM platforms through CEF and Syslog formats.
One point to confirm: ConnGuard's own product page lists on-prem deployment, while the multi-tenant, SaaS and MSSP options are described for the unified platform. Ask S3M how each option applies to the modules you plan to offer.
What does SAMI add, and how does it treat customer data?
SAMI is S3M's conversational security analytics layer. It sits on top of ConnGuard and APNZone, reads their live NAC and cellular Zero Trust telemetry, and answers questions in plain language: users online today, endpoints failing posture, active guest sessions, or which SIM is connecting from outside its authorized region.
Three design choices stand out for a provider:
- Read-only. SAMI never changes policy or sessions. When action is needed, it recommends the step and points to APNZone, where the team acts.
- Tenant-isolated. Each environment's data stays its own, and nothing is pooled across customers. Where model improvements are shared, raw subscriber data never is.
- No new agents or hardware. SAMI works from telemetry the platform already produces.
Every answer is source-backed and traceable to the telemetry behind it, which gives reviewers clear provenance.
What should an MSSP check before choosing a multi-tenant NAC?
Whichever vendor you evaluate, five questions help separate a native design from an add-on:
- Is multi-tenancy built in? S3M describes a native multi-tenant architecture with segregated policy domains. Ask every vendor whether theirs is native or bolted on.
- Can you deploy where each customer needs it? S3M lists on-prem, SaaS and MSSP delivery. Check that the vendor you pick offers all the models your customers will ask for.
- Does it fit the customer's existing network? Look for open standards such as 802.1X, RADIUS, SNMP and REST APIs rather than infrastructure replacement.
- Is analytics kept per customer? Ask whether data is pooled. SAMI is described as tenant-isolated.
- Does it cover unmanaged devices? Without deep visibility and classification, printers, contractor laptops and IoT devices expand the attack surface silently.
How does the S3M partner program support MSSPs?
The S3M partner program is open to value-added distributors, resellers, systems integrators and MSSPs. Partners get margins, deal registration, sales and technical training, and marketing development funds, with more at higher tiers, such as NFR licenses and a dedicated channel manager. The reseller program page lays out the Authorized, Premier and Elite tiers.
S3M also describes the platform as modular: "Start with NAC. Add endpoint or guest in weeks, not quarters." On time to value, its partner page says: "First module live in days, not quarters. Full platform rollout in weeks."
If you run an MSSP practice and want to offer managed NAC, start on the S3M partners page to see how the program works and how to become a partner.