Double encryption for Next® as a Service

As part of our ongoing efforts to keep Next® as service safe and compliant with GDPR, we have finalized our rollout of double encrypted disk sets, with customer managed keys in Microsoft Azure. 

From design, Next® already supports strong encryption of all 'data in transit' using Transport Layer Security (TLS), and in Next® as a Service we use TLS v 1.2.

For 'data at rest', you get the far best encryption using infrastructure based encryption - such as Microsoft's encrypted disk sets. The only challenge being that when Microsoft manage the keys, they also have access to your data. Not that we don't trust Microsoft, but from a GDPR point of view trust it is not enough, when you are dealing with a US based company. Even when data is located in the EU. That is why we have introduced another layer of encryption, where we manage the keys - CMK - customer managed keys. 

For the techie ones

For encryption of 'data at rest', on premise, we generally recommend using OS specific features such as DM-Crypt for Linux or BitLocker for Windows. Using infrastructure encryption provides the best possible performance and a minimum of inconveniences. For Next® as a Service running on Microsoft Azure, we have implemented encrypted disk sets using customer managed keys, in addition to the encryption already in place using platform managed keys. Azures encryption uses 256-bit AES encryption, one of the strongest block ciphers available, and is FIPS 140-2 compliant. 

For customers requesting the maximum level of security we recommend Next® as a Service.

Additional information

Please refer to the online product guide for additional information on this feature, once it is released.

Commercial terms and conditions

This functionality is an integrated part of our Next® as a Service offering. 


Despite our best efforts, we may be forced to change both content and expected delivery of future product updates without notice.



Double encryption for Next® as a Service


New standard feature



Expected release:

November 21

Affected products:

Next® as a Service





Responsible product manager:

Kim Hellum




Kim Hellum