# How will adding an SD-WAN solution affect our current firewall setup?

We just finished a fairly painful firewall deployment, and I am not eager to touch our firewall config again anytime soon. A partner is recommending we look at Bigleaf for internet optimization/failover. Still, I need to know upfront: does this kind of solution typically sit in front of the firewall or replace it, or does it work alongside whatever security setup you already have? Trying to avoid a scenario where "adding SD-WAN" turns into "redo our whole network security posture."

##### Post Metadata
- Posted at: about 2 months ago
- Net upvotes: 2


## Comments
### Comment 1

Understandable to be gun-shy after a firewall deployment, and the good news here is Bigleaf&#39;s whole deployment model is built around not touching that again.

Bigleaf Edge Firewall is now generally available as part of Bigleaf Cloud Connect. You can deploy Bigleaf outside a third-party firewall and keep that firewall in place, or add Bigleaf Edge Firewall for branch stateful security and secure, optimized site-to-site connectivity from a single appliance. The right option depends on whether you want to retain your existing firewall’s security controls or use the Edge Firewall feature set at the branch.

Bigleaf installs on the WAN side of your firewall, not in front of it and not instead of it. Practically: the Bigleaf router sits between your ISP circuits and your Fortinet box, and presents itself to the firewall as a single regular WAN connection. Your firewall doesn&#39;t know or care that Bigleaf is doing anything underneath — it keeps enforcing every security policy, NAT rule, and VPN configuration exactly as it already does today. The traffic optimization (failover, prioritization, the same-IP behavior) all happens transparently between the firewall and the ISP circuits, on Bigleaf&#39;s side of that boundary.

To be precise rather than overpromise: the one thing that typically does need a small touch is updating NAT/VPN rules to reference the new WAN IP block Bigleaf presents, since that&#39;s a new IP range sitting where your ISP&#39;s used to be. That&#39;s a WAN IP update, not a policy rewrite — it&#39;s not the kind of &quot;redo our whole security posture&quot; project you&#39;re trying to avoid, but I&#39;d rather flag it plainly than imply zero touch of any kind. Outside of that, no rule redesign, no re-architecting, and it&#39;s compatible with Fortinet specifically (along with Palo Alto, SonicWall, Meraki, Cisco, and others), so you&#39;re not being asked to second-guess a purchase you just finished making.

Given this is coming through a partner, it&#39;s also worth asking them directly what the actual on-site deployment looks like for your specific Fortinet setup — the mechanism above is the general model, but they&#39;ll know your NAT/VPN specifics.

Choosing a Firewall-Friendly SD-WAN - https://www.bigleaf.net/blog/choosing-firewall-friendly-sd-wan/  — goes deeper into exactly this deployment model and what does and doesn&#39;t need to change.

Can Your Firewall Do This? - https://www.bigleaf.net/resources/bigleaf-vs-firewall-can-your-firewall-do-this/  — useful for understanding what Bigleaf adds versus what your firewall is already handling, since those are different jobs.

##### Comment Metadata
- Posted at: about 2 months ago
- Author title: Digital Marketing Manager




## Related Product
[Bigleaf Networks](https://www.g2.com/products/bigleaf-networks/reviews)

## Related Category
[SD-WAN](https://www.g2.com/categories/sd-wan)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


