Skip to main content

Securing Data at Rest with IBM Guardium Data Encryption

This topic describes how to secure data on persistent storage (data at rest) in SingleStoreDB with IBM Guardium Data Encryption. This configuration allows you to protect all SingleStoreDB information, including data files, backups, and logs from unauthorized access, including by unauthorized administrative users. The process is also known as Transparent Database Encryption or TDE.

IBM Guardium Data Encryption encrypts all protected SingleStoreDB data with strong encryption. If the encrypted data is obtained in any way by someone without keys to access it, it will be useless. Even the root user on the Linux system running SingleStoreDB can be prevented from accessing the information directly via the files where it is stored, even if they impersonate a user with access by using sudo. Keys can also be revoked to render data inaccessible.

Getting Started

The certification matrix below shows the versions supported for SingleStoreDB and Guardium Data Encryption:

Certification Matrix

Versions

IBM Guardium Data Encryption

4.0.0.0

SingleStoreDB

7.1.x, 7.3.x or newer

Certified OS

RHEL/CentOS 6 or 7 (version 7 is preferred), Debian 8 or 9 (version 9 is preferred)

Process Overview

IBM Guardium Data Encryption is the same product as Thales CipherTrust Transparent Encryption (CTE), formerly known as Vormetric Transparent Encryption (VTE). IBM resells it under the Guardium name. To use IBM Guardium Data Encryption to secure data on persistent storage, follow the process described here for CTE/VTE. IBM Guardium Data Encryption documentation is available here. That documentation also describes the version numbers of CTE/VTE corresponding to each Guardium version.