Veeam also automatically uses network-level encryption for any connection with Veeam Cloud Connect service providers. Network transport encryption should be used if the network between two backup infrastructure components is untrusted or if the user desires to protect Veeam traffic across the network from potential network sniffing or “man in the middle” attacks.īy default, Veeam Backup & Replication automatically encrypts communication between two nodes if either one, or both, has an interface configured (if used or not) that is not within the RFC specified private use IPv4 address space (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16). The key has a one-time use and it’s discarded once the session is completed.
The two components then establish an encrypted connection between each other using this key, and all communications between these two components for that session are then encrypted with the key.
Whenever two backup infrastructure components need to communicate with each other over the IP network, a dynamic key is generated by the backup server and communicated to each node over a secure channel. Network encryption in Veeam Backup & Replication is controlled via the global network traffic options. Network rules Network transport encryption This site uses Just the Docs, a documentation theme for Jekyll.
