Guide, 12 Nov 2026, read 12/13 Nov 2026
One contract and one console cost less to run, a split SSE plus SD-WAN buy gives you more choice
What the choice changes in practice
The architecture argument for one vendor or two is mostly settled by what you will have to staff. I have run migrations on both models. The single-vendor build was faster to cut over. The split build was easier to defend in a vendor review and harder to troubleshoot at two in the morning.
Count four things before comparing features: contracts, consoles, support queues and renewal dates. A split buy means two of each, and the renewal dates drift apart unless you align them in the first order.
How the vendors publish the SD-WAN piece
The table lists what each vendor's own pages say about where branch SD-WAN sits. It is a statement of packaging, not a verdict on quality.
| Vendor | Branch SD-WAN as published | Console as published |
|---|---|---|
| Cato Networks | Part of Cato SASE Cloud with SSE, ZTNA and FWaaS; branch sites use a Socket or vSocket (Cato states) | Cato Management Application (CMA), one console (Cato states) |
| Cisco | Catalyst SD-WAN or Meraki MX, separate from the Secure Access subscription | Catalyst SD-WAN and Secure Access can be managed together in Cisco Cloud Control; Meraki SD-WAN uses its own dashboard |
| Zscaler | Zero Trust SD-WAN is a standalone item on the pricing page and needs a Zscaler Edge appliance | Not stated on the pages read |
| Forcepoint | Secure SD-WAN and NGFW appliances | Secure Management Console, a separate console from the cloud security portal on the pages read |
| Palo Alto Networks | Prisma SD-WAN is a separate product | Linked to Prisma Access through a CloudBlade thin client |
| Arista VeloCloud | SD-WAN edition subscriptions; SSE from partners including Zscaler, Netskope and Check Point | VeloCloud Orchestrator; ETM branch security announced 21 Jul 2026 for general availability in Q4 2026 |
What one contract buys you
Cato states that networking and security share context in one platform, managed from the CMA. Fortinet states that FortiSASE runs on one operating system with one agent and a single console. Open Systems says its SD-WAN and security service edge are built as one platform with one policy. Those are vendor claims and I treat them as the vendor's description, not as test results.
The procurement gain is concrete anyway. One purchase order, one support contract, one set of service credits. If the SD-WAN and the inspection service are from the same company, nobody can point at the other vendor during an outage.
Cisco shows that even inside one vendor the answer depends on the product. Cisco states that Catalyst SD-WAN and Secure Access can be managed together in Cisco Cloud Control, while Meraki SD-WAN stays in its own dashboard. So "one console" depends on which SD-WAN product the branch runs. Check the product name on every branch line of the quote.
What a split buy costs you
Cisco's own page says Meraki SD-WAN is managed in its own dashboard, a different console from Secure Access. Zscaler lists Zero Trust SD-WAN and Device Segmentation outside its two platform bundles, sized separately. That is two line items and, in Cisco's Meraki case, two places to build policy.
The split buy is not wrong. If you already own SD-WAN hardware under a term you cannot exit, buying SSE alone saves you from paying for the overlap. In a customer story, BorgWarner replaced branch MPLS backhauling with the Zscaler and Aruba EdgeConnect integration, and Zscaler's own SD-WAN is described there as a future step.
The cost shows up in change control. Every branch rule that touches both layers needs two approvals, or one engineer with rights in both consoles.
Contract terms to compare
Ask for the support terms of each product separately. iboss publishes standard support as live 8am to 8pm ET on weekdays, with 24x7 live support in a higher package. A split buy can put your SD-WAN on 24x7 and your SSE on business hours without anyone noticing until the first weekend outage.
Ask who owns a fault that sits between the layers. Ask for the SLA of each layer and check whether either covers the link between the branch device and the first inspection point.
Align renewal dates in the first order. If SSE renews in March and SD-WAN in September, each renewal is negotiated with the other as a switching threat, and the vendor knows it. Co-term both contracts at signing, and ask for the same notice period and price-increase cap on both.
Operations that stay the same either way
Neither model removes the work of mapping sites to policy, cleaning up old firewall rules or fixing DNS. Single-vendor does not mean single-pass or simple; it means one escalation path. Plan the same site inventory, the same pilot sites and the same rollback either way.
One more check: the vendor's own counts of what is bundled shift between pages. Read the order form, not the home page.
A rule I use
Choose one vendor when the branch count is above roughly 50, the network team is under five people and the SD-WAN contract is up for renewal within 18 months. Choose a split buy when SD-WAN hardware is under a term you cannot exit, when different teams own network and security, or when a regional requirement forces a different SSE. Write the owner of each console on the first page of the runbook.
Count your change volume too. If branch policy changes weekly, two consoles cost engineer hours every week, and that outweighs most license differences.
Sources
- Cato Networks, home page, read 12 Nov 2026
- Cato Networks, firewall as a service, read 12 Nov 2026
- Fortinet, FortiSASE product page, read 12 Nov 2026
- Cisco, Secure Access data sheet, read 12 Nov 2026
- Cisco Meraki, SD-WAN overview, read 12 Nov 2026
- Zscaler, pricing page, read 12 Nov 2026
- Forcepoint, Secure SD-WAN, read 12 Nov 2026
- Zscaler, BorgWarner customer story, read 12 Nov 2026
- Arista, ETM for VeloCloud SD-WAN press release, read 12 Nov 2026
- iboss, service level agreement, read 12 Nov 2026
- Open Systems, home page, read 12 Nov 2026
- Palo Alto Networks, Prisma Access licensing guide, read 12 Nov 2026
Last reviewed 12 Nov 2026.