Three concurrent SD-WAN engagements in banking and a state legislature, delivered through the practice’s review gate — see the SD-WAN portfolio. Before any of them, a zero-trust overlay onto a three-hundred-vehicle municipal fleet: the fire and rescue mobile gateway program, where the overlay went on top of transport that already worked and existed to carry policy, segmentation and steering rather than connectivity.
SD-WAN is sold as a simplification and delivered as a routing problem wearing a controller. Moving path selection from a protocol outcome to a policy decision is a real improvement: the business intent becomes something you can state directly rather than something you approximate with metrics and route maps.
The cost of that is blast radius. A conventional routing mistake is usually local and usually visible where it was made; a policy mistake in an overlay is applied everywhere the controller reaches, at once. Which puts SD-WAN in the same governance category as orchestration and automation rather than in the same one as traditional WAN design, and is why the routing-configuration review sat in front of production rather than after it.
Applied in
- SD-WAN Portfolio — Banking and State LegislatureThree concurrent SD-WAN engagements in regulated and public environments, with the low-level design at revision 2.0 and every configuration passing a routing review before production.
- Fire & Rescue Mobile Gateway and SD-WAN OverlayThree hundred apparatus turned into routed nodes on the enterprise network — dual carriers on private APNs, head-ends behind two providers, and a zero-trust overlay behind a firewall virtual system built for the fleet.
Career
See also
Also searched as
- zero trust
- ZTNA
- microsegmentation
- least privilege network
- SASE
- SSE
- secure service edge
- cloud-delivered security
- SDN
- software-defined networking
- software-defined WAN
Compliance-driven isolation and per-tenant policy, designed under regulatory constraint before the vocabulary existed.