Prisma Cloud by Palo Alto Networks Reviews

I am a cloud security architect. I assess the cloud infrastructure for customers and help implement security control. I use Prisma Cloud for assessment. After we have the visibility, we deploy security controls, such as perimeter firewall control, proxy control, and endpoint security control.

We have purchased the enterprise license that provides all the capabilities such as CSPM, CWP, and DSPM.

Prisma Cloud provides security spanning multi- and hybrid-cloud environments with Azure, GCP, and AWS clouds. It provides comprehensive security for all these CSPs.

By default, Prisma Cloud supports integration with ServiceNow and Remedy. There are a few more default integrations. Cortex is their own native solution, but in terms of overall automation, Prisma Cloud supports a lot of integrations. It is very helpful for organizations to be able to automate these daily tasks. Different organizations use different security tools. A few of them are directly integrated with Prisma Cloud and a few of them are not. However, most organizations use solutions like Remedy and ServiceNow, so these direct integrations are very helpful. They can save about 70% of the time.

Prisma Cloud provides comprehensive visibility into cloud-based resources. Most organizations are shifting their workloads from on-prem to the cloud. Nowadays, everyone is using the cloud infrastructure, and it is a very big challenge for every organization because, without a CNAPP solution, they do not have much visibility into their cloud resources. CNAPP solutions like Prisma Cloud provide visibility into any misconfigurations, threats, or anomalies. They are very good for code-to-cloud visibility.

Prisma Cloud provides code-to-cloud visibility for the application development cycle of an organization. Some organizations use SAST and some organizations use DAST. Prisma Cloud is a combination of both. You can integrate your GitHub or your IDE environment with Prisma Cloud. You can have a view of the vulnerabilities inside your IAC or application code. You also can integrate it with CI/CD. It is very comprehensive. Not many can leverage the complete benefit of Prisma Cloud. In my last organization, we only used it for runtime protection. We did not use it for CI/CD or code and build. In my current organization, we are using it end to end. It is a good tool. We have the complete capability. The first stage is code and build. The second stage is deployment, and the third stage is run time. It provides complete development life cycle protection.

The time to value is usually immediate. At times, the deployment can take some time, but as soon as the deployment is complete, you get the findings.

The visibility and control Prisma Cloud provides completely align with the customers' needs. At times, we have to create some custom policies. It is completely compatible with the needs of the customers.

It provides end-to-end visibility from development to deployment to production. It prevents the development teams from pushing vulnerable code to production. A lot of things can be prioritized and resolved before deployment. By fixing things beforehand, you save a lot of effort or workload later.

Prisma Cloud's findings help us to create policies. In our organization, the vulnerability reports go to the network team or cloud infrastructure team. They analyze the alerts and create organization-level policies. For example, if there is an instance that is using a public IP, based on that incident, they would create a policy at the org level so that in the future, no one assigns any public IP to an instance. It helps them to create better policies.

Different modules are valuable for different customers. We are leveraging CSPM. It is one of the best solutions for comprehensive visibility into cloud resource configurations and compliance. It has a lot of out-of-the-box policies, and the visibility that we are getting is impressive.

The DSPM module is valuable. This is the latest one that Palo Alto procured from Dig Security. No competitor provides this functionality in a single pane of glass. The support for Linux and container security is also very good. That is the beauty of Prisma Cloud. However, in terms of Windows security, Prisma Cloud is lacking because currently, there is no runtime protection available.

The UI is very good. We get all the things within a single UI. It is easy to use. A new user can easily understand it. It is very user-friendly.

It does not provide runtime security or protection for Windows Server. It is currently lacking in terms of Windows environment. They are integrating their Cortex solution with Prisma Cloud. Once they have a unified agent, I am sure that these challenges will go away.

DSPM is a bit limited in terms of data security and storage capabilities. It only supports a few databases or storage accounts. There is still a long list of services that they need to support.

I have been using Prisma Cloud for four years.

I would rate it an eight out of ten for stability.

It is working smoothly. There is no issue. Scalability also depends on the environment. It depends on how much credit you have purchased. If you go beyond that, they notify you. They will not allow you to onboard more accounts. It totally depends upon the credits that you have purchased, so scalability within the credit limit is good. It is 100%.

We have about 40 to 50 people using this solution.

Their support is average. It is not too good and not too bad. For about 50% of the cases, they have to reach out to their engineering team. The engineering team takes a couple of days or weeks to revert. They are usually unable to provide support without the involvement of the engineering team.

Neutral

I have worked with CrowdStrike's CNAPP solution and Aqua Security. Prisma Cloud is the best in my opinion. It is a market leader. 

Prisma Cloud has more than 100 compliances built in. It supports almost all the services inside the CSPs, whereas other CNAPP solutions only support a few of the services or most commonly used services such as compute, databases, or networks. Prisma Cloud supports maximum services from the CSP side and more than 100 compliances. It has the capability of RQL, so you can create custom queries and get the required data.

It is very easy if you have an understanding of the solution. If you are new to this field, you can face challenges during implementation. Without proper knowledge of the roles, IAMs, and infrastructure, you will face some challenges during the deployment.

I can deploy it within an hour, but before that, we have to fulfill some prerequisites. We have to create a role for Prisma Cloud. We have to create a service credential. Every organization has its own procedure. They might take a day or a week to create the required service credential and assign necessary permissions to that. Once we have all the prerequisites, within an hour, we can deploy it. After the deployment, it starts providing visibility. It takes approximately 24 hours.

Our environment is hybrid. We are using AWS, Azure, and GCP. We also have an on-prem environment for which we have deployed Defender for CWP capability. Prisma Cloud provides us with cloud-native security and visibility.

They are regularly implementing new features in Prisma Cloud. They are doing regular updates in the backend, and they keep us informed. Mostly, they are performing these kinds of activities at night so that there is minimal impact.

Maintenance-wise, there is not much. Everything runs smoothly. They take the feature requests and notify us when they implement those requests. They are regularly changing and updating it.

I do not have any metrics for cost savings, but it certainly helps with security and compliance. The visibility it provides helps to fix any vulnerabilities. A data or security breach can cost an organization a lot in terms of money and reputation.

Prisma Cloud provides visibility into vulnerabilities, but it is an organization's responsibility to fix those vulnerabilities. Prisma Cloud only provides visibility. It is only an assessment tool. The team has to fix those vulnerabilities. The time taken to fix the vulnerabilities varies because different teams work on it. 

I have not explored all CNAPP solutions. Overall, I would rate Prisma Cloud an eight out of ten.

We currently leverage Prisma Cloud's Cloud Security Posture Management and Cloud Workload Protection Platform modules and plan to migrate to their full Cloud Native Application Protection Platform solution for a more holistic security approach.

Our security system uses three major CSPMs, ingesting logs and integrating them with a central CSPM page for visibility. We also incorporate identity and document management systems. Prisma Cloud's detection tool based on its policies provides initial alerts, with our SOC team focusing on the most relevant ones. We leverage a modified threat framework combining NTSF and MITRE to monitor key policy areas like malware, unauthorized access, phishing, data loss, and system failures. Within Prisma, we categorize policies based on our organization's priorities, using custom tags to identify them and create dashboards. Webhooks then send these alerts to our SIEM platform for further analysis.

Prisma Cloud offers security spanning across multi-cloud and hybrid cloud deployments, supporting industry leaders like Google Cloud Platform, Microsoft Azure, Amazon Web Services, Alibaba Cloud, and Oracle Cloud.

Prisma Cloud simplifies compliance with regulations, a crucial security aspect for large organizations, by providing full visibility into our cloud environments. This eliminates the time-consuming need to manually check configurations within each cloud service provider. With Prisma Cloud's single pane of glass view, everything can be done in one place, saving us an average of 15-20 percent of the time compared to the previous method of having a dedicated person manage each CSP individually.

Automation streamlines report delivery and notification generation. It can also integrate with various third-party services like Slack, Jira, Microsoft Teams, and Microsoft Sentinel, allowing for further automated notifications and actions within those platforms.

Our cloud visibility was limited before Prisma Cloud. Now, we have a good level of insight, not perfect, but significantly improved. We can monitor new deployments, configurations, and overall activity. This is crucial because most organizations, like ours, are increasingly cloud-based. Stricter regulations require compliance, and Prisma Cloud simplifies this. They offer pre-built compliance standards so we can easily generate reports, ensuring we meet our obligations.

While Prisma Cloud delivered as promised, realizing its full benefits in our large organization took several months. Due to the size and complexity of our internal communication and collaboration structures, it naturally took time for everyone to fully understand and adopt the platform's capabilities.

Prisma Cloud offers timely runtime alerts when properly configured. These alerts integrate well with our SIEM and are easy to understand. However, the majority stem from the CSPM module, as CWPP typically necessitates manual investigation for actionable insights. Prisma Cloud has reduced the runtime alerts by 20 percent.

Our initial Prisma Cloud deployment has already delivered a 5 percent cost saving, and we expect these savings to grow as we expand its use across our cloud environment.

Our primary focus right now is compliance. This means having clear visibility into our organization's security posture. Additionally, agentless scanning with Prisma Cloud is important for us. While we're also interested in the Cloud Workload Protection Platform, it's important to consider that our environment includes both containers and virtual machines. Overall, the most valuable features for us in Prisma Cloud are those that provide visibility, ensure compliance with regulations, and help us align our on-premises servers and cloud environments with mandated security standards.

Prisma Cloud stands out as a user-friendly and powerful CSPM solution thanks to its comprehensive capabilities, built-in features, and flexible tagging system. It simplifies cloud security by automatically connecting to numerous cloud service providers and pulling relevant information for our use, minimizing the need for manual configuration and troubleshooting.

Prisma Cloud's preventative approach to cloud security can be complex, especially for features like automated certificates. These require specific access permissions for Prisma Cloud, introducing dependencies and additional configuration steps.

While Prisma Cloud offers agent-based deployment for comprehensive visibility and control, agent dependencies and user resistance can create hurdles. Improved agentless scanning capabilities from Prisma Cloud would be ideal, but currently, agents remain necessary for optimal visibility.

Prisma Cloud is a powerful security platform, but like any similar tool, it won't eliminate the need for occasional manual interaction with our CSPs. While Prisma Cloud can handle many tasks, some actions might still require us to log directly into our CSP account.

The CSP logs could be improved by providing more visibility into the specific logs Prisma is feeding. Since CSP has multiple versions and Prisma might be receiving different logs than expected, it would be helpful to have a clearer indication of the log types or more detailed logs themselves. This would allow us to verify if we're receiving everything or missing something. While Prisma Cloud offers log searching, it requires queries to navigate the vast amount of data. Ideally, Prisma could integrate a simpler way to view the logs it's collecting without extensive searching.

Some module customization might be needed and certain features like adding custom labels are currently unavailable unless we have administrator access. This limitation can be frustrating and I would like to have this functionality included in Prisma Cloud.

I have been using Prisma Cloud for two years.

I would rate the stability of Prisma Cloud seven out of ten. Occasionally when we have an issue it can take some time to resolve.

I would rate the scalability of Prisma Cloud nine out of ten.

We have a dedicated account manager who provides support whenever needed. While they're always responsive, responses may occasionally take some time.

Positive

Despite being a cloud-based solution designed for easy deployment, Prisma Cloud's initial setup took a few months due to our team's workload on other projects. Fortunately, only two people were required for the actual deployment process, which itself is straightforward as long as the necessary network connectivity is established beforehand.

Prisma Cloud's licensing system functions as expected with a solid licensing infrastructure.

In our evaluation of Wiz and Aqua Cloud Security Platform, we investigated their capabilities to address detection rule limitations in Prisma Cloud CSPM. We were hoping to find alternative solutions offering broader rejection capabilities. However, both Wiz and Aqua require agents for in-depth details, similar to Prisma Cloud. While neither excelled in overall detection capabilities, Wiz impressed us with its integration of external alerts. Unlike Prisma Cloud, Wiz allows for easy visibility and filtering of alerts from AWS Guard Duty, a significant advantage.

I would rate Prisma Cloud by Palo Alto Networks eight out of ten.

Prisma Cloud offers built-in security automation for tasks like remediating misconfigurations. For instance, it can automatically adjust a non-compliant AWS configuration, but only if you grant the necessary permissions. While this is useful, a SOAR solution like XSOAR can provide a fuller approach to security automation.

Over 50 people in multiple departments within our organization USE.

Prisma Cloud required minor maintenance for platform updates and policy changes that need to be reviewed.

While many Cloud Security Posture Management tools offer similar features, consider your budget before choosing Prisma Cloud. Some CSPMs bundle all functionalities into one package, forcing you to pay for everything even if you don't need it. Prisma Cloud, on the other hand, allows you to purchase only the modules relevant to your organization's needs. Additionally, Palo Alto is a well-established vendor in the market.

We use the compliance and vulnerability management modules. We are a bank and have certain controls in place. My business unit is cloud-only, and we need to enforce controls, and for audit purposes, we need to collect evidence of control enforcement. We have a number of controls around cloud resources. We configure Prisma to enforce those controls pretty automatically. Prisma generates evidence of the controls that we can present to auditors when we are audited. If we didn't solve this problem, we could lose our license.

It's hard for me to say how Prisma has improved our organization because it was implemented before I joined. But given the number of security controls that have been automated with Prisma, we have managed to achieve a fair amount of manual cost reduction for our control testers. And the automation and integration capabilities of Prisma have allowed us to save a lot of engineer time on evidence. Without Prisma, we would have to do all these things manually. Overall, it results in a huge FTE reduction.

With the number of controls that need to be tested, we would be talking about a team of around 100 people. With the Australian salaries, Prisma is probably saving us $1,000,000 to $2,000,000 a year.

The framework to configure controls is pretty good; it's pretty sophisticated. We can implement a fair amount of testing for a fair number of controls.

It's vulnerability management is quite good, and its integration functionality is something that we have found to be pretty capable.

We also use Twistlock for container security, which is good.

And Prisma Cloud's security automation capabilities are quite good. We use the periodic scanners, and we feed Prisma filings into our control evidence management system. They tick all the boxes for us.

One thing that is missing is Cloud Run runtime security—serverless. That would be great to have in the tool. It's not that easy to have Cloud Run in specific environments.

We have also found that Google Security Command Center has a little bit better coverage for GCP because it's native. That's why we pay for both tools. But ideally, we should only need one tool. Prisma Cloud's coverage of GCP is okay, but a little better coverage would be better.

Our cloud environment is complex, and Prisma doesn't cover all aspects of it. We don't rely on Prisma for any kind of security discovery. We just rely on it as a control-test and automation tool.

We get a few alerts in Prisma, and it allows us to trace any violations back to the source. It's a pretty straightforward interface.

Another thing that we have found useful with Prisma is its Jira integration. When our integration finds a new alert, it creates a ticket in Jira, so it's fully visible and tracked, appearing in all the dashboards.

I joined this branch of the bank six months ago, and Prisma is my portfolio now.

It's stable enough. I can't remember any outages of Prisma Cloud.

It's a SaaS service and is licensed both for our team and for the enterprise. On our side, there are 1,000-plus user licenses. We have five or six integration points, so in that regard, it's not humongous.

We are growing extremely quickly, and Prisma Cloud provides all the required services without any need for us to do anything to scale. It's pretty elastic. We'll probably grow by 10 times in the next couple of years. So far, I don't have any doubts that Prisma will support us.

I've never dealt with their technical support. Prisma Cloud just works.

Our bank itself is huge and uses all sorts of solutions. My business unit is quite young, it's only three years old, and I don't think there were any solutions in this space.

Deploying it was pretty straightforward compared to other tools. We implemented a fair number of compliance rules pretty quickly. I recently participated in some integration activities, and integration-wise, it was very straightforward.

As for maintenance on our side, there really isn't any. We periodically need to review the controls being tested and the control automation, to make sure that they're aligned with changes in the controls. Other than that, it's pretty maintenance-free.

We have managed to save a fair amount of money and effort in hiring manual testers. That's what automation does for us.

I wouldn't mind if it were cheaper. We are spending a fair amount of money on Prisma Cloud. It's probably okay, but, funnily enough, banks don't have money. Periodically, we have cycles of cost-cutting, so if we could save on Prisma Cloud, that would be great.

We don't use Prisma for build and deploy, we use another set of tools. Right now, we are doing our internal due diligence to figure out if we can replace all of those with a single tool, whether it's Prisma or any other tool. We don't know at the moment.

It's very hard to attribute any kind of runtime alert reduction to Prisma Cloud as we use a whole zoo of tools. Prisma is just one piece of the puzzle. We don't have too many runtime alerts thanks to the joint work between our build tools, deployment prevention security tools, and Prisma.

While it's a good tool, you need to be mindful of serverless because serverless runtime security is tricky and, unfortunately, Prisma doesn't do too much there. Other than that, it's a good tool.

Prisma Cloud by Palo Alto Networks is a comprehensive cloud security platform that encompasses vulnerability management, container management, Kubernetes management, and serverless management. It utilizes modules, such as Cloud Workload Protection, to provide comprehensive cloud security. Before deploying any applications, Prisma Cloud performs cloud scans to identify and address vulnerabilities, minimizing potential threats. The solution provides visibility into our cloud environment, enabling us to effectively manage and monitor our infrastructure. This capability is particularly valuable in the financial industry, where hybrid multi-cloud environments are prevalent.

We use all the modules Prisma Cloud offers.

Prisma Cloud offers security scanning for multi-cloud and hybrid cloud environments. This is crucial because managing multiple cloud accounts, such as AWS, GCP, and Azure, typically necessitates accessing each account individually to view the inventories of assets and services. Prisma Cloud eliminates this inconvenience by consolidating all of this information into a single unified interface, providing a comprehensive overview.

The comprehensiveness enhances threat protection by providing integrated and out-of-the-box policies, along with all the necessary components, to effectively secure cloud environments and achieve comprehensive visibility through Prisma's capabilities.

The security automation capabilities of Prisma Cloud are effective. We can automatically remediate some of the alerts using predefined policies. We utilize Defender to detect vulnerabilities in our containers, AKS, and GKE environments.

Prisma Cloud has benefited our organization in so many ways that we can't count them all on our fingers. The Cloud Security Posture Management module of Prisma provides a wide range of capabilities, including visibility, governance, compliance, auto-remediation, integration with hybrid cloud environments, vulnerability reporting, and blocking capabilities. It also offers compliance reports, integration with third-party tools for vulnerability and alert notifications, and Cloud Workload Protection capabilities for blocking, alerting, and specifying affected containers or servers. Additionally, it provides visibility into code security by monitoring the Infrastructure as a Code environment for unauthorized users.

It enables a proactive approach to cloud security, allowing us to prevent vulnerabilities, threats, and complications arising in cloud or hybrid cloud environments. We can easily investigate and obtain comprehensive reports.

We spent the first five months after implementing Prisma Cloud familiarizing ourselves with the solution and completing the training sessions provided by Palo Alto. During this time, we began to see the benefits that Prisma Cloud offered our organization.

Prisma Cloud works with the CIB. Therefore, when we build and deploy something, we can incorporate a Prisma scan, which assists us in scanning the images and gaining insights into the state of our environment. It provides us with comprehensive visibility and raises alerts or triggers notifications to inform us of any missing elements or potential issues. This is how Prisma can contribute to the build and deploy phases.

It provides deep visibility and control regardless of how complex our cloud environment becomes.

Prisma Cloud enables us to integrate security into our CI/CD pipeline and it provides us with a single tool to protect all of our cloud resources.

Prisma Cloud provides run-time risk clarity throughout the entire pipeline, revealing issues as they arise. This enables us to effectively block vulnerabilities and rectify identified problems.

We have reduced run-time alerts. The run-time protection has helped many of our clients protect their environments.

Prisma Cloud has significantly reduced our investigation time. The clear visibility it provides into our environment and the process flow has streamlined our investigations. Additionally, using Prisma to investigate issues rather than directly accessing our cloud accounts saves valuable time.

The most valuable features of Prisma Cloud are its cloud security posture management and cloud workload protection capabilities. Integrating Prisma Cloud with our cloud service providers provides a comprehensive view of our multiple cloud environments through a single dashboard. This enhanced visibility improves vulnerability management and compliance. With CWP, we can gain complete visibility into all workloads within our environment.

We are encountering issues with the new permissions required for AWS integration with Prisma. Specifically, we need a mechanism to automatically identify and integrate the missing configuration permissions that are introduced on a biweekly or monthly basis. We have requested the Palo Alto team to develop this automation, and we are eagerly awaiting its implementation. We appreciate the efforts of the engineering team for their contributions.

I have been using Prisma Cloud by Palo Alto Networks for two years.

Prisma Cloud is a stable platform. The only downtime we experience is scheduled, and Palo Alto notifies us in advance of the scheduled outage and its duration.

I would rate the scalability of Prisma Cloud a nine out of ten. I have received positive feedback from our clients indicating that Prisma Cloud is an excellent fit for their environment.

We have repeatedly contacted technical support to address issues encountered by both ourselves and our clients. The support is helpful.

Positive

We previously used AWS GuardDuty for vulnerability management and compliance visibility, but it was not user-friendly due to the requirement to log into separate accounts to access reports.

When I first started using Prisma, I found it to be very easy to learn. Several of our engineers were already familiar with Prisma Cloud and were able to help me understand how it worked, including the UI, navigation, and integration with other tools. They also showed me how to make API calls and integrate Prisma with third-party tools. Additionally, the Prisma team was incredibly helpful whenever I contacted them for assistance. They were always willing to answer my questions and help me troubleshoot any issues I was having.

I completed the implementation myself after completing the training sessions with the Palo Alto team and attending a lab session for the Prisma Cloud deployment.

I don't have direct access to financial information, so I'm not fully aware of the overall costs. However, I do work with clients and solution teams to provide relevant solutions. I also collaborate with the research team to explain Prisma's capabilities and its comprehensive range of features. When I see the credits and other similar programs may make Prisma's licensing costs appear lower than those of competing tools, it's important to consider the overall cost when evaluating cloud security solutions. For example, when implementing cloud security measures for CSPs or CWPs, other tools may be required, potentially leading to higher overall costs than Prisma Cloud's comprehensive solution.

I would rate Prisma Cloud by Palo Alto Networks nine out of ten.

Prisma Cloud necessitates maintenance for both weekly and monthly updates.

My advice to new users and researchers is to delve into Prisma Cloud's capabilities and potential. Understanding the full scope of what it can do is crucial for new users. It's not just about visibility or the GUI; it's about the underlying work that engineers do, such as runtime protection, virus detection, and code security. New users should have a clear understanding of these capabilities. They should participate in sessions, practices, and labs to gain hands-on experience.

I use Prisma Cloud for one of my clients to provide Cloud Workload Protection Platform, Cloud Security Posture Management, and Identity and User Controls services.

Prisma Cloud is the tool of choice for my client's container security and infrastructure-as-code security, including cloud security posture management.

We implemented Prisma Cloud primarily for its code-to-cloud feature. Recognizing the industry's emphasis on automated resource deployment, we developed a Terraform script to deploy resources on the Azure platform. We aim to maintain full security monitoring from the initial code to the cloud environment. By proactively identifying and addressing high-critical vulnerabilities in container images during the build process and enforcing compliance standards within Terraform scripts through policy-driven pipelines, Prisma Cloud helps us mitigate risks and ensure the security of our cloud infrastructure.

Prisma Cloud offers full integration with all major cloud platforms, making it a versatile choice for multi-cloud environments. I've successfully implemented it for both GCP and Azure, which provides consistent security coverage across both platforms. Its streamlined onboarding process for subscription or tenant-level agentless scanning and discovery is highly efficient. The platform's cloud discovery feature also offers valuable, cost-free, enhanced data for robust reporting. This, combined with informative labels, simplifies report generation at the product level, especially in organizations utilizing microservices and namespaces for application management. These capabilities make Prisma Cloud a vital asset for managing complex cloud infrastructures.

Prisma Cloud seamlessly integrates with popular DevOps tools like GitHub and Azure DevOps, which we commonly use for our clients. Automation is straightforward: incorporate a block into your workflow or pipeline to initiate scanning and other processes. Additionally, cloud account onboarding requires only adding a service as a key. This streamlined approach facilitates automated security guardrail implementation, eliminating the need for manual vulnerability remediation. Instead, scans are run directly within the pipeline, and critical vulnerabilities are flagged for immediate attention, enhancing overall security efficiency.

Shifting security left by ensuring only sanitized images are pushed to production for container use requires a dedicated team for twelve months to address all image vulnerabilities. Prisma Cloud automation significantly accelerates this process by remediating vulnerabilities automatically.

Prisma Cloud enhances visibility for our clients, enabling them to adopt a zero-trust model with monitoring at all entry and exit points. This full approach, coupled with a robust SOAR solution, effectively manages alerts from various tools and facilitates timely remediation efforts. The platform seamlessly integrates cloud security, application security, and threat detection, providing our client a unified view of their security posture.

Prisma Cloud offers comprehensive security across the entire cloud-native development lifecycle, covering all stages from code creation to cloud deployment, including the build, run, and deploy phases. Essentially, it provides security protection for every critical step within the development and production process.

Prisma Cloud offers a consolidated tool for cloud security, effectively covering CSPM, CNAP, CWPP, and ISE components. While their AppSec capabilities are still under development, I anticipate a comprehensive solution in the near future. Although Prisma Cloud is a strong standalone option, integrating a SOAR tool from another provider might be necessary for a truly end-to-end solution.

Prisma Cloud has proven effective in reducing runtime alerts by up to 20 percent, a significant benefit for our clients. While they are still verifying our adherence to proper procedures for this new solution, it's worth noting that Prisma Cloud offers a comprehensive set of policies, including those for detecting crypto mining and other threats.

Prisma Cloud is currently the market leader in runtime protection, enhanced by its ownership of Syslog and seamless integration. Its exceptional container security capabilities and an unmatched ability to address the MITRE ATT&CK framework distinguish it from other tools. This full suite of features positions Prisma Cloud as the optimal solution for our needs.

Prisma Cloud offers robust runtime scanning capabilities, which is beneficial for security teams. However, deploying additional security tools within existing infrastructure can be challenging due to resource consumption, potentially leading to application performance issues. Prisma Cloud's advantage lies in its minimal resource usage as it runs from ports, making it easier to convince stakeholders to implement runtime security measures and ensure ongoing application protection in production environments.

Prisma Cloud's security auditing capabilities are under development. Enterprise reporting could be improved, as the current data is insufficient for developers' needs, resulting in excessive noise. The platform currently lacks status information for deferred image vulnerabilities, such as specifying the version of an image vulnerability in reports. This functionality is being developed. Additionally, separating OS-level and application-level vulnerabilities is necessary to accommodate organizations focusing solely on cloud security. Prisma Cloud is already working on this feature.

Prisma Cloud's enterprise reporting needs significant improvement. We have already discussed this issue with them. The current reports are excessively noisy, making it impractical for developers to address the vast number of reported vulnerabilities. To streamline the process, we require a clear distinction between vulnerabilities originating from the application and those stemming from base images. While developers should address application vulnerabilities, base image issues necessitate using third-party base images and regular updates. Many organizations already have dedicated application security tools, so duplicating efforts is undesirable. A self-service portal allowing developers to onboard their own repositories would alleviate the need for admin intervention. Additionally, Prisma Cloud should provide a mechanism to defer vulnerabilities without known fixes, improving report clarity.

I have been using Prisma Cloud by Palo Alto Networks for two and a half years.

I would rate the stability of Prisma Cloud seven out of ten. It has room for improvement.

Prisma Cloud is scalable. I would rate the scalability eight out of ten.

The technical support is good.

Positive

All Prisma Cloud deployments are straightforward due to the comprehensive and improved documentation. Following the steps outlined, the tenant can be onboarded, and scanning can be initiated within approximately two days.

Prisma Cloud is cost-efficient, but the credits are on the higher end.

Prisma Cloud is the market leader in container security. While Microsoft Defender for Cloud also offers container security features, our comparison of Wiz, Defender for Cloud, and Prisma Cloud revealed that Wiz lacks enforcement capabilities, preventing us from blocking or denying actions. Additionally, Defender for Cloud's pricing model, based on virtual CPUs, becomes prohibitively expensive for container clusters, which often have thousands of them. Prisma Cloud's cost-effective, credit-based pricing and robust enforcement capabilities make it the right choice for our needs.

I would rate Prisma Cloud by Palo Alto Networks seven out of ten.

I would not consider time to remediate a capability as it's dependent on the resource owner's actions. The alert will remain unresolved until they address the misconfiguration on machines X, Y, or Z. This is not solely a tool limitation; At the same time, full auto-remediation is an organizational goal, often hindered by specific needs and customizations. Consequently, without complete auto-remediation, achieving desired service-level agreements is challenging.

Our client is a medium retail enterprise business.

We use it to manage multiple AWS accounts within our platform. Our primary focus is on ensuring compliance across all accounts, aligning with specific standards such as GDPR. We conduct regular certifications of AWS accounts to assess the compliance of services and promptly address any non-compliance issues. In cases where services are found to be non-compliant, we notify the responsible teams and work collaboratively to remediate the identified alerts. In addition to code security, we also use Prisma Cloud to protect our workloads, including serverless functions and containers. This comprehensive approach ensures a robust security posture for our cloud infrastructure and applications.

It serves as a comprehensive solution for both proactive vulnerability management and reactive runtime threat detection.

We manage this tool through a designated management account, handling all configurations within a limited account. At times, we find it necessary to customize scripts, such as when we encounter challenges with integrating Splunk. In this instance, the events are not being formatted as desired. To address this, we aim to create a script and Lambda functions to ensure the events are in the preferred format. It enhances our ability to respond effectively, allowing us to prioritize and focus on resolving any real or potential issues impacting system performance.

It offers security scanning capabilities for multi and hybrid-cloud environments. Currently, we support two clients, each with multiple sub-clients. Within these clients, we manage two DNS instances—one in the US region and the other in the UK region.

The comprehensiveness of the security features in Prisma Cloud is highly commendable. Occasionally, like any product, we encounter issues, and during such instances, we receive prompt and quality support from AWS. The collaborative nature of addressing and resolving issues enhances the overall convenience and effectiveness of using Prisma Cloud for our cloud production environment.

To proactively address cloud security, this tool has been instrumental. We've designed it as an offering for our sales department, enhancing our ability to cater to customer needs. Currently, our focus is primarily on container security, encompassing AWS, GCP, and Azure. This tool effectively identifies and manages vulnerabilities and compliance issues related to containers.

It offers the visibility and control we require, adapting seamlessly to the complexity and distribution of our cloud environment. With the Access Controller system, we can define multiple roles, granting specific access to workload environments, vulnerabilities, and compliance information. Leveraging these features, we efficiently manage access across our teams. This includes utilizing group connections to organize and simplify access, reducing the complexity associated with console and account access in our cloud environment.

It provided a strong confidence in the overall security and compliance posture of our workload.

It has empowered us to seamlessly integrate security into our CI/CD pipeline and align it with existing DevOps processes. Within our Jenkins pipeline, we leverage Checkmarx integration to conduct scans on our code repositories and jobs running through the pipeline. The introduction of numerous features with Prisma Cloud has significantly enhanced our security measures. While we haven't fully explored these features in the US region, as they are still in progress, we look forward to utilizing them once they go live in our pipeline.

It provides clear insights into runtime risks throughout the entire pipeline, presenting issues as they are uncovered during the build phase. This dual functionality includes both fixing and addressing runtime concerns. Within our categorized runtime alerts, we receive numerous notifications, acknowledging that some may be false positives. However, this abundance of alerts serves as a proactive measure to identify and investigate any suspicious activities occurring at runtime. We analyze each alert to determine its relevance and, if necessary, proceed with incident response actions. It ensures that legitimate issues are addressed promptly, while also minimizing the risk of overlooking potential threats.

To minimize runtime alerts, we have the flexibility to create custom rules, allowing us to bypass specific alerts that we are confident are expected and should not appear in our console. This customization is crucial for maintaining a streamlined team environment and ensuring our business operations are not unnecessarily disrupted.

It has significantly reduced the time spent on alert investigations, thanks to its built-in investigate feature. It allows us to efficiently query only the relevant alerts, enabling us to filter based on our release criteria. This streamlined approach has resulted in a notable reduction of about twenty to thirty percent in investigation times.

I find the code security feature in Prisma Cloud particularly valuable. It provides insights into potential vulnerabilities in our code, helping us identify and rectify issues before they can be exploited. Additionally, the emphasis on container security is notable, making it a key focal point within Prisma Cloud.

The security automation capabilities of the solution are quite effective. With numerous automated features, such as investigation acquisition, we can utilize queries to analyze our environment and review past activities. The overall automated functionality is impressive—we no longer need to create templates from scratch, as they are already available. It streamlines our processes, making it a notable and beneficial aspect of the product, particularly when a substantial portion of tasks are automated.

The solution's comprehensiveness in securing cloud-native development throughout the entire lifecycle—from build and deploy to run—is noteworthy. Specifically, we leverage the core security features, integrating them with Checkbox, a tool mandated by Prisma Cloud. The integration facilitates Software Composition Analysis scans and checks for license violations.

The standout feature of this tool is its ability to consolidate all the features we typically access from various sources, including AWS. While AWS and other services may require the use of multiple tools, Prisma Cloud excels by offering a comprehensive solution within a single dashboard. This unified approach addresses all our requirements, making it the most advantageous aspect of this tool.

While the code security feature has undergone recent enhancements, there is room for improvement in terms of its cost module. Presently, the pricing structure poses a challenge in convincing our customers to adopt this tool, especially since code security is a critical area of interest for many.

At times, we find certain features missing. In these instances, we engage with our support team, requesting them to submit feature requests on our behalf. Our clients have expressed a need for scanning application vulnerabilities on Windows servers, a feature currently available only for Linux.

We have been working with it for two years.

It provides excellent stability capabilities. I would rate it nine out of ten.

Scalability is a strong aspect; we have never experienced issues with it. It consistently remains highly available. Our clients are large enterprises.

Support is not just good; it's excellent. I find their assistance highly commendable, and I would rate it nine out of ten.

Positive

We previously relied on RapidFile and another tool for vulnerability detection, including analyzing subscription behavior. However, since adopting Prisma Cloud, with its advanced intelligence and machine learning capabilities, we've experienced a significant improvement. It not only efficiently detects vulnerabilities but also provides deep insights into our environment. This proactive understanding of our environment, including its nature, vulnerabilities, and potential threats, has proven to be a valuable aspect of using Prisma Cloud.

We previously used Qualys, a tool known for its diverse features. While Qualys encompassed various functionalities, including container security, I noticed a discrepancy in the vulnerabilities detected by Prisma compared to Qualys. Although Prisma exhibited robust features, there were instances where certain vulnerabilities highlighted by Qualys were not identified by Prisma.

The initial setup was a straightforward process. The team was efficient, accommodating our requests and providing a trial without any cost. The entire process, from requesting the trial to obtaining our tenant, was completed smoothly within a month.

We have a team of around six people in charge of the deployment process. Maintenance is essential. Occasionally, we observe issues with the UI, usually scheduled during weekends. Notifications are provided about the main areas affected, and the tool is temporarily unavailable during this period. Following the maintenance, the tool resumes normal operation.

I find the pricing to be expensive. I would rate it eight out of ten.

I highly recommend this solution, and I suggest anyone interested in it to explore a trial first. Once they see the benefits, they can proceed with full implementation. It enables you to consolidate everything under one control, making it a definite recommendation from my side. Overall, I would rate it nine out of ten.

We used a couple of modules, mostly WAFs. We use it for detection. 

We use it for our modern infrastructure, mostly run on the cloud. We use it to measure the security of cloud-native infrastructure and to calculate the risk of the applications we use and APIs we interact with. We also use it to meet compliance requirements. We have plenty of use cases for this product.

We really wanted to capture all of the information. To make something in-house would be too much engineering work for us. We don't have to bui;d something from scratch; this allows us to use something that is highly accurate.

We're a fintech company and we deal with a bank. Doing certain tasks manually, like logging every node, server, and container, can take six to nine months. However, if you can automate the process, you achieve the same results in a short time span to help ensure product security.

We were using common CBE for general identities.

I personally used the web application API security, WAF for in-line controls. It helps with implementing an additional layer of security to block the attacks and get alerts on vulnerabilities. I am just focusing on that side.

The support is excellent. They'll call us personally and keep us updated. It's some of the best support I've dealt with.

It's great for protecting the full cloud-native stack. Being a security engineer, I have the visibility of the solution on the infrastructure. The tool is doing a good job of automating this process and making it less time-consuming for me. I don't need to handle as many manual tasks.

There are various cloud configurations that can help you gain insights. If a threat is on the portal, it will give you insight into the cloud infrastructure to help you improve the configuration to make it more secure. In terms of threat detection, you can see different kinds of payloads coming to the API. It helps you consider fixes, like adding more validation.

It is very easy for us to generate reports and download the findings while working with the team to resolve issues.

It's good for build, deploy, and run, however, we still need to figure out how to better integrate it. We're still in the early stages of exploring this for CI/CD. 

The solution does provide the visibility and control we need regardless of how complex or distributed your cloud environment becomes. When we were using our core infrastructure previously, we didn't have the visibility, for example, on which APIs we had or were using. Now, there's a better understanding. It's helped us become more confident in our security and compliance posture. If someone comes tomorrow to audit, we can do a fast report and we can pass that over to show to compliance. It would show the risk factors and what we are monitoring. It's the first thing we would go to during an audit, to provide transparency. 

The solution provides a single tool to protect all of our cloud resources and applications without having to manage and reconcile disparate security and compliance details. It's mandatory to have a tool like this to run a fintech in India as we need to have an audit trail in order to be able to submit reports. Operationally, it's helping us stay compliant. 

We are able to enable alerts. We are using it more manually. We can see alerts on Slack. We can configure alerts as we like.

The UI is good, however, they could improve the experience. The animations on the dashboard could be better. They may already be working on an update to improve this.

We'd like to understand better how to automate between the pipeline and CI/CD. There's a bridge needed between DevOps and security. We need to understand the alerts. There seems to be a gap in DevOps that we need to reconcile. 

I've been using the solution for more than six months. 

While running the solution, we have no issues at all. 

We have Prisma installed on Google Cloud, across multiple accounts and environments. We also have data recovery in another region. I'm not sure if that is covered by Prisma. 

It's scalable. It's not difficult. In fact, it's easy. You just need to add agents to the nodes you want. 

Technical support is great. There are two teams. One is always available. Another is creating tickets and looking into issues. Both are quite good. They are eager to support the customer. 

Positive

We were using another product previously. It was called Lacework. The virtual business aspect was a reason we switched. We also wanted to have more functionality and more insight and control into APIs. The visibility was also better with Prisma. 

The deployment was handled by the DevOps team, not the security team, which is the team I am a part of. There was a requirement to install it on every node of the infrastructure. However, my understanding is it did not take too much time. My understanding is that it was easy to install and it was done within 30 minutes to an hour. It was deployed in a very short amount of time. One person was able to deploy it; we didn't need a team. 

There may be some maintenance required. 

I'm not sure of the licensing terms or the exact pricing. 

We did evaluate multiple tools. We knew what we needed the tools to do and we were comparing them all together. We realized that Prisma did a better job and decided to go with them. 

I am a customer and end-user. 

I'm not sure if the product is useful in a multi-cloud environment. I hope it is. We just have the one cloud environment we use it in. That said, we are using it in multiple staging environments. 

We have not enabled the Code Security module. We still need to integrate in that sense with Prisma. We did do the integration with cloud infrastructure. 

For any product you choose, it's good to consider security. I'd recommend Prisma as it offers good security. 

I'd rate the solution eight out of ten. There isn't really anything missing in the product. However, there's always scope for improvement. 

We use the CSPM (cloud security portion management) product from Palo Alto Networks for our day-to-day activities. We use this product every day, almost 24/7. I am a cloud security engineer in my organization, and I use this product to identify misconfigurations from the account level. We use AWS accounts in our organization. We have more than 150 accounts in our organization, and we get support from this product to identify the misconfiguration among all those cloud accounts.

Along with misconfiguration, we use it to generate custom RQL based on our requirements in our day-to-day activities. We use the solution for user access and onboarding Defender into our product to identify the vulnerabilities in our cloud environments. We see if the instances are publicly enabled or encrypted. 

It also helps us to check if some changes have to be done on load balancers ELB 1 or ELB 2 in our environment.

Almost from the product level, with all the cloud accounts, 1,600 global policies and 1,200 AWS-related policies are provided. We used to customize based on compliance and integrate it with Jira. Using Jira, we inform the end users about the misconfigurations in day-to-day activities. Finally, we'll try to get the solution for the alerts generated by the tool.

The solution's dashboard looks very user-friendly. The misconfigurations alert tab also looks good. The solution has both positives and negatives, but this product is the best compared to other solutions. According to our requirements, we can very easily identify the solutions based on cloud accounts, single accounts, or multiple accounts. The graphical way JSON was recently launched is very good to get the proper exact RQL based on the requirement.

We have a suggestions team, and we used to write our thoughts on the dashboard or website. The website is reviewed by users working with the product team. Recently, we discussed a new thought with the product team that the misconfiguration or the work done by the user should be at the user level. The dashboard can be created at the user level instead of the cloud account level, which will help save time.

They can create a folder for their work, directly go to that folder, and work with it on day-to-day activities. It's a new idea we suggested to the product team. When 1,000 members are working on the product, the product team cannot implement all the 1,000 thoughts invented by everyone. We used to submit our thoughts on our product website bi-weekly or bi-monthly.

I have been working with Prisma Cloud by Palo Alto Networks for more than two and a half years.

Prisma Cloud is a scalable solution. More than 250 users are using Prisma Cloud in our organization.

Prisma Cloud's technical support team used to resolve all our issues within no time.

Positive

I previously used PingSafe, which is more cost-efficient than Prisma Cloud. When I started working with PingSafe, I thought it could be a good product. However, when I changed to Prisma Cloud, I thought it might be more efficient when compared to other products.

We have seen a return on investment with Prisma Cloud, and our organization is completely satisfied with the solution.

Prisma Cloud is a highly expensive solution.

If 50,000 employees work in a single organization or an MNC company, the company should use a high-level product, not a low-level product. It's based on the company, and it's based on the product. For my organization, I completely agree with Prisma Cloud's licensing part. I cannot discuss whether it's efficient, but I completely agree with the product features.

We are using the compliance module of the solution.

We use the solution to secure the cloud accounts in our organization that we maintain. We launched this tool for our security. We used to choose the products in the market based on the budget. Prisma Cloud was already launched and onboarded before I came to this organization. We used to onboard other tools, like Defender Cloud or Prisma Cloud.

CSPM is different from Prisma Cloud; they are two parts in a single product. For day-to-day activities, we use CSPM almost 100% and Prisma Cloud for almost 30% to 40%. CSPM identifies the alerts and misconfigurations from the account level for day-to-day activities. We inform the DevOps team to close the alert by getting the solutions from their account-level site.

We chose this product to identify the misconfigurations based on the severity level. For critical, it should be done within one or two days; for high, it should be done in three to five days. Based on the time period, we used to get these solutions in time. Sometimes, users may face many exceptions for the solution or alerts.

For example, there will be some internal ELBs (elastic load balancers) from the account level. Internal ELBs cannot be published because they'll be used internally to share the data. The policy may identify the alert from the internal ELBS also. So, we need some exceptions so that the internal load balancer can be accepted but not generate an alert from the Prisma side.

We used to change our RQL query based on the requirement. Otherwise, we approached the product or support teams to get the solution from them. They'll provide the RQL with the changes based on the requirement, and we'll get the solutions as quickly as possible. Most of the time, when there is a problem, there will also be a solution.

Maintaining an organization with multiple million dollars is not an easy thing at the market level. So, it's important to have a product that effectively identifies the issues. Nowadays, hackers send a simple link to an unknown user. When users click the link, their bank account gets hacked, and the amount gets deducted from the customer side.

When a single user gets this type of attack, an organization should be equipped to effectively identify these attacks. This product works very effectively to identify such attackers. The solution can not only help identify present attackers' thinking, but we can think about the future and customize the queries based on the attackers' mindset. We can identify the attackers' way not to get marketed in the banking sector.

Prisma Cloud is a monitoring tool that continuously monitors 24/7. It's not about getting the solution but identifying the misconfiguration. When it continuously monitors the cloud accounts, the product identifies the issues, and we get the solution.

Getting the solutions is in our hands, but identifying the issues is the product behavior. The product behavior to identify the issues is highly appreciable. Then, we get the solution based on the requirement.

Whatever automation Prisma Cloud provides to the policies is a good way to get this solution, but automating the complete tool has its positives and negatives. It's a debatable question because Prisma is not a testing tool. The tool identifies misconfigurations

The solution can't provide 100% security at the market or organization levels. If we secure a product by 99%, there is still a chance of a one percent attack. So, there should be some monitoring as well as automation. However, going for only automation or monitoring is a debated question.

We continue using Prisma Cloud because we are 100% satisfied with it, not only from my side but also at my organization level. In my organization, we started a gap analysis. We are maintaining more than 150 AWS cloud accounts. So, there are a lot of alerts for misconfiguration from the product level.

Since January, we have started one requirement to reduce the alert. We collect all the alerts in an Excel sheet, and we used to share with the DevOps HOD that these are the misconfigurations for your account. Then, the HOD used to share the sheet with the team members.

I can proudly say that we started with more than 8,600 alerts for all the cloud accounts in the month of January. Now, the count is reduced to almost 2,400 alerts for more than 40 sensitive policies. We identified almost 60% to 70% alert reduction. We are using Prisma Cloud effectively to identify misconfigurations and implement many more features to secure the cloud accounts in our organization.

We use 100% of CSPM and only 30% to 40% of the CI/CD pipeline, like Prisma Cloud. For CSPM, I'll rate it a ten out of ten. Otherwise, nine and a half out of ten because no product will satisfy a customer 100%. So, nine and a half out of ten for CSPM to secure the cloud accounts internally or prevent getting attacked by attackers. I would definitely recommend this product.

We will launch CI/CD like Prisma Cloud in the future, and the organization should also consider the budget. Prisma Cloud is a little high-budget affair. Prisma Cloud is a mandatory tool to identify the CI/CD level vulnerabilities while doing email scanning only. Our time will not be wasted by using this tool.

If we do not scan an image for vulnerabilities while deploying a code into it, it's a waste of time deploying a code that any attacker can handle. This product identifies the vulnerabilities by email scanning only, which helps to have more time for the DevOps team to get more deployment.

We used to suggest new thoughts on how it can be more user-friendly. There is an API with which we can share our thoughts. It should be selected by other users and business organizations using the product. If more people suggest that option after we launch that thought into the API, the Prisma product will think about that thought. If it is valuable, they should definitely get this solution.

Currently, we can identify the misconfigurations based on the list of policies. Suppose five to ten members work with Prisma in an organization. In that case, they cannot go daily to the dashboard and identify all the misconfigurations singly or as a group.

We suggested a new feature: a list of misconfigurations should be identified based on the user, either a single user or a group. If three members work with a particular cloud account, then those three members should create a group, and that account should be added there. This will also reduce the time of a customer working on the product.

Whatever DevOps requirement was not presented in the product, they used to discuss it with our team. If it is a requirement we need in our organization, then we will go to the product team and tell them it is a requirement from our organization level for the DevOps team. If it is a proper requirement, the engineering team will work based on it. The product team comes up with new ideas. Since the recent launch is a better version for the product team, we also used to launch the better version from the product team.

it works both ways. Whatever new features the DevOps team suggests, we discuss them with the product team. When the product team suggests new features to help the organization, the same can be discussed with our internal team. Our manager will discuss it with the HODs of the DevOps team. If it is a genuine requirement, we will try to convince the DevOps team, and based on their approval, we will launch that feature.

It's highly recommended since the dashboard is very user-friendly. The Prisma Cloud tool is integrated with Jira. Whenever any alert is generated, it will automatically trigger Jira based on compliance. It will work based on the compliance we onboarded to Jira. We used to create compliance for Jira and day-to-day activities, like generating reports based on the accounts.

Prisma Cloud is a user-friendly solution. When managing more than 50 cloud accounts, we can get the issues and misconfigurations from the single account level, the group account level, or the total account level. We can get everything based on our requirements. The solution will secure all the cloud accounts, a single cloud account when there are multiple cloud accounts, or a group of cloud accounts based on complete requirements.

Whenever we have some issues, we approach the product team to get this solution. Recently, we faced some issues with the policies tab, which we use to create policies, and the investigation tab, which we use to create a new RQL. Whatever RQL query is implemented, there is no point in creating all the RQL queries to a policy. We get the data by creating an RQL query, and we create a policy to monitor the product. The count should match when there is a single RQL query from the investigation type and the policies tab or alert tab.

Recently, we faced an issue with a mismatch between the alert tab count and the investigation tab count. We approached the product team, and they suggested the solution within a very short time. There were some issues with the pipeline, but they fixed that bug within no time, and we got a 100% solution from them.

Three to four teams are working with a single product. The security, SOC, and DevOps teams are working with the product team to identify the misconfigurations in their environment. It's not just a single person who identifies the issues from service or product levels.

The DevOps or SOC team may identify an issue and inform our security team. Also, we may find some issues and inform the product team. A combination of all groups will work to identify issues and ensure that the product will work effectively. So, all the things will happen in a single process.

We have to close cases within a specific period based on the severity. Critical cases should be closed within one to three business working days, high-severity cases within three to five working days, medium-severity cases within five to eight working days, and low-severity cases within eight to fifteen working days.

We use some budget for the product based on the agreement. Besides that, we save a lot of money compared to the security level. I'm not talking about the product level. Product-level money is different based on the agreement. In the last one and a half years that I started working with this product, only one time without a product level or service level, we entered some credits by enabling some policies. If we have some knowledge of the product, almost 95%, there is no waste of money.

Prisma Cloud is a completely user-friendly product. The product is highly recommended for the cloud environment level. Whatever requirements we have, we can get by creating a new RQL based on our requirements. It is not only related to work. Whoever works with cloud security in an organization is greatly noticed.

If someone identifies an issue in your work, you'll remember that person. In the same way, when I notified some issues from the cloud account level, I used to interact with the entire DevOps team, not only a single person. The product helps you get more recognition.

Previously, we used the solution globally. However, because there may be a chance of data being made publicly accessible, we are currently onboarding only on the internet from the Prisma site. This secures the data and prevents it from being made publicly accessible.

I would recommend Prisma Cloud to other users or organizations looking to secure their organization in any cloud environment without budget constraints. I'm only talking about AWS because we have an AWS environment, but the solution can secure any cloud account effectively.

Overall, I rate Prisma Cloud a nine out of ten.