Organizations often need to support multiple protocols: web browsers prefer HTTPS, legacy scripts use FTP, and modern apps call REST APIs. The Globalscape Web Proxy can accept all these protocols on the front end while speaking a single, optimized protocol (usually FTPS or HTTPS) to the backend server. This removes the need to open multiple ports on the internal firewall.
Regulatory frameworks require that sensitive data—be it patient records, payment card information, or personal user data—be protected both in transit and at rest. By terminating external TLS connections at the proxy and re-establishing a separate, controlled connection to the backend, the proxy ensures that external parties never directly touch the internal server. This separation is a key control in audit trails and compliance documentation. globalscape web proxy
This architecture is often called a "DMZ proxy deployment." The proxy resides in the demilitarized zone (DMZ)—a semi-trusted network segment—while the actual EFT server containing sensitive data stays safely behind the internal firewall. 1. Enhanced Security via Surface Reduction The most compelling reason to deploy the Globalscape Web Proxy is security. By placing the proxy in the DMZ, your internal EFT server never needs a public IP address or direct internet exposure. Attackers see only the proxy, which is hardened and has no stored credentials or permanent data. This dramatically reduces the attack surface. Even if the proxy is compromised, the intruder gains no direct access to your core file storage or user database. Organizations often need to support multiple protocols: web