What is our primary use case?
We use the solution to monitor and manage our various cloud environments, providing complete visibility in a single platform. We also use it for configuration, network, and anomaly monitoring. On the compute side, that's for containers and Kubernetes, so we know when changes are made and whether those changes are approved or within our required security controls.
The platform has yet to become part of our CICD pipeline; we mostly use it as a security tool for monitoring and remediation.
Regarding modules, we use the CSP and the compute module.
How has it helped my organization?
Prisma Cloud helps us take a preventative approach to cloud security. It raises awareness of particular threats. Although it's a reactive type platform in that alerts happen on events that have already occurred, it allows us to take a step back and consider our cloud infrastructure more thoroughly. In this sense, the solution enables us to maintain our posture and current programs.
The product reduced our runtime alerts by approximately 25%.
What is most valuable?
Configuration monitoring and alerting is the most valuable feature; it happens at the cloud's speed, allowing our development team to respond quickly. If a configuration goes against our security best practices, we're alerted promptly and can act to resolve the issue. As cloud security staff, we're not staring at the cloud all the time, and we want to let the developers do their jobs so that our company is protected and work is proceeding within our security controls.
The product provides efficient and comprehensive protection for the full cloud-native stack. It presents its findings in layman's terms; alerts are pretty straightforward as to what's going on and why, whether a configuration needs to be changed, and recommendations on how to remediate.
We used the solution's security automation capabilities, so in the event of an alert, it can be resolved with the click of a button; we click remediate, and the configuration is changed to the recommended status, which is very helpful. However, we use automation sparingly, as we usually have to coordinate changes in the cloud with development teams or through change control. Our typical usage is for completely forbidden scenarios, such as publicly accessible storage containers. We fix that by clicking remediate, then follow up with the team to determine if that was intentional. Sometimes, although accurate, the recommendation may break something else if there is a compensating control in place. So, automation is helpful but not overly used.
For the most part, the tool provides the visibility and control we need, regardless of how complex and distributed our cloud environments become. Sometimes the platform can be a little kludgy, but we can usually click around and figure it out. Regarding confidence in our security and compliance postures, I don't know how anyone could have a cloud presence without some form of CSP, and I'm delighted with Prisma.
The solution provides risk clarity at runtime and across the entire pipeline, showing issues as they are discovered during the build phases. However, we still need to utilize this feature to 100%.
What needs improvement?
The UI could use some improvement; we usually find the information we're looking for, but what fields can be clicked on and what workflow to follow to get the required information is not always evident. Sometimes we're all over the place, clicking around to drill in and uncover the alert and investigation details we're looking for.
For how long have I used the solution?
We've been using the solution almost continuously for around five years.
What do I think about the stability of the solution?
Prisma Cloud is pretty stable; it's a great product, and I'm happy with it.
What do I think about the scalability of the solution?
The platform constantly evolves regarding new features and functions, which can sometimes be a little overwhelming, but it's very scalable. It's just a matter of familiarizing myself with those functions and features. It's the type of tool that is constantly improving, and its scalability suits our environment well.
How are customer service and support?
The customer support is excellent and helped a lot during the deployment process. I rate them nine out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I demoed other solutions but never actually used or implemented one before Prisma.
How was the initial setup?
The initial setup is pretty straightforward, though some of the documentation is convoluted. The support is good, though, so getting someone on the phone or an engineer to respond via email or meeting is easy. The setup was straightforward, and the support was excellent. If I had the permissions to set up the cloud-side integrations, it would have taken a day, but I had to rely on the availability of other staff members, so it took about a week.
What was our ROI?
The platform is relatively new and expensive, so it's hard to put a number on it. However, the amount of man-hours saved by it easily uncovering some of the flaws in our security posture means it definitely saved us money.
What's my experience with pricing, setup cost, and licensing?
The product is very expensive, but the cost is a necessary evil; I don't know how we could have any kind of cloud presence without this type of monitoring. The pricing is calculated by module and resource usage. Ultimately, it saves us money in the amount of time we would spend uncovering what it uncovers, and we might not make the required discoveries without it anyway. Prisma offers incredible value, though I wish it were cheaper.
People argue that there are native tools within the various cloud environments, but nothing that streamlines from a timing and comprehension perspective for small security teams. If you don't have a dedicated team of 20 staff, Prisma is the tool you need. I don't know any company that does what they do or how they do it.
Native tools may uncover a misconfiguration, but for a multi-cloud environment, you have to be proficient with multiple different tools, none of which tells the whole story. Prisma pulls in all the data and gives you everything you need to know in one platform. It also pulls in extra data, including network traffic, anomaly traffic, configuration data, and vulnerability data, so you can correlate that information and make an educated decision as to what's going on in the environment, and what needs to be changed or addressed.
Which other solutions did I evaluate?
I evaluated Lacework, Sysdig Secure, and Illumio Zero Trust Segmentation, though I see them more as Veracode than CSP competitors. I didn't find any products that compare to what Prisma Cloud does.
What other advice do I have?
I rate the product nine out of ten.
My advice to those before implementing the platform is to do the integration yourself if you have the time, are IT savvy, and have the necessary permissions. It only requires a little time, a few days to a week at most, and there is great value in doing the integration yourself rather than paying for their support to do it. Onboarding the solution will provide an understanding of how it communicates with the cloud environment, how roles are associated and created, and how the remediate feature functions. It's important to go through those steps rather than paying someone else to do it; you'll save money and understand how the tool does what it does, which is essential in utilizing it.
Regarding the solution securing the entire cloud-native development lifecycle across build, deploy, and run, we have yet to use it that way, not to say that we won't. This feature is a relatively new part of Palo Alto's CICD deployment, so we haven't used it yet.
Prisma Cloud provides a single tool to protect all our cloud resources and applications, without managing and reconciling disparate security and compliance reports to about 70%. However, we have yet to utilize the tool to its full capacity.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.