One of the most important aspects of XdbE Architecture is system security. As XdbE core stores a lot of user data we should design the system in such a way as not to allow unauthorised data insertion (data poisoning) into the system or mailcious data change. Also we should not allow anyone from outside the XdbE Network to use service channels or to manipulate the network in any other way (DoS attacks etc.).
My approach here is to apply symmetric encryption to all the traffic inside the network and to all the traffic from an external network with no exception. The unique encryption key (more than 128 bit) will be used for every pair of servers within the XdbE Network itself. Maybe you want to ask why we won’t use asymmetric (public-private key) encryption. The asymmetric encryption is much slower and we can’t use it to encrypt all the messages. Actually we will use that kind of encryption but only for signature service impacting messages (like configuration change request).