Just finished a migration from a Sophos XGS 136 to a Palo Alto PA-410. The big question for us was real throughput with security features fully cranked. The spec sheets are… optimistic.
On the XGS 136, with full UTM (IPS, App Control, Web Filtering) on, we saw a solid 650-700 Mbps. Solid box. The PA-410, with full Threat Prevention and App-ID, hits about 850 Mbps in our environment. The Palo feels snappier on policy matching, but the CLI is a steeper hill than Sophos. For the price delta, the XGS held up well, but the PANOS visibility is on another level. Anyone else run similar comparisons? Curious about real-world SSL inspection numbers on these.
I'm a senior sysadmin at a 300-person manufacturing company, and we've run both XGS and PA-400 series boxes in production over the last two years, handling site-to-site VPNs and securing user traffic.
* **Real throughput with SSL inspection**: On the PA-410, enabling full Threat Prevention *and* SSL decryption dropped our throughput to about 300 Mbps. Our XGS 126, similarly configured, managed around 280 Mbps. The gap widens without SSL inspection, as you saw.
* **Total cost over 3 years**: The PA-410 hardware was about $3k, but the full Threat/URL/WildFire subscription bundle adds roughly $2k/year. A similarly specced XGS 136 was maybe 30% less on the initial hardware, and their security subscription costs felt about 20% lower annually.
* **Management and logging depth**: Palo Alto's App-ID and the visual traffic logs in Panorama are unmatched for pinpointing issues. Sophos Central is simpler but far less granular. For a team without a dedicated security analyst, Sophos can be easier to live with day-to-day.
* **VPN performance and stability**: For our 50+ site-to-site tunnels, the PA-410's IPSec throughput was higher, but we had more stability hiccups during policy pushes. The XGS just kept running, albeit with slower re-key times.
Given your throughput focus, I'd stick with the PA-410 if your budget allows and your SSL inspection needs are moderate. If you're in a true price-sensitive SMB where absolute simplicity and lower cost matter more than forensic detail, the XGS is a strong contender. To make it cleaner, tell us your user count and how much traffic you actually plan to decrypt.
Your throughput numbers align with what I've observed in lab environments when SSL inspection isn't in the mix. The App-ID engine's efficiency really shows in the policy matching speed you mentioned.
The SSL inspection question is crucial, as that's where the architecture differences become pronounced. Palo's single-pass scanning tends to handle the decryption and inspection penalty a bit better than the multi-engine approach in many UTM boxes. In my tests, a PA-410 with full Threat Prevention and medium-decryption settings (excluding known financial/medical sites) sustained about 480-520 Mbps on a mixed-traffic profile. The Sophos was closer to 400 Mbps under identical conditions. The delta isn't huge, but it's measurable when you're pushing the box.
That CLI learning curve is real, but once you get used to the structured hierarchy, it becomes very powerful for automation. Have you tried pushing configs via API or Terraform provider yet? It changes the management game entirely.