Palo Alto Networks Software Firewalls

Name: Palo Alto Networks Software Firewalls
Brand: Palo Alto Networks
Rating: 4.4 (302 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

MarketsCloud-Native Application Protection Platform (CNAPP)Firewalls Security Service Edge (SSE)

Palo Alto Networks Software Firewalls screenshot

Published Jun 11, 2026

01Common complaints

- Budget-constrained environments where NGFW subscriptions will not be fully utilized; some subscription components may be perceived as expensive relative to basic firewall needs. - Teams with low tolerance for version churn or limited release-management capability; community-reported incidents highlight the importance of staged testing and HA design. - Organizations expecting deeply integrated cloud-native firewall constructs without traffic steering; VM-based approaches typically require explicit routing. - If support responsiveness is a critical factor and premium support or partner escalation channels cannot be secured; community feedback indicates variability in support experiences.

Deal disqualifiers (poor fit)

Use cases that only require basic L3/L4 firewalling and for which cost is a primary constraint.
Organizations unable to tolerate release instability risk and lacking the ability to stage upgrades or operate HA patterns.
Procurement processes that require fully transparent, self-service list pricing without vendor engagement.

Release quality and bugs

Community reports and some independent coverage document random or unexpected reboot behavior tied to specific PAN-OS versions and hotfixes. Buyers should evaluate release notes, known issues, and vendor advisories prior to rolling out new versions.

Security vulnerabilities and DoS risks

Public reporting has documented patched vulnerabilities (including DoS-style issues) in PAN-OS and associated components; operational security practice requires timely patching and monitoring of vendor advisories.

Licensing complexity

Multiple licensing models (credits-based BYOL vs PAYG) and entitlements tied to capacity or feature bundles can complicate forecasting and procurement.

Roadmap visibility

Public roadmap details for VM-Series or specific software features were not available in the materials reviewed; forward-looking commitments are often shared under partner or NDA arrangements.

02Why they buy

Observed in customer and practitioner feedback

Consistent application-layer control model (App-ID style) across hardware and virtual deployments is commonly cited by practitioners as a reason to standardize on the vendor's platform.

Vendor-claimed differentiation (requires buyer validation)

The vendor positions the product in the context of broader security and cloud offerings. Specific vendor claims about scale or comparative performance should be validated via third-party testing, proof-of-concept trials, or direct methodological disclosure.

Areas where competitors may have an advantage

Pricing transparency and procurement simplicity in some channels.
Potentially lower total cost of ownership for organizations that do not require the full application-layer threat stack.

03Field reports

Review platforms (G2, TrustRadius, PeerSpot, Capterra)

G2, TrustRadius, PeerSpot, and Capterra host user reviews and summaries for VM-Series and related Palo Alto products. Review excerpts and platform summaries indicate a mix of sentiment, highlighting ease of some implementations and strengths in application-layer policy and advanced threat features, alongside critiques such as perceived cost and support variability. Review platform summaries should be validated against full review text for context and sample size.

Community (forum) commentary — real-world pros and cons

Community discussions (for example, forum and community-hosted discussions) are not verified buyer statements but can provide operational detail. Positive observations noted by practitioners include: - Consistent application-layer controls and an established App-ID model. - Flexibility for lab and testing scenarios (for example, use of virtual wire). Reported frustrations in community discussions include: - Variable support experiences, with some users reporting slower or less helpful responses in community forums compared with vendor support channels. - Licensing and subscription packaging changes causing perceived price increases or procurement complexity (anecdotal reports exist).

Analyst platforms

Direct access to paid analyst portals (for example, the full Gartner Peer Insights dataset) was not included in the sources used for this report; vendor-authored materials referencing analyst recognitions should be treated as vendor-provided summaries unless independently validated via the analyst platform.

Outcomes customers reported (metrics)

Vendor-commissioned ROI and Total Economic Impact (TEI) studies are cited in vendor materials and typically report quantitative ROI and efficiency improvements. These studies are vendor-commissioned and should be reviewed for methodology, sample size, baseline assumptions, labor rate assumptions, cloud cost inclusion, and potential selection bias before applying findings to other contexts.

Vendor case study examples (public cloud deployments)

Palo Alto provides public case studies referencing customers (for example, public sector and enterprise customers) and cites commissioned TEI or Forrester studies. These items illustrate potential outcomes but require critical evaluation of methodology, sample size, and relevance to a buyer's environment. Critical evaluation points: - Vendor-commissioned ROI and TEI studies often reflect specific customer profiles and assumptions; readers should review the underlying methodology and assumptions. - Case studies frequently omit detailed baseline and counterfactual assumptions; procurement teams should request clarifying details during vendor engagement.

Independent validation references

Independent lab reports and third-party validations exist for some Palo Alto products; however, readers should confirm the scope and date of any independent test reports and whether the VM-Series or specific software features were included in the test scope.

04Best fit

Company sizes (practical guidance)

Mid-market to enterprise organizations (typical ranges in deployments vary widely) where security teams can operate and maintain an NGFW stack and where segmentation and consistent application-layer policy provide measurable value.
Cloud-forward enterprises running multi-region workloads that require consistent inspection across VPC/VNet and data center.

Industries

Common in regulated and higher-risk industries such as finance, healthcare, government, and enterprise SaaS.

Roles and personas

Decision makers: CISO, VP of Security, Head of Network Engineering, Cloud Security Architect.
Users: firewall administrators, SecOps, NetOps, cloud platform engineers.

Pain points addressed

Need for consistent application-layer policy across hybrid environments.
East-west segmentation in virtualized environments.
Threat prevention and visibility across encrypted traffic where decryption is used.

Qualification criteria (good fit)

Organizations that have standardized on Palo Alto NGFW/PAN-OS and want policy portability across hardware and virtual deployments.
Organizations with mature change control and release management practices.
Teams able to invest in cloud routing and high-availability patterns required to support VM-based firewalls.

05The pitch

What the product does (core value proposition)

Palo Alto Networks "Software Firewalls" are the company's virtualized and cloud-deployable firewall offerings (commonly referred to in the industry as "next-generation firewalls" or NGFWs). These products are intended to apply consistent security policy and threat prevention across public cloud, private cloud, and virtualized data center environments. In Palo Alto's packaging, this typically includes: - VM-Series Virtual NGFW (virtual appliance form factor) for common hypervisors and cloud environments. - An associated licensing/consumption model via Software NGFW Credits (credits-based) for BYOL deployments, plus cloud marketplace pay-as-you-go options. The vendor positions the product to provide the same PAN-OS features used on hardware appliances (App-ID/User-ID/Content-ID, threat prevention, decryption controls, logging/visibility) in software-defined environments.

Target market and market positioning

Target market: mid-market to large enterprise; also managed service providers and regulated organizations that require segmentation and policy consistency across hybrid cloud.
Positioning: the vendor positions the product as extending NGFW capabilities into cloud/virtual environments, commonly sold as part of a broader platform strategy (NGFW plus SASE/Prisma plus Cortex).

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

Download full report →