Quick Take
Quick Take: A tender BOM that says "servers, switches, storage" buys you three different kits and a price comparison that means nothing. Write 9 fields on every line — function, performance floor, quantity with units, interfaces and optics, licence term, power and cooling, warranty, delivery window, acceptance test — add a deviation table, and ask for one alternative column. Then bids differ in price and delivery, not in what is being bought.
You are not writing paperwork. You are deciding what the evaluation committee will be able to compare. Spend two hours on the BOM now, or spend a tender round re-running it later. Send us the draft clauses and we will mark the lines that will come back incomparable, before the tender opens.
What goes wrong when the PA-1400 RFQ uses firewall-only Gbps?
Quick Answer: You award a light inspection test. Production turns Threat Prevention on.
GSC already sends pa 1400 datasheet, pa-1410 datasheet and pa-1420 datasheet queries to BENQUAN — and the specs page collects impressions when buyers need a sizing answer, not another chassis photo. Typical scene: finance compares “8.5 Gbps firewall” on PA-1410 against another vendor’s Threat Prevention figure. After cutover, Threat subscriptions and IPsec are on; latency climbs and new sessions fail.
This page is model-specific: which Palo Alto PA-1400 datasheet rows are eligible for award. The general rulebook lives on NGFW throughput: which datasheet rows to size. Ports, PoE and optics stay on the PA-1400 series specs RFQ page.
Soft channel Mbps below are industry-published “up to” figures from the public PA-1400 Series datasheet (PAN-OS 12.1 appmix) — pending confirmation on your dated PDF and software train.
PA-1400 datasheet rows — which ones bind the RFQ?
Quick Answer: Same appliance, stacked numbers; award on Threat Prevention and IPsec.
| Datasheet row (PAN-OS 12.1 appmix) | PA-1410 (up to) | PA-1420 (up to) | Use for RFQ sizing? |
|---|---|---|---|
| Firewall throughput (appmix) | 8.5 Gbps | 9.5 Gbps | No — not award metric |
| Threat Prevention (appmix) | 4.5 Gbps | 6.2 Gbps | Default yes |
| IPsec VPN | 4.1 Gbps | 5.6 Gbps | Required if VPN binds |
| New sessions/sec | 100,000 | 140,000 | Always beside Gbps |
| Max concurrent sessions | 945,000 | 1.4M | Always beside Gbps |
Threat Prevention on the public sheet includes App-ID, IPS, antivirus, antispyware, WildFire, DNS Security, file blocking, and logging under appmix. All values are “up to” and vary with configuration — Mbps pending confirmation. For interactive first-pass math, use firewall sizing calculator.
What “real” PA-1400 throughput means for procurement
Quick Answer: Capacity with Threat Prevention on — not firewall-only marketing.
Definition: for buying and tendering PA-1410 / PA-1420, real throughput is the sustained rate when the security features you will enable are on, under a mix close to production — including IPsec if VPN is in the design. It is not the firewall-only appmix Gbps printed above Threat Prevention on the datasheet.
Like rating a truck by towing with the trailer attached, not empty top speed. Palo Alto labels the deep inspected row Threat Prevention; Fortinet materials often say Threat Protection — different words, same RFQ idea. Model numbers, PoE and ports belong on the specs page; this page only freezes the metric name.
PA-1420 lifts Threat Prevention, IPsec and session table versus PA-1410 and adds more 10G SFP+ density. Pick 1420 when those ceilings bind — do not invent a firewall-only story to justify the cheaper SKU.
Lock PA-1400 metrics on the RFQ, 6 steps
Quick Answer: Features → Threat Prevention → IPsec if VPN → sessions → PAN-OS date → calculator check.
- Step 1 — List features that stay on day one — App-ID, Threat Prevention subscriptions, WildFire, DNS Security, URL, IPsec VPN — if enabled, it belongs in the sizing row.
- Step 2 — Circle Threat Prevention on the PA-1400 PDF — PAN-OS 12.1 appmix: 4.5 Gbps (PA-1410) or 6.2 Gbps (PA-1420). Strike firewall-only 8.5 / 9.5 Gbps for award math.
- Step 3 — Add IPsec if VPN binds — Lock 4.1 Gbps (PA-1410) or 5.6 Gbps (PA-1420) when tunnels are in scope.
- Step 4 — Write CPS and session ceilings — Put new sessions/sec and concurrent sessions beside Gbps on the RFQ.
- Step 5 — Attach datasheet page and PAN-OS train — Require every bidder to cite the same named row and software/datasheet date.
- Step 6 — Cross-check headroom with the calculator — Run peak bandwidth + VPN share through /firewall-sizing-calculator.html; method detail on the NGFW companion article. Mbps pending confirmation.
Small first step: open your dated PA-1400 Series PDF. Highlight Threat Prevention and IPsec. If the RFQ still cites only “firewall throughput,” rewrite that line before you compare price.
Who must use Threat Prevention — who can simplify?
Quick Answer: Branch with Threat on + VPN: deep rows mandatory. Low-VPN segments: still ban firewall-only awards.
Internet or campus edge with Threat Prevention subscriptions and IPsec. Threat Prevention (4.5 / 6.2 Gbps) and IPsec (4.1 / 5.6 Gbps) bind design. Size HA so failover does not strand sessions. Firewall-only is never enough if Threat and VPN are planned.
Internal segmentation with App-ID + IPS, limited VPN. Threat Prevention may bind — still print feature names on the RFQ so sellers cannot substitute the 8.5 / 9.5 Gbps firewall line.
- Fit: any PA-1410 / PA-1420 RFQ naming Gbps; equal-BOM multi-vendor bake-off; buyers who landed on datasheet queries with no useful click.
- Not fit: desktop PA-400 class; PA-3400+ chassis needs; already-measured production PA-1400 with proven Threat Prevention headroom.
PA-1400 datasheet traps on RFQ
Quick Answer: Award on firewall-only, ignore IPsec, skip sessions, undated PDF.
| Trap | What happens | Fix |
|---|---|---|
| Award on 8.5 / 9.5 Gbps FW | Threat-on collapse | Threat Prevention 4.5 / 6.2 |
| Ignore IPsec row | VPN kills capacity | 4.1 / 5.6 Gbps IPsec |
| Gbps only | Session exhaustion | Add sessions/sec |
| Use average Mbps | Peaks drop sessions | 95th percentile + headroom |
| No PDF / PAN-OS date | Stale row | Page + train on RFQ |
| Mix PA-1410 with PA-1420 math | Wrong ceiling | Name exact MPN on every line |
Cross-brand comparisons still need the same named row — open the NGFW datasheet-vs-real method before you mix Palo Alto Threat Prevention with another vendor’s firewall headline.
Frequently Asked Questions
Quick Answer: A tender BOM is the issuer's pricing baseline: same lines, same units, same licence years. Bidders answer with a deviation table, and the committee compares lines, not totals.
Default to Threat Prevention appmix — 4.5 Gbps on PA-1410, 6.2 Gbps on PA-1420 (public PA-1400 Series datasheet, PAN-OS 12.1). If site-to-site or remote-access VPN binds capacity, also lock IPsec (4.1 / 5.6 Gbps). Do not award on firewall-only appmix (8.5 / 9.5 Gbps). Mbps pending confirmation — re-check your PDF and software train.
Firewall appmix measures forwarding with a lighter inspection mix. Threat Prevention includes App-ID, IPS, antivirus, antispyware, WildFire, DNS Security, file blocking, and logging under the same appmix label. Same chassis, deeper test — the Threat Prevention row is the procurement metric. See the companion NGFW method article for the general rule.
When VPN is in the design (branch HA, hub spoke, remote access), IPsec Gbps often binds before Threat Prevention alone. Put both named rows on the RFQ line. If the site is pure internet edge with no tunnel budget, still ban firewall-only awards.
Use Threat Prevention and sessions: PA-1410 ≈ 4.5 Gbps TP / 945k sessions; PA-1420 ≈ 6.2 Gbps TP / 1.4M sessions. Port density and SSD differ too — freeze those on the specs page; this page only freezes the metric names.
New sessions/sec (100k / 140k) and concurrent sessions (945k / 1.4M) beside Gbps. Bandwidth can look fine while the session table is exhausted. Mbps and session figures pending confirmation on dated datasheet.
The specs page freezes ports, PoE, SKU stem and optics BOM. This page answers which Threat Prevention / IPsec rows to lock for sizing and award. Use both; for the cross-brand method, open the NGFW datasheet-vs-real article and the firewall sizing calculator.
References
Quick Answer: Buyer behaviour figures come from the G2 and TechnologyMatch 2026 surveys; tender scale from DoNews award tracking for the first seven months of 2026. Checked 21 October 2026.
Key Takeaway
Key Takeaway: Size and RFQ PA-1410 / PA-1420 on Threat Prevention (4.5 / 6.2 Gbps) — and IPsec (4.1 / 5.6 Gbps) when VPN binds — not firewall-only appmix (8.5 / 9.5 Gbps). BENQUAN GLOBAL LIMITED supplies PA-1400 series with competitive pricing for equal-BOM RFQs that name the same datasheet rows; Mbps pending confirmation.