The Thales Data Protection on Demand Terms of Service have been updated. Please review the Terms of Service for more information.
The Thales Data Protection on Demand Terms of Service have been updated. Please review the Terms of Service for more information.
In the upcoming release of FW 3.0 for Luna Cloud HSM, CPv1 will be removed from FIPS firmware support as it is no longer compliant with 140-3. As this only affects FIPS mode, all affected users should use CPv4 or transition service to non-FIPS mode. If Luna Network HSM users want to clone to Luna Cloud HSM with a FIPS partition they will have to use Luna 7.8 or higher. See Universal Cloning for more information.
Luna Cloud HSM Datacenters are now configured with a floating IP address. Users should be aware that any client configuration that relies on a static IP address configuration will no longer function.
Please see the Client Network Connectivity Documentation for information about configuring your client environment. Thales does not recommend using any static IP filtering when accessing the service. Should your configuration require the use of static IP address filtering, please contact Thales Customer Support for more information.
The certificate CA provider for the platform authentication service is being changed to Sectigo, a global leader in digital identity security solutions. The scheduled time for this change is detailed on the DPoD Status Dashboard.
Please be aware that you may need to update your system's certificates and ensure that CA CRL and OCSP endpoints are reachable in accordance with this change.
If you require assistance or have any inquiries please contact our Support Team using the Thales Customer Support Portal.
Users can now subscribe to individual components through the Thales Data Protection on Demand Status Page. When you subscribe to updates you can specify the DPoD components, services and regions that you would like to receive updates for.
To become a subscriber or update your subscription visit the Thales Data Protection on Demand Status Page and click Subscribe to Updates.
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 has made the following changes to how billing and service subscriptions work in DPoD:
Tenants that have an accepted Service Elections form will have the following changes:
Tenants that do not have an accepted Service Elections form will have the following changes:
Note: If your tenant is unable to retrieve and display subscriptions please contact Thales support to resolve the issue. You will be unable to provision new services until the issue is resolved.
The Service Provider Tenant Usage Report and the associated tenants/usageReport
, tenants/usageDetails
, and service_instances/usageDetails
endpoints are deprecated and will be removed from the platform by the end of 2023.
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.
When Max Session Objects goes over 100 the user will now receive the following error message: CKR_MAX_OBJECT_COUNT_EXCEEDED.
Previously there was no session object limit set therefore there was no message sent to the user.
The firmware versions for Luna Cloud HSM Services operating in NA and EU non-FIPS environments have been updated. The current firmware version based on region and FIPS mode are as follows:
Universal Cloning
Universal Cloning (CPv4) is now a supported feature when combining UC 10.5.0 and Firmware 2.0. Universal Cloning can be used for key migration to any trusted Thales HSMs that also support the Universal Cloning protocol.
In order to use the Universal Cloning feature, the following must be true:
NOTE: You can only clone between initialized partitions, and they must have the same cloning domain (secret), which is provided at the time of initialization.
More info can be found here: Universal Cloning.