Prisma SD-WAN Reviews & Product Details

I really like how seamlessly users are able to connect to the enterprise application. Prisma SD-WAN solves my enterprise connectivity problem, allowing us to seamlessly connect with the applications. The users can connect from different geographical locations to the enterprise application seamlessly, and they are able to use the best link available. The monitoring is very important feature for us, it helps navigate different app performance, and the ISP performance on Strata Cloud Manager Portal. Review collected by and hosted on G2.com.

The monitoring could be improved. We sometimes see there is a glitch in the monitoring. The dashboard is not presenting the right values, and most of the time the monitoring agents, they kind of get corrupt. We have to get to the support team and then get it fixed. Review collected by and hosted on G2.com.

Prisma SD-WAN has been a game-changer. The biggest win for us is definitely the centralized management – having that "single pane of glass" view, especially with our existing Palo Alto firewalls, is incredibly valuable. It makes troubleshooting so much faster and more intuitive. I also love how it dynamically steers traffic based on real-time conditions. We've seen a noticeable improvement in application performance, and the lag that used to frustrate our team has pretty much disappeared. Review collected by and hosted on G2.com.

One thing that took some getting used to was the terminology and how policies are structured within the orchestrator. It's powerful, but there's a definite learning curve to fully grasp its intricacies. The UI, while functional, could also use a bit of polish in certain areas. Sometimes, navigating between different policy layers or trying to find specific logs feels like it requires more clicks than it should. And I've heard some folks mention that the documentation could be more robust – luckily, we haven't hit too many roadblocks that required deep dives into it, but it's something to consider. Review collected by and hosted on G2.com.

What I like best about Prisma SD-WAN is how intelligent and automated the path selection is.

It constantly monitors the performance of all WAN links and dynamically steers traffic based on real-time conditions like latency, jitter, and packet loss — which has significantly improved application performance without me needing to manually intervene.

I also like the management over cloud which is easy to control. Review collected by and hosted on G2.com.

One thing I dislike about Prisma SD-WAN is that the initial learning curve can be a bit steep, especially if you're coming from a traditional networking background. The terminology and the way policies are structured in the orchestrator take some time to get used to.

Lastly, the UI — while functional — could be a bit more hard in some areas. For example, navigating between different policy layers or finding certain logs sometimes takes more clicks than it should.

That said, these are mostly usability issues, and once you're familiar with the platform, they’re manageable. Review collected by and hosted on G2.com.

honestly, I was bracing for a headache, but it just clicked right into place. Once it was running, everything felt smoother; our apps worked better, and the lag that used to frustrate the team pretty much disappeared. On top of that, knowing our network is more secure with all these new devices popping up everywhere is such a relief. Plus, saving money every month doesn’t hurt! It’s those little wins that make it feel like a smart, no-nonsense upgrade. Review collected by and hosted on G2.com.

honestly, tweaking the analytics dashboards to fit what we need feels way more complicated than it should be and What bugs me most is that sometimes video calls get choppy, which is really annoying when you’re trying to stay professional. Review collected by and hosted on G2.com.

Application-defined steering and SLA management, single-pane orchestration at scale, and deep integrations with Prisma Access and CloudBlades for policy automation and security consistency.

designed for hub/cloud-centric topologies so validate full-mesh or complex east-west requirements early; ION branch appliances emphasize connectivity over NGFW feature parity so plan for security insertion (Prisma Access or on-box PAN-OS) accordingly; and teams will experience an operational learning curve shifting from traditional MPLS/firewall models.

Strongly recommended for customers that have embraced an internet-first SASE approach and require automatic application-based routing and centralized operations; confirm full-mesh and branch security requirements before a broad rollout. Review collected by and hosted on G2.com.

As a certified practitioner, what I dislike about Prisma SD-WAN can be summarized in a few pragmatic concerns: it has a clear hub-and-cloud bias that makes full-mesh or complex east-west fabrics harder to design and operate, so you must validate topology fit early and often; the ION branch appliances prioritize connectivity and steering over full NGFW parity, meaning branches that need deep inspection will require Prisma Access or supplemental firewalls; the operational model demands a mindset shift — app-centric policies, CloudBlades and overlay behaviors introduce a learning curve for teams used to traditional MPLS/firewall operations, which calls for upfront training and scripted runbooks; licensing and feature modularity (many capabilities behind add-ons) complicate cost forecasting and procurement, so build detailed cost models and negotiate bundles; reliance on a cloud control plane, while generally resilient, creates another availability surface to plan for test control-plane failure modes and ensure local failover is rock solid; the platform produces a high volume of telemetry that can overwhelm teams unless filtered and integrated into observability systems; hardware and firmware heterogeneity across ION SKUs can make lifecycle management and upgrades fiddly, so standardize SKUs and automate patching; deep integration with Palo Alto’s SASE ecosystem risks vendor lock-in for organizations that need multi-vendor flexibility — where possible preserve standard protocol interop; SD-WAN steering can’t fix poor ISP last-mile so customers sometimes have unrealistic expectations, which requires ISP diversity and SLAs in the design; and finally, while Prisma is strong broadly, very niche edge features or specialized routing behaviors may be better served by competitors, so pilot and bake-off critical functions before a wide rollout. Review collected by and hosted on G2.com.

The compatibility with a lot of enviroments because we some time we need to communicate cloud with onprem and the configurations we need to follow are so easy to configurate Review collected by and hosted on G2.com.

1. Complex initial setup – The onboarding process can be complex, especially for teams without deep networking experience.

2. Steep learning curve – The interface and configuration options are powerful but may feel overwhelming at first.

3. Documentation gaps – Some users report that documentation is either too generic or lacks real-world deployment examples.

4. UI performance – The web interface can sometimes be slow or unintuitive, especially when navigating large configurations.

5. Licensing and cost – Pricing models may not be straightforward, and costs can grow with scale.

6. Integration quirks – Integration with legacy systems or third-party solutions may require manual workarounds. Review collected by and hosted on G2.com.

I think the main points that the SD-WAN focuses on, are the best things.

The ease of integration in my companies network was something I did not expect, it's pretty easy to use and I haven't had to use the customer support for the system yet even with the frequency of use but I heard it's good. My favorite feature is probably the Ai Ops aspect, while not original, they do it well. The implementation is somewhat of a learning curve but more efficient when you know it. Review collected by and hosted on G2.com.

I think the worst things about the Prisma is that the price of the system is pretty high, I think being such a new product that is to be expected but still harder to convince people to buy it because of that. Review collected by and hosted on G2.com.

I run the day-to-day SD-WAN fabric for 98 clinics and two data centers, using ION 3200/5200 appliances and Prisma policies pushed from Panorama. The traffic-engine looks at loss, jitter, and one-way delay every 200 ms with built-in synthetic probes, then flips sessions to the cleaner link in under 300 ms—fast enough that our SIP handsets never click. App-ID fingerprints more than 3,000 SaaS and medical apps, so I can pin Epic Hyperspace and PACS image pulls to the 500-Mbps DIA link while sending Windows updates out the cheaper broadband path. The device OS exposes a full REST API; I use a 120-line Python script to pull JSON metrics, merge them with Splunk HEC events, and show branch MOS scores in a single glass. Template-based configs mean I only set the BGP ASN, loopback IP, and site tag once; the box auto-generates IPSec tunnels with AES-256-GCM, IKEv2, and SHA-256 checks. Zero-touch deploy really works—we ship an ION, the nurse plugs in power and WAN, and it dials home through TLS 1.2 to claim its config. All this cut circuit outages by 42 % and helped slash P1 ticket volume by about a third. Review collected by and hosted on G2.com.

Code upgrades still drop forwarding for 60-90 seconds—fine for web, but bad for HL7 streams that hold TCP sockets open for hours. The policy UI hides object IDs deep in nested menus, so bulk edits with the mouse are slow; a typo in a JSON import can leave the device stuck in “staged” until support clears the lock. IPv6 support exists, but you can’t do dual-stack path rules yet, so I run NAT64 as a band-aid. Flow reporting exports NetFlow v9 only; if you want IPFIX you need to push logs to Cortex Data Lake and pull them back out, which adds delay. On 1 Gbps links, the in-line IPSec engine tops out near 840 Mbps with AES-GCM—enough for now, but we’ll hit the ceiling as we move more imaging to the cloud. Finally, TAC response on complex BFD-flap bugs can take two business days, and you often bounce between SD-WAN and firewall queues before getting the right engineer. Review collected by and hosted on G2.com.

The cloud-native model is interesting, the policy-based approach is conceptually modern, and the integration with Palo Alto’s broader ecosystem is definitely a plus Review collected by and hosted on G2.com.

Complex and unintuitive management interface – The console is not user-friendly, and many configurations require a steep learning curve, even for teams already familiar with other SD-WAN solutions.

Lack of stability – We experienced instability in tunnels and failovers that weren’t always timely. In critical environments, this is a serious concern.

Limitations in complex scenarios – The product seems to perform better in standardized deployments. When dealing with advanced configurations or integration with existing systems, options are often rigid or require workarounds that feel like temporary fixes.

Support needs improvement – Response times are not always fast, and we frequently had to re-explain the same issue to multiple support engineers. Additionally, the available documentation is scattered and, in some cases, outdated. Review collected by and hosted on G2.com.

Ease of Use

Palo Alto SD-WAN excels in its intuitive interface, which simplifies policy management and traffic prioritization. Leveraging my experience with CheckPoint and Stormshield NGFW platforms, I found Palo Alto’s centralized dashboard particularly streamlined for configuring QoS policies and monitoring application performance. The visual topology mapping reduces complexity in troubleshooting, aligning with my work in global WAN environments (MPLS, IPSEC, SSLVPN). Review collected by and hosted on G2.com.

Cost and Licensing Overhead

The platform’s premium pricing model and feature-tiered licensing (e.g., advanced security modules, cloud integrations) may strain budgets for small-to-medium enterprises. This contrasts with open-source or cost-flexible solutions like pfSense or Fortinet, which you’ve likely encountered in past roles at smaller firms. Review collected by and hosted on G2.com.