Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > Serv-U to Serv-U Gateway connection security

Serv-U to Serv-U Gateway connection security

Updated November 7, 2018


This article describes the security configurations and protocols used by Serv-U and the Serv-U Gateway connections.

See the Serv-U Distributed Architecture Guide for information about the purpose and timing of these connections.


All Serv-U versions


Serv-U connects to Serv-U Gateway using multiple connections to send configuration data, listen for new connections, and transfer files. Serv-U to Serv-U Gateway connections are encrypted as long as the related listener's protocol is a secure protocol (such as FTPS, SFTP, or HTTPS).

Gateway control channel

Serv-U uses connections to control and monitor the Serv-U Gateway. These connections are implemented as proprietary TCP/IP connections. 

Gateway data channel

All data connections used between Serv-U and Serv-U Gateway use the same protection mechanism as the related listener on Serv-U Gateway.

The Serv-U to Serv-U Gateway connections that handle FTPS and HTTPS connections are protected by SSL/TLS. As a result:

  • SFTP connections are protected by SSH.
  • FTP and HTTP connections are not protected because they use clear text.

The same certificate key lengths and negotiated bit strength apply to the Serv-U to Serv-U Gateway connections.



Last modified