For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-overview.md.
Skip to content

What is Encryption at Rest on a dedicated server?

View as Markdown

Understand what Encryption at Rest protects on an OVHcloud Dedicated Server, how disks are encrypted and unlocked, and who manages the keys

Objective

Encryption at Rest encrypts all the disks of your OVHcloud Dedicated Server in hardware. This guide explains what Encryption at Rest protects, how it works and what it changes for you.

Info

OVHcloud manages the passphrase that unlocks the disks. The encryption key stays inside each disk and is never sent to you. You do not manage the passphrase, and it is never sent to you either. Using your own keys (Key Management Service, Secret Manager or BYOK) is not available.

Requirements

Instructions

This section describes how Encryption at Rest works, what it protects and the points to know before you enable it.

How Encryption at Rest works

The drives perform the encryption themselves. All data written to the disks is encrypted before it is stored, so it cannot be read without the disk keys.

At each boot, the disks are unlocked automatically before your operating system starts. You do not need to enter anything, and your server returns to service without any action from you.

What Encryption at Rest protects

Encryption at Rest protects data on a disk that is physically removed:

  • from your server.
  • from the datacentre.

What Encryption at Rest does not protect

Encryption at Rest does not replace the security measures you apply to your system. It does not protect:

  • data while your server is running: once the disks are unlocked, the operating system reads them in clear text.
  • your operating system or applications against an attack, including online attacks.
  • data in transit on the network.

Encryption at operating system level (for example LUKS on Linux or BitLocker on Windows) adds a layer whose keys you manage, but it does not protect against these risks either. Follow the security practices that apply to your workloads.

Good to know

Read these points before you enable Encryption at Rest:

  • All disks or none: Encryption at Rest applies to every disk of the server. You cannot select disks one by one.
  • Opt-in: Encryption at Rest is never enabled by default, including on a new server. You enable it from the or the OVHcloud API.
  • Data erasure: enabling Encryption at Rest erases all the data on the server, and you must then reinstall the operating system. Back up your data first.
  • Disabling: you can disable Encryption at Rest from the OVHcloud Console or the OVHcloud API. Disabling performs a cryptographic erase of the disks, and you must then reinstall the operating system.
  • Backups: your backup tools (Veeam, Restic, etc.) keep working. They read your data as the operating system sees it.
  • Pricing: Encryption at Rest is included, at no extra charge.

Go further

Enable or disable Encryption at Rest on a dedicated server

Manage Encryption at Rest on a dedicated server with the API

Encryption at Rest requirements and limitations

Encryption at Rest on dedicated servers: FAQ

Join our community of users.

Was this page helpful?