Secure FTP Server Access

Edited

Introduction

Symplectic maintains FTP servers whose main purpose is to provide a location to which clients can upload data feed files for import into Symplectic-hosted instances of Elements. Several different FTP servers cater to the various geographical locations in which Elements can be hosted by Symplectic:

How to Obtain Connection Credentials 

If you are implementing a data feed against a Symplectic-hosted instance of Elements that requires your files to be uploaded to a Symplectic FTP server, please contact Symplectic support, who will work with you to provide the appropriate access.

FTP Server Security

Ensuring the security of the data you upload to our FTP servers is very important. At Symplectic, we protect your information using a robust encryption system. Please see below for more details.

Secure File Transfer Protocols

Clients have the option to upload files to our FTP (File Transfer Protocol) servers using either the SFTP (SSH File Transfer Protocol) or the FTPS (FTP over SSL/TLS) protocol. Both protocols offer strong encryption mechanisms to safeguard data during transit.

Encryption at Rest

Our FTP servers encrypt all data at rest using AWS volume encryption. This means that even if unauthorized access occurs at the physical storage level, the data remains unintelligible without the proper decryption keys.

Encryption in Transit

When files are transferred to and from our servers, they are transmitted over encrypted connections. Both SFTP and FTPS protocols mandate encrypted connections, adding an additional layer of security to prevent eavesdropping and data interception during transit.

Requests to Process PGP-encrypted Files

Occasionally, we receive requests from clients who wish to upload PGP-encrypted (Pretty Good Privacy) files. However, Elements data import processes do not currently support the decryption of client-side encrypted files, so we cannot support this use case at present.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.