A Remote Server connection combines the remote service's authentication, transport encryption, and access permissions. Use encrypted protocols and keep certificate or host-key verification enabled. The available settings depend on the provider.

Network Security

Cloud Storage

Cloud storage API connections use HTTPS. The remote provider's endpoint and the connection configuration determine the negotiated TLS version and cipher. See the provider's setup page for authentication and firewall requirements.

Native content collaboration integrations use the provider's HTTPS API. Egnyte and ShareFile use the file transfer protocols documented on their provider pages.

Protocol-based File Transfer System

Protocol-based Remote Servers support SFTP, FTP/FTPS, and WebDAV. Configure the protocol and encryption mode to match the remote server; a port number alone does not establish which protocol is running.

SFTP

SFTP runs over SSH, normally on port 22. The server host key identifies the remote server. Verify an unexpected host-key change with the server operator before accepting the replacement. SSH negotiates algorithms supported by both sides; see Ciphers.

AS2

AS2 uses its own partner configuration. Transport encryption and message signing or encryption are separate settings; follow the AS2 setup instructions for the partner connection.

FTPS (Explicit)

Explicit FTPS begins with an FTP control connection, normally on port 21, and upgrades it to TLS before authentication. Select Require SSL (Explicit) when this is the remote server's required mode. FTPS uses separate control and data connections; it is not HTTPS.

FTPS (Implicit)

Implicit FTPS begins TLS immediately, normally on port 990. Select Require SSL (Implicit) for a server using this mode. It differs from explicit FTPS in when TLS begins, not in whether credentials are encrypted.

FTP

Plain FTP does not encrypt credentials, commands, or file contents. Prefer a required FTPS mode. Use If Available permits an unencrypted connection when the server does not support TLS, and Never use disables TLS. Encrypting a file with GPG does not protect the FTP login or commands.

WebDAV

WebDAV over HTTPS encrypts the connection, normally on port 443. HTTP, normally on port 80, does not encrypt credentials or file contents. Use HTTPS whenever the remote service supports it.

Self-Signed SSL Certificates

For TLS connections, keep verification of the remote certificate's hostname, validity, and trust chain enabled. Allowing a non-matching or untrusted certificate bypasses checks used to establish the server's identity. A connection can still be encrypted while lacking that identity assurance. Ask the server operator to provide a valid certificate rather than disabling verification to work around an unexpected certificate failure.

Authentication Security

Remote Server credentials, including passwords, keys, and tokens, are encrypted while stored within Files.com. Grant the remote identity only the access the integration requires, and configure Files.com folder permissions separately for users accessing mounted files.

Remote Server Security