For all versions prior to 3.3, there is no encryption done specifically on the contents being transferred. Furthermore, since it doesn’t use REST or Bolt, there is no SSL/https configuration either. Transactions are propagated via transaction logs, which are a binary representation of the data and are not human-readable. However, that does not equate to encryption.
A common way to solve this problem is to implement VPN tunneling between instances, such that the data is transferred through a secure tunnel.
Commencing with 3.3 we would recommend Intra-Cluster Encryption ”’
- Last Modified: 2020-09-15 13:07:09 UTC by Dana Canzano.
- Relevant for Neo4j Versions: 3.0, 3.1, 3.2, 3.3, 3.4.
- Relevant keywords causal-cluster, encryption.