Release Notes

Product Description

CipherTrust Manager is the center of the CipherTrust Data Security Platform. It serves as the central point for managing configuration, policy and key material for data discovery, encryption, on-premise and cloud based use cases. It is the successor to both the Thales eSecurity (formerly Vormetric) DSM and the Gemalto (formerly SafeNet) KeySecure platforms.

Product Abbreviations

Release Description

This release is available on the Customer Support Portal in the following formats:

• An upgrade file for physical k570, k470 and k160 CipherTrust Manager devices, and existing k170v Virtual CipherTrust Manager instances.

• An OVA image file for deploying a new Virtual CipherTrust Manager on VMWare vSphere or Nutanix AHV.

• A VHDX image file for deploying a new Virtual CipherTrust Manager on Microsoft Hyper-V.

• A QCOW2 image file for deploying a new Virtual CipherTrust Manager on OpenStack or RedHat OpenShift.

In addition, 2.21.0 Virtual CipherTrust Manager will be available on the following public clouds, as the Community Edition:

• Amazon Web Services: SafeNet Cloud Provisioning System

• Google Cloud

  Note

  As 2.21.0 is not the default version, you must use the gcloud CLI to retrieve it.

• Microsoft Azure: Available as a BYOL image in the Microsoft Azure Marketplace

• Oracle Cloud

• IBM Cloud

  • An OVA image file for deploying a new Virtual CipherTrust Manager on IBM Cloud VMWare.

  • A QCOW2 image file for deploying a new Virtual CipherTrust Manager IBM Cloud Virtual Private Cloud Gen2.

2.21.0 contains a number of new features and enhancements. Refer to Release 2.21.0 for details. For the list of known issues, refer to Known Issues.

Features and Enhancements

Release 2.21

Platform

• Enhancements to Open ID Connect (OIDC) authentication for CipherTrust Manager users.

  • CipherTrust Manager now attempts to fetch group claims from the UserInfo endpoint during OIDC authentication, when the OIDC connection is configured for authorization code flow, and no group membership information is in the ID token.

  • Added the ability to specify a scope value when creating an OIDC connection.

• Introduced logging of REST crypto operations in audit records over REST API using the ENABLE_REST_CRYPTO_RECORDS system property.

• Introduced a system property UI_IDLE_SESSION_TIMEOUT to configure the session timeout for the UI when it is idle.

• Support for Certificate Revocation List (CRL) verification of Syslog, Loki, and Elasticsearch server certificates has been added to log forwarders.

• Added following new regions to AWS Connection Manager:

  • ap-southeast-5

  • ap-southeast-7

  • ca-west-1

  • il-central-1

  • mx-central-1

• Introduced PASSWORD_HASH_ITERATIONS system property to define how many times a hashing algorithm is applied repeatedly to a password. The default value is 10000 and the permissible values are 10000 and 5000.

• Support for post quantum cryptography curves along with traditional curves using Key Exchange algorithms (KEX) for SSH interface. This feature is in tech preview.

• Support for post quantum cryptography curves along with traditional curves via configurable TLS groups on Web interface on UI. This feature is in tech preview.

• k160 physical appliance: Zeroization Buttons have been enhanced to not only clear any attached token HSM of all objects and perform a system reset, but also clear the SSH key and ksadmin password, remove log files (CM, akeyless, upgrades); remove backups and backup keys; clear custom networking configuration; and power off the device.

CCKM

• Tech Preview: PQC-enabled TLS channel with quantum-safe ciphers (ML-KEM) between CCKM and Google Chrome.

• AWS:

  • GUI: Added new regions for AWS resources.

  • Added support for on-demand rotation of imported/BYOK cryptographic key material without changing the AWS key identifier (key ARN).

  • Added support for on-demand rotation of AWS native keys.

    Note

    With support for on-demand rotation of both native and imported BYOK keys, the refresh operation now takes longer than in previous releases. This is because detailed rotation information must be synchronized from AWS KMS to CCKM.

• Azure:

  • API: Enabled uploading of wrapped CipherTrust Manager keys (local and external) to Azure Premium and Managed HSM vaults.

• Google Workspace CSE:

  • Added support for the Beta release of Google's end-to-end encrypted email and will extend the support to the GA version upon its availability.

  • API: Added capability for the Privileged Wrapped API to enable encrypted bulk import.

CTE Suite

Information in this section applies to all types of CTE Agents unless stated specifically.

• The enhanced CTE client management UI is now Generally Available (GA). This feature, previously in Tech Preview, provides a uniform display for client details across the CipherTrust Manager platform and reorganizes parameter modification controls for improved clarity.

CTE

• Addressed issues with missing key SALT during CipherTrust Manager upgrades by improving the handling of "Unique to Client" keys.

• Added support to display the release timestamp of the compatibility matrix after it is uploaded.

• Added the GuardPoint icon to already active GuardPoints when creating GuardPoints for clients and client groups.

• Included client group names in client reports.

• Added support for enabling or disabling multiple GuardPoints on clients.

• Added support for subdomains to inherit the compatibility matrix if they don’t have one.

CTE UserSpace

Notes on CTE UserSpace

CTE UserSpace is a kernel-independent file encryption product. The resources of CTE UserSpace clients running 10.0 and higher Agent versions are managed by the Transparent Encryption application on the CipherTrust Manager. These clients can't be managed by the ProtectFile & Transparent Encryption UserSpace application.

This release does not support the following features:

• Kernel Compatibility Matrix

• Agent and System locks

• CBC and XTS keys

• COS, IDT, and LDT policies and GuardPoints

DDC

• Added support for processing and reporting for partially completed scans, allowing users to receive results even when some sub-scans fail. The system will skip failed sub-scans, continue processing successful ones.

• Extended support for upgraded DDC Agents. Refer to DDC Agents for details.

• Added the following new infotypes.

  • Blood Type - It helps organizations, that deal with personal medical data, to detect the eight main blood types, and remediate these vulnerabilities within their organization's digital systems.

  • Turkish Tax Identification Number - It can detect 10-digit Turkish Tax Identification Number (TIN).

• Enhanced the following information types.

  • Turkish Identification Number can now detect TIN that begin with '8'.

  • Australian Driver License Number has now support for selecting robust or relaxed search to apply either a strict or lenient search to scans.

  • Australian Healthcare Identifier has improved scan time when detecting unsecured healthcare identifier data.

  • Australian Individual Healthcare Identifier has improved scan time when detecting unsecured healthcare identifier data.

  • Belgian National Number can now detect national numbers with mixed separators, specifically a combination of period and dash symbols.

• Distributed scans can now be performed in Salesforce targets.

• Updated TLS protocol and SSH protocol libraries, compression and image processing libraries, regular expressions library, and other third-party library upgrades for increased application security.

• Updated data compression and image processing libraries for increased application security.

• End of support: The following platform/features are scheduled to reach end of support in an upcoming release.

  • Email targets - Exchange Domain

    • Exchange Server 2013

  • Server targets - SharePoint Server

    • SharePoint Server 2013

  • Hadoop clusters

    • Apache Hadoop 2.8.0 and older

  • Database targets

    • MySQL 5.7 and older

    • Oracle 18c and older

• Troubleshooting logs are now available during all stages of scan.

Application Data Protection

• GUI Enhancement: Redesigned the protection policy wizard to improve user experience and navigation.

• BDT: Introduced the ability to delete jobs in initiating, completed, or stopped states.

• BDT: Implemented support for a dynamic progress bar on the job status page, providing real-time updates for ongoing jobs along with an option to stop a running job.

CipherTrust Secrets Management (CSM)

This release does not include any features or enhancements for CSM.

Resolved Issues

System Upgrade Supported Releases

System upgrades on a single unclustered device have been tested from releases 2.18.0, 2.19.0, and 2.20.0.

Refer to the System Upgrade page for instructions to perform an upgrade or downgrade.

The cluster upgrade section provides instructions to perform an upgrade on a cluster of devices. Supported upgrade paths depend on the method used to upgrade the cluster.

• Cluster remove/rebuild is supported from 2.18.0, 2.19.0, and 2.20.0.

• In-place cluster upgrade is performed from one minor version at a time, so there is no limit on starting version.

Restoring a backup from release 2.18.x or later is supported; however, restoring a newer backup to an older version is never supported.

An unclustered CipherTrust Manager can be downgraded to the previous minor version. For release-specific upgrade/downgrade information, refer to the release notes for your release.

Advisory Notes

This section highlights important issues you should be aware of before deploying the CipherTrust Manager. There is also a full list of known issues associated with the release.

Add All AWS CloudHSMs in AWS Cluster for High Availability of Root of Trust

If you plan to have more than one AWS CloudHSM in an AWS Cluster, you must manually add each additional to CipherTrust Manager as soon as possible.

Otherwise, if none of the configured CloudHSMs is available on root-of-trust service restart, CipherTrust Manager does not recognize the additional, unconfigured CloudHSMs. The CipherTrust Manager application is not accessible with no root of trust available. Contact customer support to recover from this state.

Transparent Encryption UserSpace and ProtectFile

• The ProtectFile & Transparent Encryption UserSpace tile will not be available in the future versions of CipherTrust Manager.

  Note

  In the upcoming releases, support for ProtectFile and the legacy Userspace client (version 9.0.0 and earlier) will be discontinued. All the corresponding endpoints and services will be removed from the both GUI and API Playground.

  After upgrading to the upper versions of CipherTrust Manager, existing ProtectFile clients will no longer function. To continue using ProtectFile, it is advised to use lower versions of CipherTrust Manager. However, Thales will not offer any client or CipherTrust Manager side support for ProtectFile.

Platform

Policies

Policies created to manage authentication based on the Client IP parameter don't apply to the requests coming to the NAE and KMIP interfaces with "anonymous login" mode enabled. For details, refer to Client IP.

Recommendation for NAE KeyQueryRequest

If a domain has more than 1000 cryptographic objects (keys and opaque objects), to fetch keys, it is recommended to use KeyNamesRequest instead of KeyQueryRequest. The response time of KeyQueryRequest is proportional to the number of keys on the CipherTrust Manager, therefore, it may lead to a timeout exception on the client side.

Log Forwarders

The log forwarders are not configured to use the system's proxy configuration. If proxy is configured, the log forwarders bypass the proxy servers.

Backup and Restore

The backup and restore of users and groups in a domain only works among the domains of different CipherTrust Managers. This feature does not support backup and restore among different domains of the same CipherTrust Manager.

Client Renewal

During client renewal, if another client (which has Auth mode set to DN) already exists in the system with a matching subject DN, the client renewal may fail. This applies to external or local CA clients. For external CA certificates, delete the client to be renewed and register a new client with a new certificate and different subject DN.
However, for local CAs, it is not required to delete the client to be renewed, rather set the do_not_modify_subject_dn field to false. Refer to Renew Local CA Client Certificates for details.

Downgrade not Supported on this Release for Most Models

The downgrade operation from 2.20 to 2.19 is not supported for any model. You can downgrade a k160 physical appliance to 2.15.0 or 2.16.x. Attempting to downgrade 2.20 will fail on k570 and k470 physical appliance, and k170v and k470v virtual appliances.

The following alternatives are available:

• For physical appliances, factory reset the appliance using the kscfg system factory-reset command, which resets the appliance to the software version applied at the factory. Then upgrade to the desired version following supported upgrade paths, and restore a backup.

  Note

  This is not supported on k160 models.

• For virtual appliances, deploy a new virtual appliance, and then restore a backup.

LDAP Connections

Added a validation in the GET /v1/usermgmt/connections/{id}/users/ API to prevent it from working on LDAP Connections. It is documented in the API Playground that this API supports zone connections only. To get all the local users and the already authenticated LDAP users of all the configured LDAP connections, the GET /v1/usermgmt/users API can be used.

Update Alarms for Secure Copy Protocols (SCP/SFTP)

Customers need to modify the existing alarm if configured with the message SCP Backup. They must update the message from SCP Backup to Secure Copy Backup in the alarm.

Increased Disk Space and Cluster Node Downtime Required for Upgrade from CipherTrust Manager 2.13.x or lower

Due to major internal database upgrades in 2.14.x and 2.16.x, CipherTrust Manager upgrade requires more free disk space and cluster node downtime when upgrading from CipherTrust Manager 2.13.x or below. You cannot directly upgrade from 2.13.x to 2.21.x, so these effects apply when you first upgrade from 2.13.x to an intermediate minor version, 2.14.x, 2.15.x, or 2.16.x.

• You require 35 GB of free disk space to exercise the upgrade.

• In-place online cluster upgrade requires additional downtime for cluster nodes. An individual cluster node might be unavailable for 10 minutes or more.

• During upgrade, the message NOTICE: skipped replication for captured CCL command "LOCK TABLE in replication sets (kylo) is displayed multiple times. This is an expected part of backend database configuration and does not indicate a problem.

Required System Volume Disk Size for Virtual CipherTrust Manager

If you have deployed at a Virtual CipherTrust Manager with the previous evaluation disk size of 50 GB, you need to increase the system volume disk space to exercise the upgrade. We recommend at minimum 300 GB.

Recommendation for Secure Initialization Vector in DESede CBC, AES CBC, and AES GCM Encryption Requests

When generating a new AES or DESede key CipherTrust Manager currently generates and stores a Default IV associated with the new key. This is mainly used to support specific legacy integrations and applications.

We strongly recommend future crypto applications use a secure, unique initialization vector (IV) for each AES CBC, AES GCM, and DESede CBC encryption request, rather than relying on a default IV provided by CipherTrust Manager for the security of your data. For example, unpredictable, unique IVs for AES CBC requests protect against oracle attack techniques such as ROBOT, DROWN, POODLE, and BEAST.

We recommend to use CipherTrust Manager's random number generation to produce secure IVs, or you can provide your own IV with each AES CBC, AES GCM or DESede CBC encryption request following the security guidelines for constructing secure IVs in NIST SP800-38A and NIST SP800-38D.

In the KMIP interface, always set the RandomIV object in the Cryptographic Parameters attribute to true or provide your own secure IV in the Request Payload as an IV/Counter/Nonce object.

In the REST and NAE interfaces, use CipherTrust Manager's random number generation to produce secure IVs for cryptographic requests, or provide your own secure IV.

Some Key States Change After Upgrade

After upgrade from 2.4.x some key states are remapped as a result of harmonizing NAE-only key states. In most cases, the allowed operations for a key remain the same before and after upgrade, so key usage is not disrupted.

As you cannot upgrade directly from 2.4.x to 2.20.x, these changes take effect when you first upgrade from 2.4.x to an intermediate minor version, 2.5.x, 2.6.x, or 2.7.x.

• When a key has an NAE state of Retired and the deactivation date is set in the future, the key is set to Deactivated immediately upon upgrade. No cryptographic operations are allowed.

• When a key has an NAE state of Restricted and Protect Stop Date is set in future, the key is set to Active and the Protect Stop Date is set to the current time. Decryption, signature verification, unwrapping, and MAC verification are allowed.

• When a key has an NAE state of Active and Activation Date is not set, the activation date is set to the current time. All cryptographic operations are allowed.

• When a key has an NAE state of Active and Activation Date is set in the future, the key is set to a Pre-Active state and the Activation Date is retained. No cryptographic operations are allowed until the Activation Date is reached.

• When a key has a state of Deactivated before upgrade, its state will be unchanged after upgrade. However, the allowed operations for the Deactivated state change for 2.5. The key loses its ability to decrypt, verify signatures, unwrap, and verify MACs. You can re-activate the key after upgrade and set the ProtectStop date to restore those operations.

Protect the ksadmin Private SSH Key

The private SSH key for the ksadmin account is critical to system security and must be carefully protected. Failure to do so could allow an attacker to compromise the system.

TLS/SSL Must be Enabled in a Production System

As it may be useful for troubleshooting, it is possible to disable TLS/SSL for the NAE interface. This will lead to an insecure system. Therefore, TLS/SSL should always be enabled for a production system.

DDC

Clusters

• Only one CipherTrust Manager node in the cluster can have DDC activated. To access DDC, create a new DNS entry to point to the active CipherTrust Manager node.

• DDC functionality cannot be accessed through the CipherTrust Manager FQDN. DDC requests sent to an inactive CipherTrust Manager node fail (and return the impression that DDC fails randomly).

Licensing

Overlapping licenses are not supported (except for the trial license).

EOS for Legacy Reports

The support for Legacy Reports has been dropped in DDC 2.11.

EOS for KCT Datastore

End of Support for KCT Datastore Format in DDC 2.11.

Upcoming End of Support for Platforms and Features

• Linux 2.4 Node Agents

• Email Targets - Microsoft Exchange (EWS)

• Microsoft 365 - Exchange Online (EWS)

• Web Browser - Internet Explorer

Compatibility

This section documents known compatibility topics to be considered before deploying the CipherTrust Manager.

TLS Compatibility

This table identifies the supported TLS versions for each of the CipherTrust Manager interfaces. The default minimum value reflects the default minimum_tls_version setting. This setting controls the lowest acceptable TLS version allowed for connections to the interface.

By default, CipherTrust Manager accepts the following ciphersuites for TLS 1.2+ connections:

• TLS_AES_256_GCM_SHA384 (TLSv1.3)

• TLS_CHACHA20_POLY1305_SHA256 (TLSv1.3)

• TLS_AES_128_GCM_SHA256 (TLSv1.3)

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

TLS Deprecation Notices

• Use of TLS 1.0 and 1.1 protocols is deprecated. This support will be discontinued in a future release. Upgrade all applications connecting to CipherTrust Manager interfaces to TLS 1.2 or higher as soon as feasible.

• Use of the following CBC-based ciphersuites is deprecated, and support will be discontinued in a future release:

  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA

  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

  • TLS_RSA_WITH_AES_256_CBC_SHA

  • TLS_RSA_WITH_AES_128_CBC_SHA

Client Platforms

The following client Platforms are supported by the CipherTrust Manager.

CipherTrust Application Data Protection

• CADP for .NET Core: minimum version 8.11.0

• CADP for C: minimum version 8.14.0

• CADP for Java: minimum version 8.13.0

CipherTrust Application Key Management

• CAKM for Oracle TDE: minimum version 8.10.0

• CAKM for Microsoft SQL Server EKM: minimum version 8.5.0

CipherTrust Cloud Key Manager

Minimum version 1.6.3.20532

CipherTrust Database Protection

• CDP for Oracle: minimum version 8.12.0

• CDP for MSSQL: minimum version 8.12.0

• CDP for DB2: minimum version 8.12.0

• CDP pdbctl: minimum version 1.5.1

• CipherTrust Teradata Protection: minimum version 6.4.0.12

• Transformation Utility: minimum version 8.4.3

CipherTrust Transparent Encryption

Minimum version 7.0.0

CipherTrust Transparent Encryption UserSpace

Minimum version 10.2.0.83

CipherTrust Transparent Encryption for Kubernetes

Minimum version 1.0.0

CipherTrust Vaulted Tokenization

Minimum version 8.7.1

CipherTrust Batch Data Transformation

Minimum version 2.2.0.2816

CipherTrust Vaultless Tokenization

Minimum version 2.5.2.19

ProtectFile

Minimum version:

• ProtectFile Windows 8.12.3

• ProtectFile Linux 8.12.3, 8.12.4p02 (for migration to CTE)

The latest three GA versions of ProtectFile are tested with CipherTrust Manager. Older versions are expected to work, but they are not tested explicitly.

Data Discovery and Classification Agents

Linux minimum kernel version is 2.6.

There are no changes in Agent requirements if you are upgrading from CM 2.4 to 2.5.1. If you are upgrading from a version older than 2.4 please refer to Upgrading Agents.

TDP Version Compatibility

Data Discovery and Classification requires TDP 3.1.5.1 or newer.

• If you have an existing TDP 3.1.5 cluster, you should apply the patch 3.1.5.1.

  Following the TDP upgrade users are required to Configure TDP service HDFS again and also Configure TDP service Livy.

Known Issues

This section lists the issues known to exist in the product at the time of release.

CipherTrust Manager

Application Data Protection

CipherTrust Application Data Protection (CADP for C)

CipherTrust Cloud Key Manager

CipherTrust Database Protection

CipherTrust Data Discovery and Classification

CipherTrust Secrets Management

CipherTrust Transparent Encryption

Batch Data Transformation (BDT)

ProtectApp

ProtectFile