Why encrypt your VMs?
A VM leaves its data in several places: on the disk of the server that runs it, in the copies of the distributed storage, in the replicas of your BCP or DRP and in your backups. Without encryption, each of these places can expose it: a replaced disk, a forgotten copy, a poorly protected backup.
On the PYSOFT cloud, this data is encrypted before it leaves the server that runs the VM. This is often required for health, financial or personal data, and it helps meet the requirements of Law No. 18-07 on the protection of personal data.
AES-256 encrypted disks
Tick "encrypted" when you create the VM: the hypervisor encrypts every sector of its disk with AES-256-XTS, transparently. The VM's operating system sees no difference: nothing to install, nothing to configure.
The volumes you add are encrypted in the same way when they are created, and a VM created from an encrypted image is encrypted automatically.
Copies and backups are encrypted too
Encryption takes place on the server that runs the VM, before any copy is made. The distributed storage servers only receive, copy and write encrypted data. The replicas of your BCP and the link to your DRP recovery site only ever see encrypted data.
Your backups and the continuous data protection (CDP) journal also keep the data encrypted: a restore gives you back an encrypted disk, with its key.
One key per VM, destroyed with it
Each VM has its own key. The platform stores it and only hands it to the hypervisor that runs the VM, over a connection that is encrypted and authenticated on both sides (mutual TLS).
When you delete the VM, its key is destroyed: anything that might remain of its disks on our servers becomes unreadable. Its backups keep their own copy of the key, so that they remain restorable for as long as you keep them.
Memory encrypted by the processor (AMD SEV)
Our hypervisors are equipped with AMD EPYC processors. A VM can run on them with memory encrypted by the AMD security processor (SEV), with a key that the hypervisor does not know: its memory remains unreadable from the server. With SEV-ES, the processor registers are protected as well. SEV-SNP, which additionally protects memory integrity, is under development.
This mode applies to OpenBSD VMs and to Linux VMs prepared for it. What a VM sends to its disk or to the network leaves the encrypted memory: also encrypt the disk inside the VM (a tool is provided for Linux) and your network traffic (TLS, VPN).