Navigator Key Trustee Server 5.10.0

Recommended Hardware and Supported Distributions

Key Trustee Server must be installed on a dedicated server or virtual machine (VM) that is not used for any other purpose. The backing PostgreSQL database must be installed on the same host as the Key Trustee Server, and must not be shared with any other services. For high availability, the active and passive Key Trustee Servers must not share physical resources. See Resource Planning for Data at Rest Encryption for more information.

The recommended minimum hardware specifications are as follows:

• Processor: 1 GHz 64-bit quad core
• Memory: 8 GB RAM
• Storage: 20 GB on moderate- to high-performance disk drives

Key Trustee Server supports the following Linux distributions:

• RHEL and CentOS: 6.4, 6.5, 6.6, 6.7, 7.1, 7.2, 7.3
• Oracle Enterprise Linux: 6.7, 6.8, 7.1, 7.2, 7.3

Cloudera Manager Requirements

Installing and managing Key Trustee Server using Cloudera Manager requires Cloudera Manager 5.4.0 and higher. Key Trustee Server does not require Cloudera Navigator Audit Server or Metadata Server.

SELinux Requirements

SELinux must be disabled for Key Trustee installation and operation. Modify /etc/selinux/config to set SELINUX=disabled and reboot the system for the change to take effect.

umask Requirements

Key Trustee Server installation requires the default umask of 0022.

Network Requirements

For new Key Trustee Server installations (5.4.0 and higher) and migrated upgrades (see Migrate Apache Web Server to CherryPy for more information), Key Trustee Server requires the following TCP ports to be opened for inbound traffic:

• 11371

  Clients connect to this port over HTTPS.

• 11381 (PostgreSQL)

  The passive Key Trustee Server connects to this port for database replication.

For upgrades that are not migrated to the CherryPy web server, the pre-upgrade port settings are preserved:

• 80

  Clients connect to this port over HTTP to obtain the Key Trustee Server public key.

• 443 (HTTPS)

  Clients connect to this port over HTTPS.

• 5432 (PostgreSQL)

  The passive Key Trustee Server connects to this port for database replication.

TLS Certificate Requirements

To ensure secure network traffic, Cloudera recommends obtaining Transport Layer Security (TLS) certificates specific to the hostname of your Key Trustee Server. To obtain the certificate, generate a Certificate Signing Request (CSR) for the fully qualified domain name (FQDN) of the Key Trustee Server host. The CSR must be signed by a trusted Certificate Authority (CA). After the certificate has been verified and signed by the CA, the Key Trustee Server TLS configuration requires:

• The CA-signed certificate
• The private key used to generate the original CSR
• The intermediate certificate/chain file (provided by the CA)

Cloudera recommends not using self-signed certificates. If you use self-signed certificates, you must use the --skip-ssl-check parameter when registering Navigator Encrypt with the Key Trustee Server. This skips TLS hostname validation, which safeguards against certain network-level attacks. For more information regarding insecure mode, see Registration Options.

What's New in Cloudera Navigator Key Trustee Server 5.10.0

• Key Trustee Server supports RHEL 7.3.
• Key Trustee Server supports OEL 6.8, 7.2, and 7.3.
• Key Trustee Server supports modifying the supported ciphers and protocols for TLS.