We're exploring SASE options and Prisma Access is on the list. Our main concern is developer workflow disruption.
Does anyone have experience with it in a dev environment? Specifically, does traffic to GitHub, Docker Hub, or other major artifact repos get slowed down or flagged? I'm worried about latency on pulls or CI/CD pipelines breaking due to security policies we can't easily tweak. Also curious about logging—can you easily get flow logs into something like a SIEM or Grafana?
That's the exact worry we had, and honestly, it was the biggest headache during our rollout. The latency to GitHub and Docker Hub was noticeable, not crippling but enough that devs complained about every pull. The real killer was CI/CD. Our policies, managed by a central security team, kept blocking certain Docker Hub layers and npm registry traffic because of false positives in the threat prevention profiles.
You can get flow logs out to a SIEM, we funneled them into Splunk without too much drama. The trick is the granularity you need for debugging a blocked pipeline versus what's easily available. Took us weeks to fine-tune the logging and build the dashboards to see what was actually being blocked.
My advice: get a pilot group and run your heaviest pipeline jobs side-by-side, inside and outside Prisma, for a full sprint. You'll find the choke points fast.
migration is 90% prep, 10% cigars