Encryption options for at rest and in-transit data

Appian Cloud data is encrypted at rest by default. For in-transit, I would typically recommend a VPN tunnel to the other Cloud system to ensure a secure connection.

Hi Justin, thanks for your reply. I had a couple of questions:

when you say, Appian Cloud data is encrypted at rest by default - what data are you talking about. Is it the data in the Appian engines/kdbs?Looks like the kdb data is stored in a proprietary format but not encrypted.
community.appian.com/.../is-the-kdb-database-encryptyed-at-some-level-we-have-a-security-review-regardin

any idea as to what version of the kdb does APPIAN use? The latest version seems to be kdb 3.6. does appian upgrade to the latest release on cloud immediately?

All of the data for the Cloud instance is encrypted, not just the KDB. You're right that otherwise the KDB is a proprietary format.

As to the version of KDB, I believe they are on 3.3 per the licensing output. However, Appian upgrades the latest version of their software (Appian 18.x) to the latest version on their Cloud platform shortly after release, and scheduling is coordinated with the system owner/customer.

Are we able to setup a SSL VPN connection? I see the documentation says only IPSec VPN Connection.

The AWS MSSQL server is going to be configured to accept only encrypted connections (SSL/TLS).

Updated Questions:
1. If we setup a IPSec VPN connection between APPIAN CLoud and AWS MSSQL. And AWS MSSQL accepts only encrypted connections (SSL/TLS). Are we still able to connect?

2. If we are not able to connect using IPSec VPN, will setting up a SSL VPN connection help? I see the documentation says only IPSec VPN Connection, can we setup a SSL VPN connection between APPIAN cloud and remote resources.

3. For IPSec VPN connection - is it tunnel or transport encryption ?