The Service Provider Tenant Usage Report and the associated tenants/usageReport, tenants/usageDetails, and service_instances/usageDetails endpoints have been removed from the platform.

As an alternative use the Service Report in the DPoD service provider tenant or the /v1/service_instances/usageBillingReport endpoint, and the  /v1/backoffice/serviceAgreements{tenantId} endpoint to compile tenant usage information.

The Luna Cloud HSM for DKE service is now available for trial and subscription. 

Provision the service through your Thales DPoD Tenant to access a Luna Cloud HSM partition and the Luna Key Broker for Microsoft DKE service software. Use the service software to create a Microsoft DKE endpoint by running the included container and connecting the Luna Cloud HSM service for secure storage of DKE cryptographic keys. 

See the Luna Cloud HSM for DKE documentation for more information about provisioning and configuring the service.

Thales Data Protection on Demand has updated the procedure for purchasing service subscriptions. Services can now be purchased through the subscriptions tab in the DPoD user interface instead of the services tab. This includes subscribing to new services, renewing expiring subscriptions, or adding quantities to an existing subscription. 

For more information see Purchasing a Service Subscription.

Thales Data Protection on Demand launched the DPoD Public Marketplace. The public marketplace is available at https://market.dpondemand.io.

The following public marketplace endpoints are now available:

• GET /service_types
• GET /service_types/ {id}
• GET /service_categories
• GET /service_categories/{id}

For more information about the DPoD API see Using the API and the DPoD Platform API.

An issue was found with the Luna Cloud HSM Support Tool version 1.0.0 where incorrect data was reported for datacentre connectivity in some cases. 

This issue has been fixed with the Luna Cloud HSM Support Tool version 1.0.2.

Luna Cloud HSM Support Tool version 1.0.2 addresses the following bug: 

• LCH-1498 - Support Tool reports incorrect info due to AuthN Changes.

FW 2.0.2 has been released to all production environments. This release resolves an issue that prevented cloning objects between two Luna Cloud HSM partitions when using the 10.5 client.

The new firmware versions based on region and FIPS mode are as follows: 

• NA FIPS - 2.0.2
• NA non-FIPS - 2.0.2
• EU FIPS - 2.0.2
• EU non-FIPS - 2.0.2

FW 2.0.2 includes the following bug fixes:

• LCH-489 - CPv4 Cloning command permissions incorrect for pre-FW-2.0 partitions.
• DPS-10104 - Luna Cloud HSM Partition Cloning Fails with the 10.5 Client

  Cloning keys between two Luna Cloud HSM partitions fails when using the 10.5 client. There are currently two possible workaround scenarios.
  -> Workaround #1 - If there is a Luna SA7 (or any other separate device to use as an intermediary for the cloning) then clone to and from that device.

  -> Workaround #2 - If there is no separate device then completely uninstall the 10.5 client and install the 10.4 client from scratch. For this option please raise a support ticket to the Thales Customer Support portal to request to join the 2 partitions together as the 10.4 client does not support dynamic partition loading.

The CipherTrust Data Security Platform as a Service (CDSPaaS) is now available for provisioning through Thales Data Protection on Demand.

For more information about CDSPaaS see CipherTrust Data Security Platform Services (CDSPaaS).

For more information about provisioning the service and getting started with CDSPaaS see Get Started with CipherTrust Data Security Platform Services.

The new Universal Client Supported Versions with Luna Cloud HSM policy has been created. This outlines the date of the released Universal Clients and their 'end of support' timelines.

If your Universal Client is found to be no longer supported it is strongly recommended that you upgrade to the latest version at your earliest convenience. 

See Upgrading your Client for more information.

The DPoD Key Broker for Google Cloud EKM service now supports the following Key Access Justification reason codes:

• GOOGLE_RESPONSE_TO_PRODUCTION_ALERT
• MODIFIED_GOOGLE_INITIATED_SYSTEM_OPERATION

For more information about the service see Key Broker for Google Cloud EKM. For more information about the newly supported codes see Key Access Justification Reason Codes.