This notification is to alert you that we are beginning the End-of-Life (EOL) process for the following Thales Trusted Cyber Technologies (TCT) KeySecure for Government appliances.
KeySecure for Government will reach End-of-Sale effective 31-Dec-2022, and End-of-Life by 31-Dec-2023. Thales TCT KeySecure G160 is not included in these timelines.
Existing KeySecure for Government customers have several options for migrating from KeySecure for Government to the CipherTrust Data Security Platform. For more information on migration options, please contact your Thales TCT account manager or firstname.lastname@example.org.
Thales TCT is pleased to announce the release of KeySecure for Government 8.15. Continuing our commitment to provide innovative products that meet our customers’ security needs, KeySecure 8.15 contains a number of customer requested enhancements, product maintenance items, and documentation improvements. KeySecure 8.15 is available on all platforms: G460, G160 (Standard and High Assurance), G350v (VMware and AWS) as both an orderable product and a field upgrade package. Review the Customer Release Notes for additional information on the improvements included in this release.To learn more about KeySecure for Government, visit www.thalestct.com/keysecure
SafeNet AT is pleased to announce the release of KeySecure for Government 8.14. Continuing our commitment to provide innovative products that meet our customers’ security needs, KeySecure 8.14 contains a number of customer requested enhancements, product maintenance items, and documentation improvements. KeySecure 8.14 is available on all platforms: G460, G160 (Standard and High Assurance), G350v (VMware and AWS) as both an orderable product and a field upgrade package.
Review the Customer Release Notes for additional information on the release including the following new features and enhancements:
To learn more about KeySecure for Government, visit www.safenetat.com/keysecure.
As cloud service providers such as Microsoft roll out new services at a staggering rate, customers must take advantage of these capabilities while still fulfilling their obligation to “own the data” by securing the data with encryption and cloud independent key management. Now, customers can leverage the encryption capabilities built into the Microsoft cloud while using SafeNet AT KeySecure for Government to manage and maintain ownership of their encryption keys.
Using the ProtectApp APIs supported by KeySecure for Government and Azure Key Vault, SafeNet AT has developed a reference tool called SafeNet AT ManageAKV that implements the integration between KeySecure for Government and Azure Key Vault. The ManageAKV tool securely authenticates to KeySecure for Government (using the ProtectApp Java/JCE SDK) and Azure (using the Azure APIs) and is used as the secure conduit to issue commands to KeySecure for Government and Azure Key Vault related to the management of customer managed keys.
The ManageAKV tool is provided as part of ProtectApp JCE. For more information, download the Azure Key Vault and KeySecure for Government Solution Brief.
KeySecure for Government 8.12.1 is now available. This release specifically addresses an issue found in release 8.12.0 concerning the SafeNet Virtual KeySecure G350v connected to a Remote HSM, both VMWare and AWS. It was discovered that after successfully registering a G350v to a remote HSM, object such as Keys, Local CAs, Certificates and Cluster Keys cannot be created. SafeNet AT strongly recommends implementing release 8.12.1 for VMWare instead of release 8.12.0 to forestall any possible issues with remote HSM functionality. Customers who use G350v on AWS should remain on version 8.11.0. This ONLY effects Virtual KeySecure G350vs that are registered to a Remote HSM. All other KeySecure platforms (G460 and G160) are NOT affected, nor are G350vs that do not register to a Remote HSM. If you are NOT using a Remote HSM then release 8.12.0 may be used for G350v (VMWare or AWS).