Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Release Notes

search

Please Note:

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

NameAbbreviation
CipherTrust Batch Data TransformationBDT
CipherTrust ManagerCM
CipherTrust Application Data ProtectionCADP
CipherTrust Application Key ManagementCAKM
CipherTrust Cloud Key ManagerCCKM
CipherTrust Data Protection GatewayDPG
CipherTrust RESTful Data ProtectionCRDP
CipherTrust Database Protection (formerly known as ProtectDB)CDP
CipherTrust Live Data TransformationLDT
CipherTrust Transparent EncryptionCTE
CipherTrust Transparent Encryption for KubernetesCTE-K8s
CipherTrust Transparent Encryption for RansomwareRWP
CipherTrust Transparent Encryption UserSpace (formerly known as ProtectFile FUSE)CTE UserSpace
CipherTrust Intelligent ProtectionCIP
CipherTrust Data Discovery and ClassificationDDC
CipherTrust Vaulted TokenizationCT-V
CipherTrust Vaultless TokenizationCT-VL
Data Protection on DemandDPoD
CipherTrust Secrets ManagementCSM

Release Description

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

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

    Note

    This release is not supported on Thales TCT k160 devices.

  • 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.

In addition, 2.17.x 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.17.x 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.17.x contains a number of new features and enhancements. Refer to Release 2.17.0 for details. For the list of known issues, refer to Known Issues.

Features and Enhancements

Release 2.17.0

Platform

  • UI enhancement: Added a count display on the alarms menu to indicate the number of active alarms.

  • Introduced Service Name and Record Type Id fields in loki audit records. These fields are displayed as columns on the UI. The existing "Service" column will be hidden from the UI. To add alarm configuration using a record from UI, instead of the service field, the newly added Service Name field will be used.

  • Added ability to create keys using templates on the CipherTrust Manager.

  • Added support for the <Algorithm> tag in KeyNamesRequest to filter keys based on their algorithms using NAE XML.

  • Included Subject Key Identifier in the issued certificate from the local CA.

  • Modified owner of a key in a domain over NAE-XML using KeyGenRequest, KeyModifyRequest and SecretModifyRequest.

  • Support to migrate the keys from DSM to CipherTrust Manager with KMIP 2.0 attributes added in the KMIP Migration Utility (MIG).

  • Support added to download reports for Cluster, Domains, License Usage, Clients, CAs and Certs, and Interfaces.

  • Introduced a dedicated prefix, dke. for hostname which will allow the CCKM DKE TLS connection to work.

  • Internal Luna HSM clients updated to keep up to date with latest security patches, bug fixes, and performance improvements, and to expand compatibility to the FIPS 140-3 Level 3 certified Luna HSM firmware 7.8.4. Connections to all Luna HSMs use Luna HSM Client 10.7. The following integrations are supported with Luna HSM firmware 7.8.4:

    • Luna Network HSM as a root of trust

    • Luna Network HSM for HSM-anchored domain

    • Luna Network HSM as a key source for CCKM

    • The embedded PCI HSM on k570 appliances as a root of trust

    Warning

    CipherTrust Manager versions below 2.17.x are incompatible with Luna HSM 7.8.4 firmware, so if you have integrated with this firmware, downgrading CipherTrust Manager would remove access to those integrations.

  • Added support for nShield Connect HSM firmware 13.4.5 for root of trust HSM.

  • Added auto-renewal behavior for the internal cluster certificate. Also added a Cluster Certificate Renewal Threshold system property to control when the certificate auto-renews.

  • Added more UI options to browse for LDAP groupmaps.

  • Added caching behavior in the UI for Loki Audit Records queries. If a user configures a query on the Loki Audit Records page, navigates away, and then navigates back, the query is still applied to the displayed records. The query remains applied for the duration of the UI session.

Limitations

  • 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.

  • 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.

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

  • 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.

  • 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.

CCKM

  • Double Key Encryption (DKE): Released support for DKE for Microsoft 365 for general availability.

  • AWS:

    • GUI: Added support for life cycle management of asymmetric AWS native keys and BYOK from local CipherTrust Manager. CipherTrust Manager as a local key source supports AES (SYMMETRIC_DEFAULT), RSA, EC, and HMAC keys.

    • API: Added capability to disable encrypt permission on rotated keys in all accounts, including the external accounts the keys are shared with.

  • Azure:

    • GUI: Added support for bulk deletion of Azure key backups.

    • API: Added capability to configure schedules to back up all the keys within a vault at specific interval.

    • API: Added capability to restore available Azure keys to a different key vault.

    • GUI: Enhanced the GUI to include status information of Azure versioned keys.

    • Added a new report that lists Azure subscriptions and key vaults discovered and added to CCKM.

  • GCP: Added capability to reimport destroyed BYOK versions using the API.

  • Licensing: Added capability to consume/free licenses using the GUI. Now, you can use the GUI to generate a report that lists the CCKM licenses consumed per domain.

CTE Suite

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

  • Added quorum support for change of client and client group passwords. Refer to Quorum Control for details.
CTE

  • Added support for Designated Primary Set (DPS) for LDT NAS. A DPS can be used to create a group of clients from which you can select a primary client to perform key rotation and versioning. The feature will be available from CTE Agent 7.7.0. Refer to Managing Designated Primary Set for details.

  • Policy Key version is now updated automatically when a key rule operation is performed. The Agent is also updated with the policy key version updates.

  • Added capability to send the Exclusion Rule flag to the Agent for a resource set so the Agent can make an informed decision to not transform the files explicitly marked to be ignored.

Note

CTE resources of Container policies on the DSM cannot be migrated to the CipherTrust Manager using the backup/restore method. The Container policies are supported only on the DSM.

CTE for Kubernetes (CTE K8s)

  • Added capability to fetch latest capabilities from all the active CTE K8s clients present in the current CipherTrust Manager domain without requiring the Agent restart. Refer to Collecting Kubernetes Agent Information for details.

  • Added capability to delete expunged CTE K8s clients manually.

Ransomware Protection

  • Added capability to the CTE for Linux Agent for detection of Ransomware and protection of sensitive data from Ransomware. CTE Agents can monitor the GuardPoints, analyze the data, and look for processes that might perform suspicious activities on the sensitive data. The feature will be available from CTE Agent 7.7.0. Refer to Ransomware Protection for details.

  • Added capability to specify directories to be exempted from RWP monitoring. This support will be available from CTE Agent 7.7.0 (CTE for Linux) and 7.6.0 (CTE for Windows). Refer to RWP Exempted Resource under Creating Process Sets for details.

CTE UserSpace
  • Added support for Multifactor Authentication (MFA) to the MFA-capable clients. In MFA, access to the requested data is granted only after the requester satisfies two or more authentication criteria. Refer to Multifactor Authentication for details. This support will be available from CTE UserSpace 10.3 onward.

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

Note

To manage the clients running the previous versions of the CTE UserSpace Agent, use the ProtectFile & Transparent Encryption UserSpace application only. Alternatively, upgrade those clients to CTE UserSpace 10.0 or a higher version.

DDC

  • Technical preview: Introduced cloud-based Thales Data Platform as a Service (TDPaaS) platform for storing scan and report data over cloud.

  • Added capability to automate disk cleanup activities and display alert banners on excessive disk consumption. See Resolving High Disk Usage Issues for details.

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

  • Added support for Singaporean Bank Account Number and Singaporean Driver License Number infotypes. Refer to Appendix for details.

  • Enhanced Australian Passport Number and United States Driver License Number infotypes.

    • Australian Passport Number data type can now detect the latest R Series passports, aligning with Australia's most recent passport standards and regulations.

    • United States Driver License Number data type now supports Minnesota's driver's license numbers in the dash separator format.

  • Improved memory consumption usage of master server when scanning and performing remediation actions.

  • Deprecated Microsoft Windows 8/8.1 32-bit.

  • Deprecated voice scan under tunable scan. Refer to Advanced Configuration.

Note

DDC 2.17 is not backward compatible, rolling back to previous version is not supported.

CipherTrust Intelligent Protection

Note

Support for CipherTrust Intelligent Protection (CIP) will be deprecated starting from CipherTrust Manager 2.18.0.

CipherTrust Secrets Management (CSM)

  • Support for custom web-rotated secrets for Luna HSM SSH and partition passwords.

  • Support for in-place upgrade of Akeyless gateway on the CipherTrust Manager using a supported versions file.

  • Support added to enable/disable CSM service on the CipherTrust Manager.

  • Created CSM Admins group with permissions to perform the CSM operations.

Resolved Issues

The following table lists the issues resolved in 2.17.0.

IssueSynopsis
KY-88830After disabling two nested GuardPoints applied to a Windows client through a Client Group, you can't enable both GuardPoints. Only one of the GuardPoints can be enabled, the other remains disabled.
KY-88182CCKM Migration: When multiple Salesforce organizations in CCKM Appliance have keys with the same name, all the keys with the same name can't be migrated to CipherTrust Manager.
KY-76609The custom policy statement doesn't update when rotating an AWS key on which the encrypt permissions are disabled (the "Disable Encrypt Permissions on Current Key" check box is selected).
Resolution: Added capability to disable encrypt permission on rotated keys in all accounts, including the external accounts the keys are shared with.
KY-73919Synchronize Salesforce certificate operations don't display error messages in audit logs.
KY-78290Creating/updating user with user_metadata doesn't work correctly on CLI.
KY-73223The error "Agent Info is currently not available" is displayed in client records on the CipherTrust Manager.
KY-86273CM: Cluster report doesn't work.
KY-86632Azure GUI: When adding a new Azure key, the Vault drop-down doesn't display all available vaults.
KY-86259CSM UI: When creating a customer fragment, pressing the "Enter" key after entering a name in the Customer Fragment Name field returns the "405 Not Allowed" error.
KY-85906Backup Admins and Domain Backup Admins are not able to schedule backups through the web console UI.
KY-84440AWS GUI: Alias specified when linking an unlinked AWS HYOK key is not attached to the key.
KY-84081License count doesn't increase for KMIP auto-registered clients. However, the the clients are registered successfully.
KY-83780GCP: After running an add KMS container schedule on CipherTrust Manager 2.14, if you upgrade CipherTrust Manager to 2.16, attempts to download the add KMS container schedule details report returns the "Wrong format of data to convert to CSV" error. The tables on the details page show no records.
KY-72796The CipherTrust Manager constantly communicates with multiple IPs of the Akeyless SAAS server (for example, "52.223.11.194", "35.71.185.167", "35.192.171.171") over port 9443, which leads to a lot of irrelevant log entries.
KY-87057• If you update the Akeyless config or modify the Akeyless connection from the connection manager and immediately sign up, the signup operation may fail to update the Akeyless config with the autogenerated credential.
• If you update the Akeyless config and immediately update the Akeyless connection configured for the Akeyless gateway, the Akeyless config might fail to synchronize.
KY-78303If you configure OIDC authentication for CipherTrust Manager users with an identity provider with a short id_token lifetime, CipherTrust Manager users are logged out of their sessions frequently, every time the id_token expires. The error message "Wrong username or password" is displayed.
KY-78214OIDC & SAML Auth login to Akeyless gateway doesn't work with CipherTrust Manager.
KY-82970After migrating from a CCKM Appliance to CCKM Embedded, searching for a migrated key, which had no backup before migration, returns the "Resource not found" error message on restore.
KY-82266CDP: A non-admin user of the ProtectDB Users group can't migrate tables on the CipherTrust Manager.
KY-81514CCKM SFDC: Refresh operations on CCKM don't remove certificates that are deleted from the SFDC console.
KY-79307When customer fragments are created/deleted in large number or in bulk, it takes too long for secret-manager service to restart and load the Akeyless gateway and console pages.
KY-79220AWS HYOK: When creating a new AWS HYOK key, a key rotation schedule can't be assigned to the key.
KY-78298CCKM SAP GUI: The Algorithm filter on the SAP Keys page doesn't show the RSA 8192 algorithm.
KY-77916AWS GUI: The Accounts column filter on the AWS Keys page returns no results when the table is reset.
KY-77452Salesforce sandbox test connection fails when using domain_name field.
KY-76147If you initiate an upgrade, and restart the CipherTrust Manager before being prompted, CipherTrust Manager services sometimes fail to restart.
KY-64751CSM: If you launch the Akeyless console from the Secrets Management tile, and the CipherTrust Manager session expires or is manually logged out, the Akeyless console session logs out as well.
KY-53100Acknowledging/clearing alarms changes alarm's source and source_id to the cluster member node which updated the alarm.
KY-52664NAE: When sending data in bulk requests, encryption fails intermittently.
KY-42593, KY-42491Launching a second scan with any Data Stores in common with a running scan may restart the first scan progress on the shared Data Store, or even fail it if the first scan is manually paused.

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.

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

Due to a major internal database upgrade in 2.14.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.17.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 100 GB.

NextGen KeySecure and ProtectFile End-of-Support

NextGen KeySecure firmware and the ProtectFile connector reached End of Support in December 2023.

In most cases, you can upgrade from NextGen KeySecure to CipherTrust Manager directly. If you are running the legacy k450 or k460 hardware model, you must migrate data to the k470 or k570 model.

We strongly recommend migrating ProtectFile to CTE or CTE Userspace.

Quorum

Do not enable quorum on the ManagePolicyAttachment and DeletePolicy operations until all the CipherTrust Manager nodes in a cluster are upgraded to 2.10 or a higher version.

SMB Connection

The Host and Port fields must be specified together, or do not specify any of them. If Host and Portare not specified while creating an SMB connection, these fields cannot be added later.

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.

Caution

The IV value used for an encryption request is needed to decrypt the data later.

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.17.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.

System Upgrade and Downgrade Supported Releases

System upgrades on a single unclustered device have been tested from the latest patches of 2.14.x, 2.15.x, and 2.16.x.

Note

Upgrades from other versions have not been tested and may not work correctly.

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.

Warning

As we cannot guarantee stability, we strongly recommend using downgraded systems for test environments only. Do not use a downgraded CipherTrust Manager in a production environment. As well, CipherTrust Manager versions below 2.17.x are incompatible with Luna HSM 7.8.4 firmware, so if you have integrated with this firmware, downgrading CipherTrust Manager would remove access to those integrations. The integrations could include Luna Network HSM as a root of trust, Luna Network HSM for HSM-anchored domain, Luna Network HSM as a key source for the CipherTrust Cloud Key Management (CCKM) product, and the embedded PCI HSM on k570 appliances as a root of trust.

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 the latest patch releases of 2.14.x, 2.15.x, or 2.16.x

  • 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.14.x or later is supported; however, restoring a newer backup to an older version is never supported.

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.

Key Usage Mask Selection

If you want to perform any operation (for example, Wrap/Unwrap) from the NAE/KMIP connector, set the usage mask explicitly for that operation while creating keys through UI.

DDC

Upgrading DDC

After you upgrade to version 2.11 you will not be able to downgrade it to any of the previous versions.

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.

InterfaceMinimum TLS versionMaximum TLS versionDefault Minimum TLS version
Web UITLS 1.2TLS 1.3TLS 1.2
NAETLS 1.0TLS 1.3TLS 1.2
KMIPTLS 1.0TLS 1.3TLS 1.2

Caution

TLS 1.0 and TLS 1.1 support will be discontinued in a future release.

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.

Caution

Older versions of most client platforms (versions earlier than the minimum versions listed below) may have incompatible TLS clients. We recommend testing older versions of client platforms in a non-production environment to ensure proper functionality.

For the purpose of transitioning from SafeNet KeySecure Classic, you can temporarily connect to CipherTrust Manager with TLS/SSL disabled on the CipherTrust Manager NAE interface; however, this is recommended only in a non-production environment.

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.

Note

ODBC driver for Microsoft SQL: To connect to Microsoft SQL, DDC Agent requires the ODBC drivers to be installed on the host. If DDC cannot find a suitable agent, make sure that these drivers are installed. If necessary, upgrade them to the latest available version. Thus, if your MSSQL Server is configured with TLS 1.2 only, install the ODBC Driver 17 for MSSQL Server.

TDP Version Compatibility

Data Discovery and Classification requires TDP 3.1.5.1 or newer.

Known Issues

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

CipherTrust Manager

ReferenceSynopsis
KY-96139Problem: When CipherTrust Manager is upgraded from v2.12.0 or older, the "unique to client keys" feature doesn't work as expected. The data is being encrypted using a key that is "not" unique to the client where the CipherTrust Transparent Encryption (CTE) agent is installed.
It is recommended to contact Thales Customer Support team to help with addressing the issue for affected deployments.
KY-94139Problem: If you configure an OIDC connection for CipherTrust Manager users, and set up group maps in a child domain, group permissions are not applied when users are logged into the child domain.
KY-93946Problem: If you create an LDAP connection in the CipherTrust Web UI, you cannot create a new group map for a group while logged into a child domain.
Workaround: Use the ksctl groupmaps create CLI command to perform the mapping in a child domain.
KY-89382Problem: CipherTrust Manager 2.15 onward, the logs are not recorded for each key export request operation in the server logs or Loki audit logs if the key export request is made within 24 hours.
KY-92312Problem: If you attempt to configure an HSM root-of-trust on the CipherTrust Web UI, the UI sometimes displays a timeout error, but the HSM configuration succeeds.
Workaround: Wait two minutes and refresh the page to see if the HSM configuration succeeded. If the HSM configuration fails, retry with the ksctl hsm setup --timeout 120 CLI command.
KY-92080Problem: If the client certificate is renewed before its expiration date, on the original expiration date, the client goes into the expired state, however, the communication between the client and the CipherTrust Manager is retained.
This issue doesn't have any impact on the functionality.
KY-91730Problem:If a network interface connection goes down on a node, the cluster status for that node displays as ready on other nodes, even though the node is unreachable.
KY-91035Problem: When you modify the key to add permissions, it wipes the custom attributes of the key.
KY-91454Problem: Before upgrading the CipherTrust Manager, if you change the setting (hide/show) of a column in a table, then after the upgrade, the order of the column is changed and the blank screen error may be displayed.
Workaround: Reset the columns setting, run the update user API, and set "user_metadata": {"persistedData": {}}.
KY-89062Problem If you attempt to create a partial domain-scoped backup in the CipherTrust Web UI, and toggle the number of results for Domain Backup Key in the Backup Properties screen, sometimes available domain backup keys no longer display. This occurs if you have more than ten domain backup keys.
Workaround: Retain ten or fewer domain backup keys.
KY-88925Problem: If you add connections to multiple Luna Network HSM V1 partitions in HA mode in connection manager, CCKM Luna key source and HSM-anchored domains are not usable.
Workaround: Use Luna Network HSM V0 partitions for HA groups formed through the connection manager. Delete existing connections to Luna Network HSM V1 partitions.
KY-89062Problem: UI: Default backup key disappears after changing view per page if the count of available keys is less than 10.
KY-88423Problem: When upgrading older CipherTrust Manager version directly to 2.17, the CSM service may get disabled.
Workaround: Enable CSM after upgrade.
KY-87618Problem: If you download the system license usage or domains report as a PDF, the user ID field is blank.
KY-87505Problem: GUI: Can't navigate to an EKM endpoint by clicking the endpoint link on the details view of the DeleteEKMEndpoint quorum metadata.
KY-87241Problem: When renewing NAE/KMIP clients, details of the new certificate are not updated until the client remains idle for approximately 10 minutes.
For KMIP clients, this issue occurs only in the TLS, verify client cert, user must supply password mode whereas for NAE clients it is observed in all modes.

For NAE clients, you can retrieve the updated certificate details using the /v1/protectapp/clients-get API or through the CM UI under Legacy Clients > Registered Clients section.

For KMIP clients, keep the client idle for at least 10 mins, after renewal.
KY-87152Problem: When a renewed client certificate reaches its expiration, the client remains in an active state but is unable to establish a connection with the expired certificate.
KY-87183Problem: Client renewal fails, if interface mode is changed from TLS, verify client cert, user must supply password to TLS, verify client cert, user name taken from client cert, auth request is optional before certificate renewal.

It is recommended to avoid modifying the interface mode when renewing the client.

Workaround: Restore the interface mode to its previous value and proceed with client renewal, or delete and re-register the client.
KY-83840Problem: The /v1/usermgmt/connections/{id}/users/ API returns all users instead of users associated with the specified connection.
KY-82087Problem: After client renewal, it takes around 10 minutes for the client to switch from expired state to active state. During this time, the client operates normally with the renewed certificate.
KY-87394Problem: In the TLS verify client cert, Allow anonymous logins mode, NAE/KMIP clients remain in the expired state after the client certificate is renewed, but continue to operate normally with the renewed certificate.
KY-84562Problem: Deactivating the CipherTrust Manager Full Trial license does not deactivate individual trial licenses.
Workaround: Reactivate the Full Trial license and re-attempt deactivation.
KY-80554, KY-81695Problem: If a client certificate contains both OCSP and CRL URLs, the certificate revocation check (for NAE and KMIP clients) only considers the OCSP and never falls back to check the CRL even if the OCSP URL is inaccessible.
KY-66351, KY-63083Problem: Clients registered in a deleted domain are not excluded from the License usage.
Workaround:
1. Log on to the root shell.
2. Delete the entries of the clients registered with the deleted domain from the database.
KY-64823, KY-61196Problem: In a CipherTrust Manager cluster, if two nodes are disconnected and you create the same user on both nodes and update them with same DN, on re-connect, duplicate users get created.
Workaround: Duplicate users cannot be authenticated as regular users, therefore, function as redundant users. It is recommended to delete these users to avoid any confusion. However, if you don't delete them, you will be allowed to log in with one user only.
KY-64600Problem: If you create multiple automatic key rotation scheduled jobs, and they are scheduled to run at the same time, a key rotation intermittently fails with the message 'There is an ongoing key rotation job, cannot add another'.
Workaround: Schedule automatic key rotation jobs to run at different times from one another.
KY-64597Problem: Typing a % (percent character) into the embedded API Guide for GET operations leads to inconsistent results, and sometimes crashes the page.
Workaround: As a best practice, avoid naming resources with the % character. If you must retrieve a resource with a % in its name, use the UI or CLI to do so.
KY-64562Problem: Policy attachments can be detached (deleted) from system policies even though those policies are read-only.
Workaround: Restart CipherTrust Manager to populate the deleted system policy attachment.
KY-61892Problem: The NAE and KMIP clients get auto-registered even if the system property, ALLOW_USER_IMPERSONATION_ACROSS_DOMAIN, is disabled and the user impersonated by the client certificate is not created in the root domain and the registration token is generated in the root domain.

However, the client wont be able to communicate using impersonated user for interface mode 'TLS, verify client cert, user name taken from client cert, auth request is optional'.
KY-61722Problem:Deleting a domain that contains an NAE (ProtectApp) client returns status code 500.
KY-61373Problem: The support for ProtectV is removed from the CipherTrust Manager, but the ProtectV license still shows up after the upgrade from version 2.10.0 to 2.12.0.
KY-61054Problem: While migrating from KeySecure Classic to CipherTrust Manager, if the local CA is signed by an external CA, the migration will fail for the local CA even if the external CA is added to the known CA list.
Workaround: If an externally imported CA and its certificates are used on the NAE/KMIP interface of KeySecure Classic, the CA will be migrated as an external CA, but the certificates will not be migrated to the CipherTrust Manager.
Therefore, to use the same certificate for the NAE/KMIP interface on the CipherTrust Manager, select the migrated external CA and upload its certificate manually by editing the NAE interface on the CipherTrust Manager.
Similarly, if a local CA and its certificates are used on the NAE/KMIP interface of KeySecure Classic, use auto-generation or issue a new certificate and upload the certificate to the interface.
KY-56426Problem: Deleted groups still show up in the key details information on the CipherTrust Manager.
KY-56213Problem: If you attempt to create a Luna Network HSM STC partition in connection manager and upload a partition identity file, the upload fails with the error Code 14: NCERRInternalServerError: unexpected error. This is because CipherTrust Manager doesn't recognize the format of the partition identity file downloaded from Luna Network HSM.
Workaround: Use the Linux command base64 -wo on the partition identity file to convert it to base64 format, and then re-attempt the STC partition creation.
KY-55416Problem: Alarms table does not support retention policy. Record based alarms will fill up the table.
Workaround: Contact customer support.
KY-54039, KY-55544Problem: Syslog message redirection from child domains to parent domains stops when 30 or more child domains enable this feature.
KY-53681Problem: You cannot delete the default backup key if it is uploaded from another domain.
Workaround: Contact customer support.
KY-52137Problem: If you rotate the root of trust key for an HSM and then reboot the appliance, services fail to start up and the reboot does not complete. This can happen when the HSM contains two root of trust keys with the same name, and the wrong HSM key is loaded.
Workaround: If you are stuck in services startup, access the HSM with another client, and re-label one of the duplicate keys.
KY-51664Problem: When nShield Connect HSM is configured as root of trust, there are intermittent connectivity issues. The nShield HSM occasionally returns a ServerAccessDenied error, and CipherTrust Manager raises the HSM is offline system alarm.
Workaround: Wait for connectivity issues to resolve after a few automatic reconnection attempts.
KY-51286Problem: In a CipherTrust Manager cluster, when replicating a node, records from one table are not replicated to the tables of the other node due to known constraints with BDR related to foreign keys.
KY-49376Problem: If a CipherTrust Manager is deployed at a version lower than 2.8, a CTE license is installed, and the CipherTrust Manager is upgraded to 2.8 or higher, the displayed CTE license usage count is incorrect.
Workaround: In a domain with pre-existing CTE clients, create or register a new CTE client, and then delete the new client.
KY-49126Problem: After the external CA is uploaded on the CipherTrust Manager, the GN and DC fields are not displayed as part of the record.
KY-48284Problem: Domain backups with local users cannot be restored into another domain in the same cluster.
Workaround: Restore the backup to a CipherTrust Manager in a new cluster, or to a different CipherTrust Manager instance which isn't clustered.
KY-47184Problem: After upgrade, services sometimes fail to restart with an error message starting with Forcing migration for retry.
Workaround: Contact customer support to recover from this state.
KY-39354Problem: Scheduled Partial Domain Backups and Domain Backups fail when there is an SCP connection. The backup file is created on CipherTrust Manager, but it is not forwarded through SCP, and the file is invalid.
Workaround: If scheduled backup through SCP is needed, create a System Backup.
KY-39235Problem: If a user fails to log in to a domain, an audit record is created in the root domain instead of the intended domain.
KY-27450Problem: Local Certificate Authorities (CAs) do not allow commas , in any of the fields.
Workaround: Configure an External CA instead. Use a backslash \ in the Distinguished Name (DN) while creating a user if you are using certificate based login. For example, C=IN,ST=UP,L=Noida,O=Thales\,INC,OU=ENC,CN=test is an accepted value.
All other printable characters are allowed, as per RFC 5280 definition of PrintableString. @ and & are also allowed, beyond the definitions of the RFC.
KY-25152Problem: You cannot pass in a custom SSH key via cloud init on Oracle Cloud instances for initial launch. You also cannot use cloud-init to auto-generate an initial password for the admin user on Oracle Cloud instances.
Workaround: Login to the GUI to enter the SSH public key on initial access. You can also change the password for the admin user on this login.
KY-17338Problem: KMIP: LDAP users cannot be set in the KMIP profile.
Workaround: To use LDAP authentication, use the KMIP auto registration.
KY-11517Problem: ProtectApp Application: The Invalid algorithm string error occurs when signing data with SHA384withRSA/PSSPadding.
KY-7289Problem: When migrating a KMIP application from KeySecure Classic to CipherTrust Manager, for encrypt/decrypt operations, the KMIP server always uses the ECB mode regardless of the provided mode.
Workaround: For migration use cases, if Cryptographic Usage Mask is specified with the CBC mode on KeySecure Classic:
  1. Decrypt the data using KeySecure Classic.
  2. Encrypt the data with keys stored on CipherTrust Manager.
KY-7288Problem: When migrating from KeySecure Classic to CipherTrust Manager, AES-GCM encrypt/decrypt operations, AuthenticatedEncryptionTag is returned appended to CipherText.
Workaround: For migration use cases, when using AES-GCM with KeySecure Classic:
  1. Decrypt the data using KeySecure Classic.
  2. Encrypt the data with keys stored on CipherTrust Manager.
After migration to CipherTrust Manager, the AAD tag is not appended to the data. It is sent as a separate tag.
KY-504Problem: Integration with CloudHSM Cluster: Fail-over is not supported between different ENI IPs within an AWS CloudHSM cluster.
NC-2063Problem: If a user is deleted (or LDAP connection name changes), they fail to display in the keys table.

CipherTrust Application Data Protection (CADP for C)

IssueSynopsis
KY-47385Problem: If you migrate a non-deletable VAE key from Data Security Manager to the CipherTrust Manager, the imported key is shown as "deletable".
Workaround: After migration, edit the key attributes on the CipherTrust Manager to make it non-deletable.

CipherTrust Cloud Key Manager

IssueSynopsis
KY-95730Problem: GCP GUI: The details page of a Google key page shows incorrect Soft Delete Wait Time.
KY-92814Problem: CCKM GUI: After applying a filter to a column, if you navigate away from the screen and return back, the filter may not persist.
Workaround: Apply the filter again.
KY-92752Problem: If the AWS XKS is connected and CCKM is disconnected, you cannot update the External Custom Key Store details of an AWS KMS Account.
Workaround: You can disconnect the AWS Console and CCKM, then update the External Custom Key Store details of an AWS KMS Account.
KY-87019Problem: GWS GUI: When creating a new endpoint, the Identity Provider list displays only 10 identity providers.
Workaround: Use the API to create a new endpoint using the required identity provider.
KY-86980Problem: Salesforce GUI: When adding a new Salesforce key using DSM to configure the source key, the DSM Domain field on the Configure DSM Key screen may not display all the available DSM domains.
Workaround: Use the API to add a new Salesforce key by uploading a DSM key created in a specific DSM domain.
KY-92234Problem: AWS GUI: AWS connection linked with an AWS KMS account can't be changed.
Workaround: Run the patch /v1/cckm/aws/kms/{id} API to change the AWS connection.
KY-91459Problem: CCKM UI: Scheduler can't be linked to AWS HYOK keys.
Workaround: Link the scheduler using the API.
KY-89617Problem: EKM GUI: Clicking the Refresh button on the Cryptospace Endpoints tab displays incorrect number of endpoints.
Workaround: Navigate away from the Cryptospace Enpoints tab and visit it again.
KY-89969Problem: Cloud key management APIs don't work behind a proxy for Google EKM, Google Workspace CSE, Microsoft DKE, OCI HYOK, SAP, DSM, and external CipherTrust Manager.
Workaround: Add the proxy URLs for your cloud to the proxy exception list and allow this URL in the firewall. Refer to URLs to Whitelist for Running CipherTrust Manager Behind Proxy.
KY-89331Problem: AWS: While creating an AWS asymmetric key, the key upload to AWS fails with the error "Failed to create KS RSA key pair."
KY-89277Problem: GCP GUI: After adding a new key version with CipherTrust (Local) as the source, on clicking the source key ID on the Key Versions list page, the "Resource not found" error occurs.
KY-89038Problem: GCP GUI: Only 100 key rings are listed on the Add Key Rings screen even if more than 100 key rings exist.
Workaround: View all the existing key rings using the API.
KY-88498Problem: GUI: The "Expiration Date" check box is disabled for "Luna HSM" and "CipherTrust (External)" key sources while performing manual key rotation.
KY-87229Problem: Luna HSM GUI: When a CCKM User with permissions to view keys tries to refresh all keys of a Luna HSM partition, incorrect error "Unable to start refresh on Luna Partition" is displayed. The error should be "Access forbidden on partitions".
KY-84973Problem: If a user doesn't have the read permission, a "Resource not found" error is continuously displayed for all clouds with Luna HSM as the key source.
KY-72770Problem: OCI: The origin field of asymmetric HSM keys with External BYOK as Origin Type is set inconsistently for initial and subsequent versions. The origin of the initial version is correctly set to EXTERNAL. However, the origin of subsequent versions is incorrectly set to INTERNAL.
This issue is at the Oracle end.
KY-72067Problem: GUI: Salesforce mTLS connection doesn't work when the Salesforce connection to the CipherTrust Manager is configured using the Password authentication.
Workaround: Use the authentication type of Certificate or Client Credential (My Domain) when creating the Salesforce connection to the CipherTrust Manager.
KY-65165Problem: SAP: A delete key job remains in the PENDING state for long time and fails intermittently. This issue is at the SAP end.
KY-56952Problem: GCP GUI: ACLs of Google Projects for cryptospaces and cryptospace endpoints can't be updated with the "CCKM Users" group.
Workaround: Use the API to update the ACLs with the "CCKM Users" group.
KY-42082Problem: SAP Data Custodian: SAP key activity report doesn't show any data. This issue is at the SAP end.
KY-31186Problem: If your proxy server does not support HTTP CONNECT, the CCKM Google cloud connection cannot use the CipherTrust Manager's proxy feature with a certificate.
Workaround: Add an exception (cloudkms.googleapis.com) with no_proxy or use the proxy with username and password, and restart the services.
KY-17213Problem: When a CipherTrust Manager key is created using an auto rotation schedule on AWS cloud native key, its owner is set to "Global".
Workaround: A CipherTrust Manager administrator can assign the ownership of the key to a desired user in the CCKM Users group.

CipherTrust Database Protection

IssueSynopsis
PDB-3293Problem: If datatype of a column changes from char family to blob after migration, the Return replacement value option for the Error Replacement feature does not work.

CipherTrust Data Discovery and Classification

IssueSynopsis
KY-79798Problem: Scan fails with the "Scan results could not be found" error after processing for OneDrive and Exchange Online with some targets.
KY-75646Problem: Reports of scans on Teradata tables with unique primary index show the Key Source as "Integer Non Unique Column".
KY-75083Problem: Search for the Secrets infotypes returns less matches for the PDF data.
KY-74909Problem: Search for the Secrets infotypes returns less matches for the MongoDB data store.
KY-73411Problem: Probing an empty folder in an AWS S3 bucket returns the NotFound error.
KY-72978Problem: Search for the SSH private keys returns less matches when data for multiple infotypes is present in the same file.
KY-72411Problem: Scan on Office365 Sharepoint Online completes successfully for a non-existent file.
KY-72408Problem: Text data in Sharepoint Online Notebooks can't be matched.
KY-72397Problem: Images inserted in Sharepoint Online Notebooks can't be matched.
KY-9104Problem: Scan fails with “Error scanning. The target for Data Store XYZ cannot be accessed.” This happens when the Data Store is created and an Agent is selected for the Data Store but then the Agent is no longer available and there is no way to select a new Agent from the UI.
Workaround: Edit the Data Store and edit any configuration parameters so the DDC Server automatically searches for a new suitable Agent.
KY-9399Problem: The XVA file contains a data object that is was reported when it should not. The XVA file format is not correctly handled. After an XVA file is scanned and the report is generated, an additional data object in the Data Objects tab is displayed in the UI. You should ignore it.
KY-8990Problem: Scheduled scans and those launched manually via ‘run now’ only start after X hours. If an Agent and server have the wrong time set, DDC’s ability to schedule scans or to start them immediately when they are manually launched from the UI or API will be affected and the scan start may be delayed.
Workaround: Configure an NTP server for DDC and all Agent hosts.
Problem: None of the clustered nodes responds to requests to DDC.
DDC is only active in one of the CipherTrust Manager nodes. Requests sent to any other nodes will return this error. This will be improved in next releases.
Solution:
  • Run ksctl ddc active-node to identify the CipherTrust Manager node responsible for answering DDC requests and send the requests to the indicated IP. If this does not work, please restart the CipherTrust Manager node with that IP.
  • If the node identified by ksctl ddc active-node does not answer DDC requests correctly or is no longer active, contact Thales Customer Support.
KY-22666Problem: DDC may not scan big Data Objects for Data Stores other than local storage.
The threshold to consider is a file as big as half of the assigned scan RAM. When a DDC scan encounters a file exceeding this threshold, it may completely skip the file or scan just up to that threshold. The user has no way to identify the issue from DDC reports.
Possible Workarounds:
  • Download large files to a local storage, and run the scan on this local storage data store.
  • Increase the scan RAM as indicated in the Tuning Scan Settings section.
KY-19763Problem: OracleDB and IBM DB2: uppercase schema/table name issues.
User cannot launch Oracle/DB2 scan if schema OR table was created with lowercase and DDC is configured with lowercase.
Workaround: Set the target path in uppercase.
KY-21981Problem: Postgres tables without primary keys are not completely scanned
DDC can only scan Postgres tables if they have at least one primary key defined.
Workaround: Configure at least one primary key in the tables and run the scan again.
KY-34462Problem: In G-Drive DDC scans all the path to which the scan path is prefixed.
When scanning a specific G-Drive folder, the scan is extended onto all folder names that contain the name of the folder that you intended to scan.
KY-48874Problem: A scan with MySQL datastore (version 8.0.30) fails due to "failed status in the scanner service".
KY-49115Problem: Discrepancies in scan results of infotypes for the same file in DDC 2.10 and 2.9.
These infotypes show discrepancies:
- Australian Passport Number: 1070 (in version 2.9), 204 (in version 2.10)
- China Union Pay: 1000 (in 2.9), 921 (in 2.10)
- Discover: 1001 (in 2.9), 919 (in 2.10)
- Diners Club: 1001 (in 2.9), 1002 (in 2.10)
The above discrepancy is because of the new and improved data types, which are as follows:
- The Australian Passport Number data type has been enhanced for improved accuracy and coverage of the newer passport series, with additional updates made to enable the Australian Passport Number to be detected on the passport MRZ line.
- Discover Global Network cardholder data types including China Union Pay, Diners Club, Discover, and JCB have been updated to identify 14-19 digit primary account numbers (PANs) for all supported BIN ranges.
KY-51301Problem: For SMB Data Stores with remediation enabled, scans performed after remediation completes may not find matches in encrypted files.
Workaround: Automatic agent selection does not narrow the selection of DDC Agents to those installed on host with a CTE Agent in the Agent Group protecting the SMB GuardPoint. If DDC selects any of those agents, further scans on the SMB will read the encrypted content and therefore will be unable to find any match. In order to avoid this issue, please assign use labels to force DDC to select only the right agents as follows:
- Add one dedicated label to the DDC Agents installed on the hosts with valid CTE Agent,
- Associate that same label to the SMB Data Store, in order to guide automatic agent selection algorithm.
KY-51550Problem: Office365: OneDrive for Business - Scan progress reaches more than 100%.
KY-51586Problem: A scan of a LONGBLOB file in MySQL gets stuck while scanning.
DDC should be able to scan a 20 MB table, as LONGBLOB data type supports up to 4 GB of data, yet it fails.
KY-51623Problem: Partial Scan in BLOBs of size greater than 100 MB in MSSQL.
NOTE: If a file is partially scanned, it will be considered in the inaccessible location list.
KY-52297Problem: DDC scan fails with an empty GuardPoint path for a SMB data store.
Solution: A GuardPoint for a data store must always have a path configured in CTE.
KY-51695Problem: DDC is only able to scan the initial 4 KB of any text file stored as a large binary object in database tables.
KY-52494Problem: From this DDC version on (DDC-2.10), RHEL-compatible Agents can only be installed on environments running the matching and officially supported kernel version.
KY-52532Problem: Autopause feature not working as expected in Azure Table scans.
A scan of Azure Table with the "Autopause" feature enabled has the following issues:
  • it fails to resume after autopause end time after it enters the "Autopaused" state from the "Pending" state,
  • it fails to enter the "Autopaused" state from the "Running" state.
KY-23163Problem: A scan goes into an interrupted state for CIFS after restarting the agent.
This only happens on Windows Server agents and for the Exchange Server and Windows Local Storage.
Solution: 1) Restart the Windows agent with the scan in the "Paused" state. Then resume the scan, and it will go into the "Scheduled" state.
2)Restart the Windows agent one more time and the scan comes back to normal.
KY-53620Problem: Targeted scans of a smaller dataset in a G-Drive data store take a long time, if the overall data that is stored in G-Drive is of a larger size (for example, over 500 GB).
KY-56390Problem: Scanning of any data from an Exchange Server data store works only if the agent is installed on the same machine as the Exchange Server.
KY-60493Problem: A scan is failing with an internal error when an entire SMB share is scanned.
A scan of a full SMB datastore takes a long time and and ends with an internal error. Scanning a sub folder only gives no problem and you can generate a report.
KY-66074Problem: Azure Table: The Issue related to Azure Table Data Store has been fixed as 'Cloudant Credentials', 'Basic Auth Secret' infotypes showing correct matches if relevant data resides inside the dataset.
Mongo DB: The IBM COS HMAC Credentials infotype is getting correct matches when quotes are not used while creating the dataset. But still it will get less matches with double quotes.
For example, if the dataset has more than one pair of double quotes like so:
"IBM COS HMAC TOKEN [-secret_accesskey]:: "687a726d2d905d575248759459871a2c4f92c54bdec6b78f""
In the above example, there are quotes around the '687a726d....' string. It will be considered an escape character, and MongoDB automatically appends '\' to ensure the string is preserved correctly. Due to this '\', the infotype will skip the match.
KY-66217Problem: The 'IBM COS HMAC Credentials' infotype from DDC shows fewer matches for EBCDIC formatted dataset. The conversion of the text dataset to EBCDIC format leads to this issue.
KY-66306Problem: When Google Drive is configured to use a language other than English (e.g. Portuguese), scans specifying both 'My Drive' or 'Meu Drive ' will result in a failed/incomplete scan.
Possible Workaround: Configure English as the default language for the Google Drive Data Stores that you scan.
KY-67484, KY-71568Problem: SharePoint Online Scan functionality is currently not available for a "Specific List" and "All List" as Target.
KY-76437Problem: OneDrive: Inconsistent count of sensitive data objects after every scan of the "All Users" targets.
KY-79397Problem: AWS S3: Report generation fails for scan results of large data objects.
Workaround: On the Ambari GUI, set spark.sql.autoBroadcastJoinThreshold = -1.
KY-81147Problem: AWS S3: DDC scan incorrectly marks data objects as inaccessible.
KY-81672Problem: SharePoint Online & SharePoint Server: Scans fails when "site collection" or "site in a site collection" is added as a target path using the List option.
Workaround: Manually add the "site collection" or "site in a site collection" target path according to the defined format.
KY-83875Problem: IBM DB2: Scan fails if a target path contains a table having space in its name.
KY-88518Problem: Scan trace logs are unavailable if you initiate the clean up process through the warning banner and allow the system to stop all the running scans.
Workaround: It is recommended to manually stop the running scans before initiating the clean up process.
KY-87436Problem: When accessing scan trace logs for an in-progress scan with the Trace Log toggle disabled, an inaccessible zero-byte ZIP file of scan trace log is downloaded.
KY-84441Problem: When trying to pause or resume a scan multiple times, the scan gets stuck in the "Running" state and the "Pause is not allowed" error is logged in the log files.
KY-86569Problem: If DDC comes out of the degraded mode after shutting down the client and increasing its disk space, previously "Running" scans get stuck in the "Syncing" state and show an "Internal Error" on mouse hover.
KY-86244Problem: If DDC comes out of the degraded mode after manually deleting old files, previously "Running" scans get stuck in the "Running" state with no progress.
KY-83801Problem: MongoDB data store: Scans gets stuck in the "Processing" state if the target path contains tables with "#" and "%" in their names.

CipherTrust Secrets Management

IssueSynopsis
KY-75947Problem: OpenID Connect (OIDC) fails to authenticate during callback to CipherTrust Manager from Akeyless.
KY-86481Problem: When you update the Akeyless gateway version from the Akeyless Config (UI) and the API Playground simultaneously, the gateway version doesn't match the actual Akeyless gateway version.
Workaround: Update the version to any other than the current version from Akeyless Config (UI) or API and wait for the gateway to restart before updating it again.
KY-76477Problem: Reloading the external secrets manager (universal secrets connector) page leads to a "404 page not found" error.
Workaround: Go to Akeyless console webpage (https://CM-IP/akeyless-console/items) and open the universal secret connector again.
KY-91684Problems:
1. Upgrade from CipherTrust Manager version 2.16 to 2.17 fails if the "admin" user from the root domain is deleted.
2. Operations that require a system restart (cluster, backup-restore) will also need an "admin" user in the CipherTrust Manager version 2.17, otherwise, the operation will fail.
Workaround: Contact Thales Customer Support.
KY-77535Problem: Decrypting a secret with the DFC key that no longer exists, logs the user out abruptly from Akeyless.
Workaround: Don't decrypt a secret with the DFC key that no longer exists when a user is logged in using the SSO JWT authentication method. Instead, use other authentication methods such as API or Email.
KY-84485Problem: When you rotate the custom rotated secret of the HSM SSH user and the HSM version is lower than 7.8.4, the HSM occasionally fails to accept the newly rotated password combination and throws an error "The desired password is invalid".
Workaround: When encountering this error, rotate the secret again or upgrade the HSM version to 7.8.5 or the latest.
KY-64648Problem: The "Forgot Password" feature for email is not supported through Akeyless gateway on the CipherTrust Manager. Only "Forgot API Access Key" feature is supported.
Workaround: Use "Forgot Password" feature for email directly on the Akeyless website.
KY-70144Problem: During secret creating for Docker Hub target in Akeyless, the connection is refused.
Workaround: Add an explicit DNS Host entry to the CipherTrust Manager for Docker Hub.
KY-64835Problem: If you attempt to modify the protection key for an existing certificate-type secret in the Akeyless console, an exception stating Unexpected error is displayed.
Workaround: Delete and re-create the existing secret with the desired protection key.
KY-63288Problem: Some internet browsers, such as Mozilla Firefox, Google Chrome, or Microsoft Edge launch the secrets management tile as a pop-up, and prompt to allow pop-ups.
Workaround: Allow pop-ups from the CM UI if prompted.
KY-61568Problem: The POST /v1/connectionmgmt/services/akeyless/connections operation in the API playground to create a new Akeyless connection introduces unnecessary parameters "meta", "products", and "category".
Workaround: Ignore these parameters. They do not affect the functioning of the Akeyless connection.

CipherTrust Transparent Encryption

IssueSynopsis
KY-91010Problem: If an LDT policy contains multiple security rules, the first security rule displayed on the second page of the Security Rules tab doesn't display the check box.
KY-89451Problem: When creating an LDT policy, if you create a new transformation key but don't specify its name, the LDT key that is created has more than 64 characters in its name.
Workaround: While creating a new transformation key during policy creation, specify a key name less than 64 characters long.
KY-75999, KY-84128Problem: The CTE licenses are not updated, when the domain gets deleted from the CipherTrust Manager or the clients of a domain are migrated from DSM to CipherTrust Manager.
Workaround: If the clients of a domain are migrated from DSM to CipherTrust Manager and the license count is incorrect for that domain, create a CTE client (for example, ABC) in the same domain and then delete it. This will correct the license count for that domain.
KY-83746Problem: Intermittent: After migrating CTE resources from DSM, the details of LDT on a migrated client shows Resume Live Data Transformation (LDT paused) even though the GuardPoint is successfully Rekeyed.
Workaround: Restart the CTE Agent (service vmd restart).
KY-72096Problem: CTE UserSpace: After upgrade to CipherTrust Manager 2.14.0, CTE UserSpace 10.1.0 clients don't show the Healthy status on GUI.
This issue is resolved in the CTE-U 10.2.0 release.
Workaround: Upgrade the clients to 10.2.0 or manually restart the CTE-U services (secfs-fuse restart) to restore the client communication to the Healthy state for older CTE-U client versions.
KY-72095Problem: After upgrade to CipherTrust Manager 2.14.0, CTE clients can take up to 25 minutes to show the Healthy status on GUI. This issue has no impact on the functioning of GuardPoints.
This issue is resolved in the CTE 7.5.0 release.
Workaround: Upgrade the clients to 7.5.0 or manually restart the VMD service (secfs restart) to restore the client communication to the Healthy state for older CTE client versions.
KY-60249Problem: The get /v1/transparent-encryption/policies API does not return the complete list of policies added to the CipherTrust Manager.
Workaround: Run the get /v1/transparent-encryption/policies API with limit as -1.
KY-59893Problem: Signature rules are not copied to a clone policy.
Workaround: On the policy details page, manually add the missing signature rules.
KY-55739Problem: When a CipherTrust Manager user having only CTE Admins group permissions initiates a Quorum-dependent operation, a corresponding Quorum is created. After the required Quorum approvals, the operation does not auto-trigger in the background.
Workaround: Retry the operation after the required Quorum approvals.
KY-55511, KY-55527, KY-55275, KY-55528Problem: Simultaneous composite operations (for example, update and delete) are not supported for quorums.
KY-55273Problem: If quorum is activated for client group deletion, then bulk client group deletion generates multiple quorums in pre-active state.
Workaround: Delete client groups individually.
KY-55064, KY-54442Problem: In case of bulk client or client GuardPoint deletion, the quorum details may not be available. However, quorum operations (such as approval, rejection) can be performed.
This issue has no impact on functionality.
KY-51759, KY-51754Problem: When quorum is enabled, if you perform an operation to delete clients or GuardPoints in bulk, the quorum is created in pre-active state.
Workaround: Activate the quorum using the /v1/quorum-mgmt/quorums/{id}/activate API.
KY-51135Problem: Group members cannot be imported from ldap for user sets.
KY-34329Problem: Browsing VxVM raw devices that have slash in the path names shows non-existing directory in the GuardPaths.
Workaround: Create GuardPoints by manually entering the raw device paths.

Batch Data Transformation (BDT)

IssueSynopsis
KY-72695Problem: 500 Status code occurs when fetching BDT policies.

ProtectApp

IssueSynopsis
KSCH-16415Problem: The Host Name field on the Client Registration screen does not have validation for host availability.
Workaround: Add clients using the API.

ProtectFile

IssueSynopsis
KSCH-573Problem: Encryption rules cannot be modified to reset values for include and exclude extension parameters.
KSCH-568Problem: Encryption rules do not prevent specifying both include and exclude extension parameters simultaneously.
KSCH-567Problem: Modifying a file level encryption rule to set the “isRecursive” flag does not return error.
KSCH-564Problem: Non-encryptor clients cannot be removed from a Linux cluster while a cryptographic operation on an encryption rule is in progress.

CipherTrust Intelligent Protection

IssueSynopsis
KY-56816Problem: Unencrypted report is generated for few files if user reboot the machine during remediation.

Workaround: User need to run scan with reclassify option or full scan again to generate correct report.
KY-55480Problem: Cross domain client registration is not working with CIP.
AGT-43391Problem: All files are not encrypted on performing bulk rename during remediation on Linux Local Storage with STD/LDT policy.

Workaround: All remaining files will get encrypted after a periodic CIP scan which runs after 8 hours (default).
KY-36741Problem: File becomes plain with MOVE operation of a tagged file with ACL and STD policy on Linux.
KY-65540Problem: PQS configurations are not visible on GUI after saving remediationconfig via API using the ID/UUID for the knox_connection_identifier name.

Workaround:

• Solution 1: Use GUI to configure PQS.

• Solution 2: Use the knox_connection_identifier name instead of ID/UUID via API.

On this page