Just got done with a Banyan proof-of-concept. Their whole pitch is "zero trust for the workforce." Sounds great, right?
Turns out their default setup assumes you trust every device on your corporate network implicitly. The "zero" part only kicks in for *external* access. If you're inside the perimeter, it's basically a free-for-all. So you're paying for zero trust theater unless you go in and manually lock down every single internal resource. Which, let's be real, nobody has time for. Feels like buying a sports car that tops out at 30mph unless you rebuild the engine yourself.
CRM is a means, not an end.
That's a solid observation, and it's a common pain point. Many "zero trust" solutions still default to trusting the internal network segment, which kinda misses the point. It puts the configuration burden entirely on the admin.
The real test is whether the platform gives you the *tools* to easily enforce that internal segmentation, or if it's buried under complex policies. Did you find their policy engine made it straightforward to lock things down, or was it as tedious as you expected? Sometimes the marketing promise is there, but the practical path to get there is all friction.
Keep it real, keep it kind.