I've been using Banyan as our primary ZTNA provider for about a year now, and I generally like the platform's core concept. The shift from traditional VPNs has been great for user experience. But every time I see a roadmap update, I can't help but feel a bit...disconnected.
My team's daily pain points are around the operational side. Managing device certificates and user onboarding for a large, non-technical sales team is still clunky. Our biggest headache is getting clean logs into our existing SIEM for the security folks—the custom parsing required is a constant project. Yet the last two roadmap webinars focused heavily on adding more third-party IdP integrations (we already use Okta) and a new mobile UI refresh.
So I'm curious what others are seeing. Does their public roadmap align with what's actually slowing your rollouts or complicating your RevOps security policies? Are they prioritizing the deep, granular controls and admin efficiencies that scale, or just checking feature boxes?
For instance, I'd trade three new IdP connectors for one solid, native way to handle just-in-time access requests tied to our Salesforce opportunities. That's a real-world pain point for us. Anyone else feeling this gap between the shiny new features and the gritty, daily admin work?
I feel this so much! We're only a few months into our ZTNA rollout and I'm already worried about the long term admin work, especially with logging. My more experienced colleague keeps saying "the setup is just the first project, the logging and cert management is the permanent one."
Can I ask a follow up? You mentioned
> a new mobile UI refresh
Was that actually something users were asking for? Because we can't get our sales team to reliably use the app as it is, a new interface seems like the last thing we'd need. It makes me wonder if their product team is getting different feedback than what we're experiencing.
That quote from your colleague is painfully accurate. The initial deployment is a sprint everyone rallies behind. The permanent state of managing certificates and normalizing logs across a dozen teams is a marathon nobody signed up for.
As for the mobile UI refresh, it's rarely driven by user demand for enterprise tools. It's usually one of two things: either a marketing checkbox to keep up with competitors who also refreshed theirs, or a development team needing a "clean" project after being buried in legacy certificate code for six months. Shiny new frontend work is always more appealing than fixing gnarly backend telemetry pipelines.
If your sales team isn't using the current app reliably, a new coat of paint won't change that. The underlying workflow and friction points are what matter. You've already spotted the disconnect.
monoliths are not evil