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/public-cloud/databases/concepts-security-overview.md.
Skip to content

Security Overview for Public Cloud Databases

View as Markdown

Public Cloud Databases security overview

Objective

In addition to the responsibility model for Public Cloud Database services, this security fact sheet aims to describe the security features and functions associated with the service. It also describes best practices that customers can adopt to secure their databases.

1.Certifications

  • ISO/IEC 27001
  • ISO/IEC 27701
  • ISO/IEC 27017
  • ISO/IEC 27018
  • HDS
  • SOC 1 type 1
  • SOC 2 type 1
  • CSA type 1
  • C5 type 1

1.1 Obtaining certification reports

Certificates and audit reports are not published in this documentation. As an OVHcloud customer, you can request access to them from your OVHcloud sales contact. Access to some reports may be subject to conditions.

The list of OVHcloud certifications is available on the certifications page.

2.Best pratices to be deployed on the service

2.1 Recommendations once the service is delivered

Once you have followed these first steps to subscribe your service and reset the default password communicated to access the service, you must restrict incoming connections to your service by declaring only the necessary IP addresses or CIDR blocks in the authorised IPs list: any connection from an address that is not on this list is refused.
You can also activate a private connection by using the vRack option.

2.2 Vulnerability scans

You are authorised to perform vulnerability scans on the service you have subscribed to. OVHcloud does not need to be informed beforehand.
Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
You are not authorised to use your service to scan other infrastructures.

3.SLA

SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
SLA for the Business/Production range in Single AZ are 99,90%.
SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
SLA for the Production range in Multi AZ are 99,95%.
SLA for the Advanced range in Multi AZ are 99,99%.
The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation.

4.Backups

4.1 Technical backups

Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request.

4.2 Customer data backups

Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the database service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at this link.
Customer data backup health status is checked daily by OVHcloud.
If you need to restore your data using a backup, you can follow this guide and create a new service for this purpose.

5.Logs

SourceContentDocumentation
OVHcloud ConsoleLogs of interactions made by admin, technical or billing contacts in the OVHcloud Console and services they have access to, using API calls.- List of API calls done with your account
- List of API calls done on services you have access to
-
Service1000 last logs for service usageSee the Logs view of the Observability tab in the OVHcloud Console
- or via API (for Kafka service as an example /cloud/project/{serviceName}/database/kafka/{clusterId}/logs
- /cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs

5.1 Content of the PostgreSQL logs

The service logs contain what PostgreSQL writes, without any redaction. With the default configuration:

  • Slow statements: log_min_duration_statement is set to 1000 ms. Every statement that runs longer is logged with its text and the values of its parameters (DETAIL: Parameters: $1 = '<value>').
  • Errors: the statement that caused an error is logged (log_min_error_statement is set to error), and some error messages quote the offending value, for example invalid input syntax for type integer: "<value>" or DETAIL: Key (email)=(<value>) already exists.

To reduce what the logs can contain, set these two advanced parameters:

  • pg.log_min_duration_statement to -1: slow statements are no longer logged.
  • pg.log_error_verbosity to TERSE: the DETAIL, HINT, QUERY and CONTEXT lines of error messages are no longer logged.

Both are applied with a configuration reload, without restarting the service. The main error message and the text of the failing statement remain logged. Set both parameters with the following API call:

Database users, including the administrator user of the service, cannot change log_statement or log_min_duration_statement, whether for their session or for a role (permission denied to set parameter). You can check the values in force with:

SELECT name, setting, source FROM pg_settings WHERE name LIKE 'log_%';
SELECT setdatabase, setrole::regrole, setconfig FROM pg_db_role_setting;

6.API

NameCapacityLink
OVHcloud Console and serviceManage customer accounts and services on which each account has access rights.

7.Accounts - User

7.1 Control plane

Using your customer account on the OVHcloud Console, you are able to manage your service using three different contacts.
OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services.

To enforce security access to your account on the OVHcloud Console, we recommend activating a two-factor authentication mechanism or SSO(Single Sign-On) authentication.

You can also create your own IAM policy on the service, with a user interface or via API, and manage your users and groups.
You can troubleshoot your IAM policy configuration and analyse actions by using API calls to get logs.

7.2 Data plane

Once a VM is created by OVHcloud, on which the customer Database engines run, a TLS certificate is generated and used by the customer to access their database.

To protect yourself against server impersonation, configure your clients to verify the certificate presented by the service. The certification authority to trust depends on the engine: see 7.4.

7.3 Passwords of database users

The password of a database user is shown only once: in the response to its creation or to a password reset, in the OVHcloud Console and in the API. It cannot be displayed again afterwards: getting a user with the API never returns its password. To reset a password, use the following API call:

Each reset generates a new password and the previous one stops working immediately. The response carries no operation identifier. If you lose the response to a reset, try to connect with the previous password. If it is refused, the reset was applied: run a new reset to get a password you can use.

On PostgreSQL, creating a user or resetting its password writes neither the password nor its SCRAM verifier to the service logs.

7.4 Encryption in transit

7.4.1 Ports, protocols and TLS versions

EnginePortProtocolUnencrypted connections refused by the serverTLS versions acceptedServer certificate signed by
PostgreSQLSpecific to each service, shown in the Control Panel and the APIPostgreSQL protocolYesTLS 1.2, TLS 1.3The CA of your Public Cloud project
MySQLSpecific to each service, shown in the Control Panel and the APIMySQL protocolNo, see belowTLS 1.2, TLS 1.3The CA of your Public Cloud project
MongoDB27017MongoDB protocol. The mongodb+srv:// URI finds the nodes through DNS SRV recordsYesTLS 1.2, TLS 1.3A public certification authority
ValkeySpecific to each service, shown in the Control Panel and the APIValkey protocol (RESP)YesTLS 1.2, TLS 1.3A public certification authority

TLS 1.0 and TLS 1.1 are refused by all four engines.

MySQL: the server accepts unencrypted connections. The connection URI provided in the Control Panel and the API contains ssl-mode=REQUIRED, so a client that uses it connects with TLS. A client that does not require TLS can connect without encryption: the passwords are not sent in clear text, but the queries and their results are. To have the server refuse unencrypted connections for a user, run the following statement with the administrator user of the service:

ALTER USER '<username>'@'%' REQUIRE SSL;

The user's unencrypted connection attempts are then refused with an Access denied error. The setting is kept when the user's password is reset with the API. It applies to one user only: run it again for each user you create.

7.4.2 Verifying the identity of the server

Encryption alone does not protect you against a server impersonating your service. Configure your clients to verify the server certificate and its hostname:

EngineClient settingGuide
PostgreSQLsslmode=verify-full and sslrootcert set to the CA certificate of your projectSecure the TLS connection
MySQL--ssl-mode=VERIFY_IDENTITY and --ssl-ca set to the CA certificate of your projectConnect using the CLI
MongoDBtls=true, already present in the URI provided. Certificate verification is enabled by default in MongoDB drivers: do not disable it with tlsAllowInvalidCertificates or tlsInsecureConnection strings
ValkeyThe valkeys:// scheme (or the --tls option), with certificate verification kept enabledConnect using the CLI

For PostgreSQL and MySQL, download the CA certificate of your project from the Certificate field of the Connection information section, in the Dashboard tab of your service, or with the API (route /certificates of your service). For MongoDB and Valkey, there is no certificate to download: the certification authority is already in the trust store of your system.

8.Features and options available at service delivery

8.1 High availability

Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan.

8.2 Data encryption

8.2.1 Encryption made by the OVHcloud teams

All network traffic on the infrastructure managing the Databases service is encrypted. Databases volumes are also encrypted with a unique key specific for each customer project.
These operations are made, by default, by the OVHcloud operation team.

Info

Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud.

For a MongoDB engine:

  • Nodes: service instances and the underlying VMs use full volume encryption using LUKS with a randomly generated ephemeral key for each instance and each volume. The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
  • Backups: backups are encrypted with AES-256 and a randomly generated RSA 4096 key before being sent to Object Storage. In every region, Object Storage then adds its own server-side encryption (SSE-OMK) to the backup buckets: each object is encrypted with its own key, derived and managed by OVHcloud.

For all the databases engines such as MySQL, PostgreSQL, Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage:

  • Nodes: service instances and the underlying VMs use full volume encryption using LUKS with a randomly generated ephemeral key for each instance and each volume. The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key.
  • Backups: backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key.

8.2.2 In-use encryption on client side

Info

Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud.

Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the database.
Client-Side Field Level Encryption (FLE) is an in-use encryption capability that enables a client application to encrypt sensitive data before storing it in the MongoDB database. Sensitive data is transparently encrypted, remains encrypted throughout its lifecycle, and is only decrypted on the client side.

8.3 CVE monitoring

The OVHcloud operation team in charge of the maintenance of Public Cloud Databases services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check, etc.

We are also in constant communication with the MongoDB team, to provide a fast and smooth transition to the latest security version of MongoDB.

8.4 vRack option

You can activate the vRack option at the subscription step or afterwards and have your private network for your Database project. The configuration of your private network can be done by following this link.

8.5 HDS option

The HDS option can be activated on the service.
This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
The subscription to the Business support level is mandatory, at least to maintain necessary requirements.

8.6 Maintenance

OVHcloud maintenance operations apply to the components of the service: the database engine, the operating system and the versions of the extensions installed on the service. They do not modify your user configuration: users, roles, memberships, privileges and ownerships. When a maintenance operation updates an extension you use, the objects of this extension are updated to its new version.

Each maintenance operation is listed with a short description, its status (for example PENDING or APPLIED) and its scheduled and applied dates, in the OVHcloud Console and with the API. The routes below are for PostgreSQL; for another engine, replace postgresql with its name.

To get the IDs of the service's maintenance operations, use the following API call:

To display the description, status and dates of a maintenance operation, use the following API call:

9.Reversibility

You can import and export your data with the standard tools of each engine. The reversibility policy of each product line lists the features you can migrate, with their formats and tools:

EngineExport and import toolsReversibility policy
PostgreSQLpg_dump and pg_restoreManaged Relational Database
MySQLmysqldumpManaged Relational Database
MongoDBmongodump and mongoexportManaged Document Database
ValkeyA Valkey client, for example SCAN then DUMP on each keyManaged In-Memory Database

The automated backups made by OVHcloud cannot be downloaded. To export the data of a backup, restore it to a new service, then export it with the tools above.

Export your data before deleting your service: see 9.1.

9.1 Erasure of customer data

Once you destroy your Public Cloud project (your Database project) in the OVHcloud Console, all allocated resources are released automatically, including used encryption keys.
As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after.

For MongoDB, deleting a service immediately deletes all its data, including its backups in every region where they are stored, on every plan (Production, Advanced).

10.Questions frequently asked in security audits

10.1 Encryption

QuestionAnswer
Are the nodes and the backups encrypted at rest?Yes, on every plan. See 8.2.1.
Can I bring my own encryption keys?No. See 8.2.1.
Is data encrypted in use?Only on MongoDB Advanced plans, with Client-Side Field Level Encryption. See 8.2.2.
Which TLS versions are accepted?TLS 1.2 and TLS 1.3. TLS 1.0 and TLS 1.1 are refused. See 7.4.
Does the server refuse unencrypted connections?Yes on PostgreSQL, MongoDB and Valkey. On MySQL, only for the users you configure with REQUIRE SSL. See 7.4.
How do I verify the identity of the server?See 7.4 for the client setting of each engine.

10.2 Access and authentication

QuestionAnswer
Who can connect to the service?Only the IP addresses and CIDR blocks you authorise. See 2.1.
Can a password be read again after its creation or reset?No. See 7.3.
How is access to the Control Panel and the API secured?With two-factor authentication, SSO and IAM policies, which you set up yourself. See 7.1.

10.3 Network

QuestionAnswer
Which ports and protocols are used?See 7.4.
Can the service be reached through a private network only?Yes, with the vRack option. See 8.4.
Can I run vulnerability scans on the service?Yes, without informing OVHcloud beforehand. See 2.2.

10.4 Backups

QuestionAnswer
How often are backups made, and where are they stored?It depends on the engine and the plan. See 4.2.
Can I download the backups made by OVHcloud?No. Restore a backup to a new service, then export its data. See 9.

10.5 Deletion and reversibility

QuestionAnswer
How do I export my data?With the standard tools of each engine. See 9.
What remains after a service is deleted?See 9.1.

10.6 Logs and maintenance

QuestionAnswer
Which logs are available?See 5.
Can the PostgreSQL logs contain data?Yes, in slow and failing statements. See 5.1 for the parameters that reduce what the logs contain.
Can a maintenance operation change roles or privileges?No. See 8.6.
How do I know which maintenance operations were applied?They are listed in the Control Panel and the API. See 8.6.

10.7 Certifications

QuestionAnswer
Which certifications cover the service?See 1.
How do I obtain the certification reports?See 1.1.
Is the service covered by the HDS certification?See 8.5 and the list of HDS-certified products.

Go further

Public Cloud Databases documentation

Visit our dedicated Discord channel: https://discord.gg/ovhcloud. Ask questions, provide feedback and interact directly with the team that builds our databases services.

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Was this page helpful?