Enterprise networks have evolved quickly, but security hasn’t always kept up. Users now switch between home, office, and public networks, while applications run across clouds and containers. Even so, many SASE models still route traffic through centralized inspection points.
Zenarmor’s latest update addresses this gap by extending its distributed SASE architecture to mobile endpoints and containerized environments.Instead of sending traffic back to a vendor-controlled cloud point of presence, Zenarmor’s model places inspection directly in the traffic path, inside infrastructure that organizations or partners already operate. That includes branch networks, cloud environments, and now mobile devices and container platforms. The immediate impact is lower latency and fewer routing detours, but the bigger story is control. Enterprises and service providers can enforce policies within their own environments rather than relying on external inspection layers.
What Changes for MSPs and Network Operators
That shift also changes how service providers deploy and operate security.
Murat Balaban, founder and CEO of Zenarmor, explained that the platform is designed to run directly within customer or partner infrastructure, with management handled through a centralized console.
He told ChannelE2E, “Service providers deploy Zenarmor using a distributed SASE model that runs directly within customer or partner infrastructure, supporting sovereign SASE deployments, rather than routing traffic through vendor-operated PoPs,” he said. “Gateways can be deployed with a simple installation script on platforms such as pfSense, OPNsense, OpenWRT, Linux, and cloud environments, while the same security stack can also run directly on endpoints.”
For MSPs and network operators, that translates into a different operational model. “Instead of backhauling traffic to distant cloud inspection points, traffic is inspected locally at gateways, endpoints, or cloud workloads,” Balaban said. “Importantly, Zenarmor integrates with existing infrastructure with little to no operational changes required. Service providers can deploy the platform on existing gateways, virtual machines, cloud environments, or endpoints rather than redesigning their networks.”
Extending SASE to Mobile Users
The mobile expansion matters because remote work is no longer an edge case. Phones and tablets routinely access corporate apps, but they often sit outside traditional network controls. Zenarmor’s approach connects mobile users to the nearest gateway, where traffic is inspected inline before reaching the internet or internal resources. That allows consistent policy enforcement across devices without forcing everything through a central cloud. For MSPs and network operators, this creates a cleaner way to extend managed security services to roaming users without adding another layer of routing complexity.
Bringing Security Into Containerized Environments
Container support adds another layer to this. As more workloads move into Kubernetes and other ephemeral environments, security tools need to keep up with infrastructure that spins up and down quickly. By packaging gateways as Docker containers, Zenarmor makes it possible to deploy inspection directly inside these environments. This reduces the gap between application deployment and security enforcement, which has been a persistent issue in cloud-native setups.
Keeping Policy and Visibility Consistent
One challenge with distributed enforcement is maintaining consistency. If inspection happens across endpoints, branches, and cloud workloads, policy drift and visibility gaps can quickly follow.
Balaban said the platform addresses this through centralized orchestration. “Security policies are defined once and automatically enforced across all deployment locations, including gateways, endpoints, containers, and cloud workloads,” he said. “All enforcement points stream telemetry and logs to Zenconsole, giving security teams a unified view of activity across users, devices, and locations.”
That centralized view also connects into existing SOC workflows. “The platform integrates with SIEM, SOAR, and monitoring platforms through APIs and Syslog, allowing organizations to maintain simple management while fitting into existing security workflows,” Balaban added. For teams already managing multiple tools, that integration layer matters as much as the enforcement model itself.
Where This Fits in the Broader SASE Shift
There’s also a broader industry angle here. Many SASE offerings still depend on centralized cloud inspection points, even as networks have become more distributed. Balaban framed Zenarmor’s approach as a response to that mismatch. “Zenarmor enables enforcement to run directly within customer or partner infrastructure, with the cloud used primarily for centralized management,” he said. “The SASE stack can run across gateways, endpoints, and cloud environments, allowing inspection to occur close to users and applications.”
For partners, that architecture shifts control and responsibility. “Because Zenarmor can run directly within partner or customer infrastructure, MSPs and network operators are not dependent on vendor PoPs for upgrades, patches, or issue resolution,” Balaban said. “Partners can deploy, update, and operate the platform within their own environments, enabling faster customer deployments and quicker issue resolution.” He also pointed to multi-tenant management and white-label capabilities as part of how partners can package the platform into their own managed services.
Why This Matters Now
Security decisions are starting to depend more on the device and the user, not just the network. That’s also where SASE begins to connect more closely with Zero Trust, especially as users and workloads keep moving across environments. For organizations, it can make security easier to manage while giving them more control over how traffic is handled. For service providers, it opens up new ways to deliver security that better match how modern networks are set up.
