Skip to content
Notifications
Clear all

Switched from Prisma Access to pure cloud-native Zero Trust. 300% more work.

4 Posts
4 Users
0 Reactions
63 Views
(@martech_tester)
Trusted Member
Joined: 7 months ago
Posts: 32
Topic starter   [#392]

Just switched our remote team from Prisma Access to a pure cloud-native Zero Trust setup. Big mistake. 😅

Prisma had everything in one pane – policies, user groups, app visibility. Now we're juggling 3 different consoles just to replicate the same security posture. Setting up a new app? Used to be one policy update. Now it's config in the ZTNA gateway, then IdP rules, then network segment mapping. Feels like 300% more manual work.

Anyone else made this move? Is there a trick to streamlining it, or do you just accept the extra overhead for the "cloud-native" flexibility? Curious if we missed a workflow.



   
Quote
(@tool_skeptic_45)
Eminent Member
Joined: 9 months ago
Posts: 14
 

I run infra for a 150-person fintech. We've had Prisma Access in production for 3 years, then also ran a parallel ZTNA pilot (using Cloudflare Zero Trust) for a specific app.

* **Fit:** Prisma is a complete, monolithic stack for an SMB/mid-market IT team that wants one throat to choke. Cloud-native ZT is for engineering-heavy shops that want to integrate best-of-breed components.
* **Real Pricing:** Prisma is $180-220/user/year, all-in. Our ZTNA pilot stack was $9/user/mo (ZTNA gateway) + $6/user/mo (advanced IdP) = ~$180/user/year for just those parts, before any network or SWG costs.
* **Deployment Effort:** Prisma's initial policy setup took us 2 weeks. The ZTNA pilot to cover one app took 3 days because of API config, service token rotation, and debugging IdP group passthrough.
* **The Breakage Point:** Prisma's SWG and TLS decryption is a checkbox. Doing this cloud-native requires managing your own forward proxy fleet or buying another service. We hit a 40% latency increase for AU users because the ZTNA gateway region selection was wrong - a config issue we had to fix ourselves.

If you can't dedicate a full-time network engineer to manage the distributed config, go back to Prisma. If you need fine-grained, API-driven control for a dev-heavy environment and have the headcount, cloud-native can work. Tell us your team size and how many apps are "internal".



   
ReplyQuote
(@test_harm)
Active Member
Joined: 6 months ago
Posts: 10
 

Yep, that's the trade-off you signed up for. Cloud-native means assembling the pieces yourself. No single pane because you're not buying a single product.

If you're not using IaC for those three consoles, you're doing it wrong. The manual config overhead is a choice. Script the IdP rules and gateway updates together. Still more work than Prisma though.


If it's not flaky, is it even tested?


   
ReplyQuote
(@Anonymous 83)
Joined: 4 months ago
Posts: 9
 

Welcome to the open buffet after years of the prix fixe menu. You traded convenience for control.

You didn't miss a workflow. You're now doing the integration work Palo Alto's engineers baked into Prisma. That's the hidden labor cost they bundle into their per-user fee.

The 300% extra work is the real price tag. Now weigh if the flexibility is worth that permanent ops tax.



   
ReplyQuote