Most SASE platforms treat channel partners as a way to move product. I’ve never really seen it that way.
I sat down with @ChannelInsider to talk about why our model lets partners host and run the infrastructure themselves, in their own environments, so they keep control of enforcement and the customer relationship.
Here’s the link: https://t.co/1XlA7nLDRP
@Y_2_Surf Thanks for the heads-up @Y_2_Surf , a signature update has been shipped a few hours ago. That should address the problem. If not, please reach out to our support team and we'll investigate together.
Cybersecurity Architect's handbook has a section which illustrates how you can use Zenarmor to introduce #ZTNA into greenfield deployments.
There's an offer to giveaway 2 copies of the book.
Might be your lucky day today 👊
Security breaks when systems are stitched together instead of designed to work together.
Murat Balaban, CEO & Founder of @zenarmor:
"Most security stacks today are built as integrations rather than architectures."
The same traffic gets inspected multiple times, policies behave differently across environments, and decisions become fragmented.
#NetworkSecurity #ZeroTrust #SecOps #ThreatDetection #EnterpriseSecurity #NetworkArchitecture
@zenarmor@zenarmor Thank you and Zenarmor is a great resource to have in the security toolset, not only for business but for those at home... My book was written to help those new to security and those with years of experience and Zenarmor works with both readers...
@sec_doc just released the 2nd edition of his Cybersecurity Architect's Handbook.
The book is a very valuable resource for anyone pursuing a path to becoming a cyber security architect.
Zenarmor gets discussed in detail (with a lab exercise) in the ZTNA chapter.
Thanks Lester, we're honored!
When we say "distributed enforcement," here's what we actually mean.
Traditional SASE sends your traffic to a centralized cloud PoP for inspection. The check happens far from where the user is. Then the traffic comes back. That detour creates latency, introduces privacy concerns, and means your security depends on someone else's infrastructure staying up.
Distributed enforcement flips that. Inspection happens right where the traffic originates. On the endpoint. At the gateway. At the edge. The same policies, the same protection, but without the round trip.
It's the difference between sending every letter through a central post office and checking it at the mailbox.
#SASE #ZeroTrust #NetworkSecurity
Network Security Is Still Relevant
The perimeter, as we know it, is dead, for sure. The castle and moat model is gone. And that’s true. But what happened next is that a lot of people took that to mean network security itself doesn’t matter anymore. Just move everything to the cloud, put identity in front of it, and you’re done.
Except that’s not what happened in practice. Organizations still have networks. They still have traffic that needs to be inspected. They still have users connecting from everywhere on every kind of device. The perimeter didn’t disappear. It just moved to wherever your people are.
And that’s what gets MSPs and MSSPs excited about what we’re building. Because Zenarmor brings network security back, but in a way that actually matches how organizations work today.
The inspection happens wherever the user is. On the endpoint, at the edge, in the cloud. It’s not about backhauling traffic to some centralized location anymore. It’s about protecting people where they actually are.
For our partners especially, that changes the conversation with their customers. Instead of trying to sell a complex stack of point solutions that they have to manage across dozens of accounts, they can deliver network security through a single app that deploys in minutes and scales across their entire customer base.
That’s why they lean in when they see it. It’s not just another security product. It’s network security made relevant again for how the world actually works now.
Every new tool you add to the security stack creates another integration point, another policy set, another dashboard, and another potential blind spot.
Most organizations don't get breached because they lack tools. They get breached because too many tools create gaps between them. Policies don't align, logs don't correlate and rules conflict. IT teams now spend more time fine-tuning configurations than responding to actual threats.
Complexity isn't just an operational headache. It's a security risk that compounds over time, especially for lean teams managing distributed environments.
We wrote about why simplifying the stack is a security decision, not just an efficiency play. Link in the thread.
When your SASE vendor inspects traffic in their cloud, your data is leaving your environment.
For many organizations, that's fine. For regulated industries, it's a compliance headache. Healthcare data crossing borders. Financial records sitting in a third-party data center. Government traffic flowing through infrastructure you don't control.
This isn't a theoretical problem. GDPR, HIPAA, and data residency laws all have requirements about where sensitive data is processed and stored.
The simplest way to solve it: inspect traffic locally. If the data never leaves your environment, the residency question answers itself.
#DataPrivacy #Compliance #SASE
Zenarmor deploys in minutes. Not days or weeks.
One app. Runs on endpoints, gateways, edge, and cloud. Full SASE protection from the moment it's installed. No hardware to rack. No PoPs to configure. No service chains to build.
If you've been evaluating SASE solutions and keep running into complexity, sign up for a free trial and see the difference a single-app architecture makes. Link in the thread 👇
Something we keep hearing from mid-market IT teams:
"Enterprise SASE vendors price us out. Budget tools can't cover our remote users. We're stuck in the middle."
Mid-market companies have the same security challenges as enterprises. Distributed teams, cloud apps, compliance requirements. But they don't have the same budget or the same headcount to manage a complex stack.
They need something that's simple to deploy, covers every user and device, and doesn't require a six-figure contract to get started.
We wrote about what mid-market teams actually need and why most solutions fall short. Link in thread.
There’s one security gap most companies don't measure:
It’s the time between when a remote worker disconnects from VPN and when they reconnect.
During that window, they're still working, clicking links, logging into apps and downloading files. But nobody is inspecting that traffic. Nobody is enforcing policy or watching.
For most companies, this window is hours per day per employee. And it's invisible to the security team.
Fixing this doesn't mean forcing VPN compliance harder. It means running inspection where the user is, so the protection doesn't depend on a tunnel staying connected.
#CyberSecurity #RemoteWork #ZeroTrust
The insurance industry has three things cybercriminals look for: regulated personal data, a distributed workforce, and cloud-based networks.
You have claims adjusters working from the field, underwriters logging in from home, and third-party brokers accessing the same systems as your internal team. All of them are pulling sensitive customer data through SaaS platforms like Guidewire and Salesforce, connected by APIs that span every corner of the business.
All of that expands the attack surface and ransomware operators know it.
The challenge isn't just stopping attacks. It's maintaining consistent security enforcement across a workforce that's constantly moving between networks, devices, and locations, while also meeting regulatory requirements that don't offer exceptions for complexity.
We put together a breakdown of what this looks like in practice. Link in thread.