Configure Encryption Key Management

From the Encryption Key Management screen, customer's can import and manage their Key Encryption Key (KEK). Only customer cloud administrators can see this page. It not visible to the customer's Service Provider Administrator (SPA).

To access this feature, the customer's Service Provider Administrator (SPA) must assign the <View Tenant KMS Keys> and <Edit Tenant KMS Keys> privileges to the customer cloud administrator's user account.

Before you begin

Contact Support to confirm that AWS Key Management Server (KMS) is available for the customer's Cloud platform Predefined logical group of server roles installed together on a physical server.. If AWS KMS is supported, Set up the AWS Key Encryption Key (KEK)

Procedure

Go to System Management. Under System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager., select Feature Settings.
Select Encryption Key Management.
Complete the AWS KMS encryption settings for bring your own key.
Click Validate settings ().
Click Save ().

The customer can change their KEK, but deletion is not possible to ensure that the customer always has access to the interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. media and transcription Process in Speech Analytics of converting audio files of the recorded agent-customer conversation to text. data that this key encrypts. If a customer needs to revoke a key, they must do so from their KMS system.

If the Verint system cannot access the customer's Key Encryption Key (KEK), Verint cannot decrypt the interactions captured for employees; so playback Process of selecting a recorded interaction, playing it back to listen to the call, and viewing the content of the interaction on the screen., export, analysis, and transcription fail.

For this reason, keep available to Verint all versions of the customer KEK that correspond to the retention period of the customer's captured interactions. If a KEK is corrupted or deleted, Verint cannot restore or access the customer's data. As Verint does not receive and is not obligated to receive or back up the customer’s KEK, Customers should ensure that they manage their own back-up of all KEKs required for Verint to access and restore backups of KEK-encrypted customer data.