Serv-U Gateway works with one or more Serv-U FTP Servers to protect against data at rest in DMZ network segments. This is a common way meet PCI-DSS requirements when working with file transfer servers. Serv-U Gateway is deployed in your DMZ. It accepts (and "terminates") incoming file transfer connections (FTP, SFTP, FTPS, HTTP and HTTPS) from the Internet and streams commands and data through to an internally-deployed DMZ over a secure, proprietary channel. No connections are ever made from Serv-U Gateway to your internal network; all connections are made inbound to Serv-U Gateway. No data is ever resident in your DMZ or on the Serv-U Gateway server. Configurations are maintained on the internal Serv-U servers and pushed out to Serv-U Gateways at start-up (and periodically as changes are made to live systems). Monitoring of Serv-U Gateways also happens from existing Serv-U management consoles; all connection information (both local and gateway) can be watched from a single pane. Like Serv-U itself, multiple instances of Serv-U Gateway may be clustered for high availability. From an end-user perspective, Serv-U Gateway looks exactly like a Serv-U server. In other words, it works with any existing FTP client, SFTP client, FTPS client, web browser, or mobile device supported by Serv-U itself.
|License||Free to try|
|File Size||5.2 MB|
|Operating System||Windows Windows 2003 Windows Server 2008|
|System Requirements||Serv-U FTP Server|