Introduction

Entrust KeyControl has been rebranded as the Entrust Cryptographic Security Platform (CSP) Key Manager.

The Entrust CSP Key Manager continues to provide a comprehensive solution for discovering and managing the lifecycles of cryptographic keys, secrets, certificates, tokens, libraries, protocols, and configurations:

  • The KeyControl Compliance Manager is now the Entrust CSP Compliance Manager. It still integrates with Entrust nShield Hardware Security Modules (HSMs) to protect the master keys for the CSP.

  • KeyControl Vault is now the Entrust Cryptographic Security Platform Vault. The Cryptographic Security Platform Vaults also still integrate with Entrust nShield HSMs to provide an optional HSM root of trust.

Because the Entrust integrations are tested against specific product versions, this guide is still branded as a "KeyControl" integration. It was tested against a pre-CSP version of KeyControl.

Exercise caution when using an Entrust Integration Guide with a product version that does not match the tested version, because your version might not function in exactly the same way.

Entrust cannot guarantee the success of integrations in configurations other than those indicated in the guide. This guide remains on the website for customers using pre-CSP versions of KeyControl.

This document describes the integration of MariaDB with the Entrust KeyControl Database Vault (KMS).

Documents to read first

This guide describes how to configure the Entrust KeyControl Database Vault as a KMS in MariaDB.

To install and configure the Entrust KeyControl Database Vault, see the Entrust KeyControl Vault nShield HSM Integration Guide. You can access it from the Entrust Document Library and from the nShield Product Documentation website.

Also refer to the MariaDB online documentation.

Requirements

  • Entrust KeyControl Vault version 10.2 or later

    An Entrust KeyControl license is required for the installation. You can obtain this license from your Entrust KeyControl Vault and MariaDB account team or through Entrust KeyControl Vault customer support (hytrust.support@entrust.com).

  • MariaDB Server 11.3.2 or later

Entrust recommends that you allow only unprivileged connections unless you are performing administrative tasks.

High-availability considerations

Entrust KeyControl Vault uses an active-active deployment, which provides high-availability capability to manage encryption keys. Entrust recommends this deployment configuration. In an active-active cluster, changes made to any KeyControl node in the cluster are automatically reflected on all nodes in the cluster. For information about Entrust KeyControl, see the Entrust KeyControl Vault Product Overview.

Product configuration

The integration between the MariaDB Server and Entrust KeyControl Vault has been successfully tested in the following configurations:

Product Version

MariaDB Server

11.3.2

Entrust KeyControl Vault

10.2

Red Hat Enterprise Linux 8.9

Kernel: Linux 4.18.0-513.18.1.el8_9.x86_64