Palo Alto Networks Cloud Security

Name: Palo Alto Networks Cloud Security
Brand: Palo Alto Networks
Rating: 4.3 (654 reviews)

Leader

The industry's most comprehensive AI security platform.

Est 2005|Valuation $306.8B|Raised $261.3M

LinkedIn 2.0M|Website|Web traffic 3.9M|FTEs 21,921|HQ Santa Clara, CA

MarketsVulnerability Management Cloud-Native Application Protection Platform (CNAPP)Firewalls

Platform CoversIaC Security

Palo Alto Networks Cloud Security screenshot

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is excessive or inappropriate - Early-stage startups and small IT teams may find the operational requirements and breadth of features disproportionate to their needs; simpler CSPM tools or native cloud-provider security offerings may be more appropriate. - Use cases where competitors may be preferable - If the highest priority is rapid, agentless visibility and prioritization with minimal operational overhead, buyers often evaluate agentless-focused alternatives first. - Technical requirements that may not be met - Organizations requiring fully agentless runtime protection for all workloads with no agent footprint should validate product capabilities and deployment modes; Prisma Cloud supports multiple deployment models and suitability depends on selected modules and environment. - Budget constraints and procurement preferences - Organizations that require transparent, predictable, low-cost entry pricing and simple scaling models may prefer narrower CSPM tools or cloud-provider-integrated security services. - Specific workflow or integration requirements - If investigation UX and highly intuitive asset exploration are mission-critical, procurement teams should validate these workflows in a proof of concept. - Red flags in the buying process - Lack of clear credit consumption estimates for target workloads and modules increases the risk of cost escalation; procurement teams should request usage examples and consumption modeling from the vendor. - Limitations acknowledged in public materials - Public-facing product pages do not centralize "known issues"; release notes and technical documentation provide change logs and resolved/known issues for specific components. - Roadmap notes and feature parity - Cortex Cloud has been positioned as an evolution that merges Prisma Cloud capabilities with cloud detection and response; public roadmap details for full feature parity across every module were not fully specified in the accessible materials. - Scale considerations - Vendor claims large-scale telemetry processing capabilities; methodology and specific customer scalability thresholds were not independently validated in this research and should be tested in large-scale PoCs. - Security or compliance considerations - While vendor Trust Center materials reference ISO and SOC coverage, organizations should validate exact product scope, tenant/region applicability, and how self-managed components (Compute Edition) affect compliance responsibilities. - Architectural or integration constraints - Some reviewers report challenges integrating certain repositories and describe documentation gaps for manual searches and investigation; organizations should validate API and integration coverage in procurement.

Deal disqualifiers: characteristics of a poor fit

Small teams with limited cloud security engineering capacity.
Organizations that require very rapid time-to-value with minimal tuning.
Organizations that require highly predictable, simple per-workload licensing and cannot accommodate modular credit-based licensing.

02Why they buy

- Competitive advantages observed in reviews and market commentary - Consolidation into a single console and broad module coverage are frequently cited benefits by users seeking to reduce the number of point tools. - Integration potential with Palo Alto's broader security portfolio (network security, SecOps/Cortex) is a differentiator for organizations seeking an integrated vendor strategy. - Differentiation from competitors - Palo Alto's positioning is strongest when buyers prioritize coupling cloud security telemetry with SecOps workflows and existing Palo Alto security investments. - Evidence-based value propositions - Vendor-commissioned TEI/ROI studies provide modeled benefits; organizations should validate assumptions and seek independent corroboration where possible. - Competitive advantages of alternatives - Some competitors are perceived as easier to deploy or operate due to agentless models or simpler licensing structures; organizations should evaluate these trade-offs in the context of their requirements.

03Field reports

Selected quotes and summary sentiment from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews (where available)

- Gartner Peer Insights (CSPM market page) contains both positive and negative review excerpts: some reviewers highlight comprehensive cloud asset visibility and real-time threat detection, while others report concerns about support responsiveness and perceived reduction in vendor attention to the product. - On the CNAPP market page, some reviewers express strong negative opinions about the user experience; these are included to show the range of customer sentiment. - TrustRadius reviewers cite consolidation and coverage as positive aspects, while also noting usability and onboarding challenges. - Community discussions (Reddit) include practitioner threads describing evaluation and replacement activity (for example, migration planning away from Prisma Cloud to alternative CNAPP providers), frequently focusing on licensing and operational cost concerns. - G2 and other review platforms contain product reviews and mixed sentiment; specific excerpts were not uniformly accessible during this research.

Balanced presentation: include both high and low ratings

Available sources show a range of feedback, including high aggregate scores in some venues and negative reviews in others. Review content includes both favorable comments about breadth and visibility and critical comments about pricing, usability, and support.

Common criticisms and complaints (support issues, bugs, missing features)

Recurrent themes across reviews and community discussion include:
- Licensing complexity and unexpected costs when enabling additional capabilities
- Operational and implementation complexity due to platform breadth
- Usability challenges in certain investigation workflows and gaps in documentation
- Variability in support responsiveness across reported cases

Reasons customers chose this product over alternatives

Consolidation of multiple cloud security capabilities (posture, runtime, identity, code security) into a single vendor stack is commonly cited as a rationale for selection.
Some customers select the product for its breadth of capabilities relative to narrower point tools.

Reasons some customers left for competitors (churn drivers)

Reported drivers for migration include licensing/pricing complexity, perceived usability or operational overhead, and preference for alternatives that emphasize faster deployment or simpler licensing models.

Specific outcomes customers report (with caution regarding verification)

Reviewers report qualitative outcomes such as reduced investigation time, consolidation of dashboards, and support for compliance reporting. Quantitative outcomes are typically vendor- or reviewer-provided and should be validated in a purchaser's own evaluation.

Customer pain points and deal-breakers

Common pain points include difficulty forecasting credit-based licensing, integration complexity, and the learning curve for advanced investigation workflows. Deal-breakers reported or inferred from reviews include inability to model costs accurately and overlap with existing cloud provider security investments.

Vendor case studies and independent evaluations

Vendor web pages highlight customer stories and modeled ROI studies (TEI-style) that present quantified benefits. These are vendor-published or vendor-commissioned materials and should be interpreted with attention to assumptions and methodology.

Specific results and quantified business impact

TEI-style and other vendor-distributed reports provide modeled ROI and productivity figures; organizations should validate assumptions and request details relevant to their own environment.

Implementation details and time to value

Public case narratives provide limited implementation detail; reviewers indicate that meaningful setup effort is common and that time-to-value depends on organizational readiness and resource allocation.

Adoption challenges and mitigation

Public documentation of adoption challenges is limited; community discussions and reviews more often describe operational pain points than published remediation steps. Organizations should capture potential integration and operational challenges as part of PoC planning.

Note on vendor-published metrics

Vendor-provided metrics such as telemetry volumes and attack counts are presented without independent verification in the available marketing materials; treat these metrics as vendor-provided and validate in procurement conversations.

04Best fit

Company sizes

Suitable fit tends to be:
- Mid-to-large organizations (from medium-sized to very large enterprises)
- Companies with mid-to-large revenue footprints
- Organizations with dedicated cloud security or DevSecOps teams
Mid-market organizations with a significant cloud footprint or regulatory requirements can also be appropriate if the team can support operationalization.

Industries and verticals where adoption is strongest

Common adopter verticals include financial services, technology, and professional services, as indicated by reviewer distribution and vendor references.
Vendor case references include examples from regulated financial services and similar sectors.

Roles and personas: decision makers and end users

Decision makers: CISO/VP Security, Head of Cloud Security, Security Architecture, Procurement/Vendor Management
End users: Cloud security engineers, DevSecOps engineers, SOC analysts (with integration to SecOps/SOC workflows under Cortex)

Pain points and challenges the product addresses

Multi-cloud visibility gaps, misconfigurations and compliance drift, runtime workload risk (containers/Kubernetes/serverless), identity entitlement sprawl, and tool sprawl across multiple point solutions.

Qualification criteria: characteristics of a strong fit

Organizations seeking broad CNAPP functionality that are prepared to invest in design, rollout, and ongoing tuning.
Organizations that prefer consolidation with a single strategic vendor and may already use Palo Alto Networks products in network security or SecOps.

05The pitch

What the product does (core value proposition in objective terms)

- Palo Alto Networks' Cloud Security portfolio is composed of multiple product lines that cover different layers of cloud security: - CNAPP / application lifecycle security: Prisma Cloud (positioning shifting toward Cortex Cloud) provides "code to cloud" capabilities spanning posture management, workload protection, identity entitlement management, and code/CI/CD security. Vendor materials describe lifecycle coverage across development and production stages. - Cloud network security: Cloud NGFW for major public cloud providers and VM-Series to apply next-generation firewall controls in cloud environments. - Data & SaaS security: Enterprise DLP and SaaS security / CASB-related offerings within the Prisma family. - Cloud detection/response alignment: Vendor messaging frames Cortex Cloud as aligning CNAPP capabilities with cloud detection and response on the Cortex platform. - Vendor materials emphasize consolidation of cloud security telemetry, prioritization aided by machine learning, and efforts to align operations across the cloud attack surface.

Target market and market positioning

- Primarily positioned for mid-market to large enterprise and regulated organizations running multi-cloud and hybrid environments that seek consolidated tooling rather than multiple point products. - Prisma Cloud's combination of CSPM, CWPP, CIEM, code security, and additional modules targets teams aiming to reduce the number of separate tools, though that breadth can increase configuration and licensing complexity. - Government-focused offerings exist; specific authorizations and availability vary by offering and region.

Get a comprehensive analysis of Palo Alto Networks Cloud Security including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →