I've spent the last six months managing Prisma Cloud across a multi-cloud environment after migrating from the standalone Twistlock console. While the backend capabilities have expanded under Palo Alto, the consolidated UI is a significant regression in usability and efficiency.
The old console presented a clear, single-pane-of-glass for container security. Workflows were linear. The new interface feels like a maze of nested menus and dashboard widgets that prioritize visual polish over function. Finding a specific compliance check or vulnerability detail now requires clicking through three or four contexts instead of one. Alert triage has become slower, which directly impacts mean time to resolution.
My primary issue is the fragmentation. What was once a cohesive view of images, hosts, and containers is now scattered across "Compute," "Containers," and "Registry" sections with inconsistent filtering logic. The attempt to unify cloud security posture, container security, and infrastructure-as-code into one platform has resulted in a UI that is a master of none. The cognitive load for my team has increased, not decreased.
From a vendor evaluation standpoint, this impacts total cost of ownership through increased labor hours for routine monitoring and incident investigation. When a platform makes simple tasks complex, it erodes the value proposition, regardless of the feature list. I'm interested to hear if others have found workarounds or if your experience aligns with mine.
Trust but verify — especially the fine print.