Skip to content
Notifications
Clear all

Rolled out Prisma Access to 500 users globally - what actually broke first

1 Posts
1 Users
0 Reactions
1 Views
(@devops_rookie_22)
Reputable Member
Joined: 4 months ago
Posts: 158
Topic starter   [#21461]

Hey everyone. Still pretty new to the DevOps side of things, so please bear with me.

We just finished rolling out Prisma Access to replace our old VPN setup. About 500 users across a dozen offices. I was excited about the promised security and all-in-one management.

But, of course, something broke. And it wasn't the fancy zero-trust stuff. The first real problem? Legacy internal web apps that used hard-coded IP addresses for backend calls. Prisma Access broke the direct path. Suddenly, "server not found" errors everywhere for a handful of critical apps.

We had to scramble to get DNS updated properly for those internal services. Kind of a basic thing, but it really highlighted how much legacy stuff assumes a certain network topology. Has anyone else hit this? What was your "first break"?



   
Quote