Skip to content 
As enterprises move mission-critical workloads to the cloud, the method of connecting private WAN environments to SaaS/PaaS providers has become a pivotal architectural decision. Relying on “best-effort” Internet routing introduces unpredictable latency and security vulnerabilities which are best overcome with the use of private interconnections.
With private interconnections, the type of required NAT (Network Address Translation) and the location of the NAT function will impact the design quality and the size of the security attack surface. This white paper outlines a framework for transitioning to deterministic, private transport, focusing on three distinct architectural scenarios:
Scenario 1: Customer-Hosted NAT (On-Premises) This model provides the enterprise with maximum sovereignty. By hosting NAT devices at internal hub locations, organizations maintain full control over complex NAT operations and large-scale session management.
