Managing DKE Endpoints
This section describes how to manage DKE endpoints from CCKM.
Microsoft Double Key Encryption (DKE) service can access CipherTrust Cloud Key Manager (CCKM) after you meet some prerequisites. Refer to Microsoft Double Key Encryption (DKE) Resources for more information about Microsoft DKE and the prerequisites.
Part of the prerequisites is creating a DKE endpoint. After you have created a DKE endpoint, you can:
Note
Users of the CCKM Admins group can manage DKE endpoints, whereas the users of the CCKM Users group can only view the DKE endpoints.
Creating DKE Endpoints
From CCKM GUI, create a DKE endpoint to make it available to the Microsoft DKE service. You can either create a new key encryption key (KEK) or select an existing KEK for the getkey and decrypt operations. If you do not specify a key, CCKM will automatically create a CipherTrust Manager key for you.
Note
-
If you plan to use the authorization method of Role ID for the access settings of DKE keys, you are required to set up an Azure connection before creating a DKE endpoint. For more information on how to add an Azure connection, refer to Microsoft Azure Connection.
-
In the Microsoft Azure application, go to the API Permissions section and configure the Directory.Read.All permission. Ensure that the
Typefor this permission is Application.
To create a DKE endpoint from the CCKM GUI:
-
Log on to the CipherTrust Manager GUI as administrator.
-
Open the Cloud Key Manager application.
-
In the left pane, click Services > Microsoft DKE. The Microsoft Double Key Encryption (DKE) page is displayed.
-
Click Create Endpoint. The Add Double Key Encryption (DKE) Endpoint dialog box is displayed.
-
Under General Info, enter a unique Name and a description for the endpoint.
-
Click Next.
-
Under Endpoint Settings, provide the following settings:
-
Key URI Hostname. Enter the hostname at which CipherTrust Manager will be visible to Microsoft.
Note
The Key URI Hostname will be used to construct the URL Google will use to send requests to CipherTrust Manager and for JWT validations.
The web interface of the CipherTrust Manager must have a valid TLS certificate signed by a trusted CA.
If the SSL termination takes place at the CipherTrust Manager, the Key URI Hostname must match the FQDN of the CipherTrust Manager. If the SSL termination takes place at the load balancer in front of the CipherTrust Manager, the Key URI Hostname must match the FQDN of the public-facing load balancer. Wildcard certificates are supported.
If you changed the web interface port within CipherTrust Manager from the default port of 443 to another port, ensure to add that same port number when configuring Key URI Hostname by specifying the new port number along with the Key URI Hostname. For example, example.com:8443.
-
Key Algorithm. The only option available for the DKE key algorithm is RSA_DECRYPT_OAEP_2048_SHA256. This box is greyed out.
-
Enable success audit events. Use this toggle to enable or disable audit recording of successful Microsoft DKE operations on this endpoint. This is optional. By default, this toggle is turned on.
-
-
Click Next.
-
Under Key Material, choose to either create a new key or copy an existing key.
Note
If you do not specify a key, CCKM will automatically create a CipherTrust Manager key for you.
If creating a new key, select Create New Key, enter the Key Name. If copying an existing key, select Copy Existing Key, select a key from the Key drop-down list.
-
Click Next.
-
Under Authorization Parameters, provide the following settings:
-
Valid Issuer. Add a trusted issuer for the DKE endpoint.
An example of a valid issuer is
https://sts.windows.net/azure tenant ID/.Note
This issuer must match the issuer within the JWT that the CCKM receives.
-
Select Authorization Method for the authorization method to the access settings of DKE keys. Select only one of the following options:
-
Use Email(s) allows your organization to authorize access to DKE keys based on email addresses only.
If you select Use Email(s), under Add Email(s), enter the email addresses that are authorized to use the DKE key and then click Add Email(s). Your entries display under Email(s).
Note
The use of wildcards '*' and '?' are supported for email addresses. The following are examples of supported wildcard formats:
-
abc*@gmail.com: supports any email that starts with abc and ends with "@gmail.com".
-
abc@?.com: supports any email that starts with abc, contains "@" followed by at least one character and ends with ".com".
-
abc@?.?*: supports any email that starts with abc, contains "@" followed by at least one character, followed by the dot character (.), and ends with at least one character.
-
?*@gmail.com: supports any email that starts with at least one character and ends with "@gmail.com".
-
-
Use Role ID(s) allows your organization to authorize access to keys based on Active Directory groups. The format is
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxwherexis an alphanumeric character.If you select Use Role ID(s), under Select Azure Connection drop-down menu, select the Azure connection to use for this DKE endpoint. Then under Add Role ID(s), add the role IDs that are authorized to use the DKE key and then click Add Role ID(s). Your entries display under Role ID(s).
To find out the role ID in Azure:
-
Log on to the Microsoft Entra portal.
-
In the left pane, click Identity > Users > All users.
-
On the Users page, search for the desired user.
-
Under Display Name, click the user name link. The details of the selected user are displayed.
-
Click Assigned roles. The Active assignments tab shows the roles currently assigned to the user.
-
Note down the role for which you want to find out the role ID.
-
In the left pane, click Roles & admins > Roles & admins. The Roles and administrators page displays all roles on the right.
-
Search and select the role you noted down earlier. The "<user role> | Assignments" page is displayed.
-
Under Manage, click Description. The Summary of the role is displayed.
-
Copy the value of Template ID.
-
-
-
-
Click Next.
-
Under Review and Add, review the details you provided for the new endpoint. These details are divided into GENERAL INFO, ENDPOINT SETTINGS, KEY MATERIAL, AUTHORIZATION PARAMETERS sections.
Note
After the endpoint is added, KEY MATERIAL will no longer be editable.
-
Click Add Endpoint.
The endpoint creation starts. A Create Endpoint In Progress message is displayed on the screen. Leave the window open until the process is completed.
-
Click Close. The Add Double Key Encryption (DKE) Endpoint wizard is closed.
The newly created endpoint is displayed in the list of Microsoft DKE endpoints.
Viewing DKE endpoints
The Microsoft Double Key Encryption (DKE) page shows the list of existing DKE endpoints residing within a given URI hostname. Search for endpoints by endpoint name or key URI.
To view the list of DKE endpoints available on CCKM:
-
Open the Cloud Key Manager application.
-
In the left pane, click Services > Microsoft DKE. The Microsoft Double Key Encryption (DKE) page is displayed. The list of DKE endpoints added to CCKM is displayed. The page displays the following details:
Field Description Name Name of the DKE endpoint. Key URI Base url hostname for KeyURI. Status State of the key. The status can be:
• Enabled
• DisabledKEK Name Name of KEK. Key Version Version of the key. Algorithm DKE key algorithm. The only option currently supported is RSA_DECRYPT_OAEP_2048_SHA256, which is the default value. Authorization Method Authorization type for DKE key: Email or Role ID. Creation Date Time when the endpoint was created. Last Modified Date and time the DKE endpoint was modified. Timestamp in format Day-Month-Year time in 24-hour notation. Description Description for the endpoint.
To view the custom columns, click the Customize View (
) icon, select the desired option(s), and click OK to display the column(s).
Viewing and editing details of a DKE endpoint
After an endpoint is created, you can view and modify the endpoint details, such as the endpoint name and authorization parameters.
This section describes how to view the details of a DKE endpoint and update details relating to GENERAL INFO, ENDPOINT SETTINGS, and AUTHORIZATION PARAMETERS as needed.
To view and edit the details of Microsoft DKE endpoints on CCKM:
-
Log on to the CipherTrust Manager GUI as administrator.
-
Open the Cloud Key Manager application.
-
In the left pane, click Services > Microsoft DKE. The Microsoft Double Key Encryption (DKE) page is displayed. The list of DKE endpoints added to CCKM is displayed.
-
Click the Name link of the desired DKE endpoint.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click View/Edit.
The edit view of the Microsoft Double Key Encryption (DKE) page is displayed.
Under GENERAL INFORMATION
-
(Optional) Update the description of the DKE endpoint in the Description field.
-
Click Update.
Under ENDPOINT SETTINGS
-
(Optional) Enter a new Key URI hostname to use a different URI hostname.
-
(Optional) Depending on current setting, set the Enable success audit events toggle to enable or disable audit recording of successful operations related to Microsoft DKE operations on this endpoint.
-
Click Update.
Under AUTHORIZATION PARAMETERS
-
(Optional) Update the trusted issuer for the DKE endpoint in Valid Issuer.
-
(Optional) Depending on which authorization method you previously configured:
If using Email authorization
- In Add Email(s), enter additional email addresses and then click Add Email(s). Your new entries display under Email(s). You can also delete an email address previously added by clicking the trash can icon next to the email address you wish to delete.
If using Role authorization
-
(Optional) In Select Azure Connection, change an Azure connection.
-
In Add Role ID(s), enter additional role IDs and then click Add Role ID(s). Your entries display under Role ID(s). You can also delete a role ID previously added by clicking the trash can icon next to the role ID you wish to delete.
-
Click Update.
Enabling a DKE endpoint
From the Microsoft Double Key Encryption (DKE) page, you can enable a DKE endpoint. Enabling a DKE endpoint allows the getkey and decrypt/unwrap operations for the given Microsoft DKE endpoint.
To enable a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to enable.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the Actions drop-down menu, select Enable. The Enable Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Enable. The Enable Endpoint dialog box displays. -
Click Enable to proceed. After the endpoint is successfully enabled, a message displays indicating "Successfully enabled Microsoft DKE endpoint".
Disabling a DKE endpoint
From the Microsoft Double Key Encryption (DKE) page, you can disable a DKE endpoint. Disabling a DKE endpoint disallows the getkey and decrypt/unwrap operations for the given Microsoft DKE endpoint.
To disable a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to disable.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the Actions drop-down menu, select Disable. The Disable Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Disable. The Disable Endpoint dialog box displays. -
Click Disable to proceed. After the endpoint is successfully disabled, a message displays indicating "Successfully disabled Microsoft DKE endpoint".
Rotating a DKE endpoint
From the Microsoft Double Key Encryption (DKE) page, you can rotate a DKE endpoint, which adds a new KEK version to this endpoint. Subsequent encrypt/wrap operations this endpoint performs will use the new version of the key. Decrypt/Unwrap operations will use whichever version of the key was originally used to encrypt/wrap.
Rotating a DKE endpoint's KEK can be done even if the endpoint is disabled. Rotating the KEK regularly is a security best practice.
To rotate a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to rotate.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the VERSIONS, click Rotate. The Rotate Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Rotate. The Rotate Endpoint dialog box displays. -
Click Rotate to proceed. After the endpoint is successfully rotated, a message displays indicating "Successfully rotated Microsoft DKE endpoint". The new key version displays in list of key versions under the VERSIONS of the edit view of the Microsoft Double Key Encryption (DKE) page.
Deleting a DKE Endpoint
From the Microsoft Double Key Encryption (DKE) page, you can delete a DKE endpoint. The getkey and decrypt operations associated with this endpoint are also deleted from the database as part of the deletion. Essentially, the record of this endpoint is deleted from the database and CCKM. A deleted endpoint is no longer included in the list DKE endpoints displayed on the Microsoft Double Key Encryption (DKE) page.
Note
Before deleting a DKE endpoint, you must first archive it.
To delete a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to delete.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the Actions drop-down menu, select Delete. The Delete Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Delete. The Delete Endpoint dialog box displays. -
Enable the I wish to delete this endpoint checkbox and click Delete. After the endpoint is successfully deleted, a message displays indicating "Successfully deleted Microsoft DKE endpoint".
Archiving a DKE Endpoint
From the Microsoft Double Key Encryption (DKE) page, you can archive a DKE endpoint. Archiving allows you preserve a record of this endpoint in “Archived” state, which can be recovered thereafter.
Note
-
An archived DKE endpoint does not consume a CCKM license.
-
When a key is in archived state, it can be viewed, recovered, or deleted. It is included in the list of DKE endpoints on the Microsoft Double Key Encryption (DKE) page.
-
A new KEK version cannot be added to an Archived DKE endpoint as this endpoint cannot be rotated.
To archive a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to archive.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the Actions drop-down menu, select Archive. The Archive Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Archive. The Archive Endpoint dialog box displays. -
Enable the I wish to archive this endpoint checkbox and click Archive. After the endpoint is successfully archived, a message displays indicating "Successfully archived Microsoft DKE endpoint".
Recovering a DKE Endpoint
From the Microsoft Double Key Encryption (DKE) page, you can recover a DKE endpoint. Recovering a DKE endpoint in an archived state allows you enable the endpoint thereby allowing subsequent requests for the getkey and decrypt/unwrap operations for the endpoint.
Note
An recovered DKE endpoint consumes a CCKM license.
To recover a DKE endpoint on CCKM:
-
Click the Name link of the desired DKE endpoint you wish to recover from an archived state.
The edit view of the Microsoft Double Key Encryption (DKE) page displays. -
Under the Actions drop-down menu, select Recover. The Recover Endpoint dialog box displays.
Alternatively, click the overflow icon (
) corresponding to the desired DKE endpoint, and click Recover. The Recover Endpoint dialog box displays. -
Enable the I wish to recover this endpoint checkbox and click Recover. After the endpoint is successfully recovered, a message displays indicating "Successfully recovered Microsoft DKE endpoint".