Decoding the world of cybersecurity

Eviden extends sovereign encryption to Microsoft Azure

Eviden has extended external encryption key management to Microsoft Azure. Two deployment models allow organisations to retain control over cryptographic roots of trust while using Azure cloud services.

Eviden extends sovereign encryption to Microsoft Azure
Summary
  • Eviden KMS now supports external key management for Azure Key Vault Managed HSM.
  • Customers can operate Eviden KMS and Proteccio HSM outside Azure, or run KMS within an Azure confidential virtual machine while keeping the HSM external.
  • Both arrangements separate critical cryptographic control from cloud workloads, although connectivity, availability and key administration remain operational considerations.

Organisations running sensitive workloads on Microsoft Azure can now use external cryptographic key management from Eviden, extending the options available to businesses seeking greater control over their encryption infrastructure.

Eviden, the Atos Group's cybersecurity and technology business, introduced support for Azure Key Vault Managed HSM external key management on 18 November 2026. The integration forms part of its Bring Your Own Sovereign Encryption offering, known as BYOSE.

Two deployment architectures are available, both using Eviden's Key Management System (KMS) and Proteccio hardware security module (HSM). They differ in where the key management software operates, but both retain the hardware root of trust outside Azure.

The expansion follows the general availability of Microsoft's external key management capability for Azure, which allows organisations to connect supported cryptographic infrastructure to services running in its cloud.

Two architectures separate key management from cloud workloads

Under the first model, both Eviden KMS and Proteccio HSM operate outside Azure, in infrastructure controlled by the customer. The components communicate with Azure through its external key management interface, maintaining the cryptographic root of trust separately from the environment hosting the protected workloads.

This arrangement gives organisations direct responsibility for the infrastructure managing their keys. It also means that connectivity between the cloud environment and external cryptographic systems becomes an important part of service availability.

The second model places Eviden KMS inside an Eviden Confidential VM running on Azure, while Proteccio HSM remains outside the cloud. Eviden describes the external HSM as providing both the sovereign root of trust and secure backup for the hybrid arrangement.

Running KMS closer to cloud workloads is intended to reduce some of the network and performance implications of managing encryption keys entirely outside the platform. The company says this configuration supports protection of sensitive information at rest and during processing.

Those are vendor-described capabilities rather than independently verified performance comparisons. Organisations evaluating either approach need to establish the security and availability characteristics of their intended deployment, particularly where applications depend on timely access to cryptographic services.

Control of encryption keys introduces operational responsibilities

Cloud providers offer native encryption services, but some organisations require greater separation between the infrastructure holding their information and the systems controlling the keys used to protect it.

Externally managed keys can provide that separation. However, keeping a cryptographic root of trust outside a cloud platform does not mean that every element of the associated application operates independently of the provider.

Applications may continue to depend on Azure computing, storage, networking and identity services. Their security also depends on the permissions available to administrators and the configuration of the software using the protected information.

The organisation responsible for external key management must maintain suitable access controls, monitoring and recovery arrangements. A key management system that becomes unavailable may prevent an otherwise functioning application from accessing information it needs.

Revoking a key can be an effective security control where access must be withdrawn, but an unintended revocation or configuration error can also interrupt legitimate services. These consequences need to be considered when designing emergency procedures and testing recovery arrangements.

The two Eviden architectures present different operational dependencies. A configuration with KMS entirely outside Azure relies on external infrastructure and connectivity, while a configuration using an Azure confidential virtual machine introduces an additional cloud-hosted component into the key management process.

European organisations examine cryptographic sovereignty

Financial institutions, public bodies and critical infrastructure operators are increasingly examining the jurisdictional and operational arrangements governing sensitive cloud services.

European regulations such as the Digital Operational Resilience Act place obligations on affected financial institutions to manage technology risk, operational resilience and external service dependencies. They do not impose a universal requirement to use externally controlled encryption keys.

Nevertheless, organisations may identify key ownership, administrative access and supplier relationships as relevant considerations when assessing cloud deployments against their regulatory and contractual obligations.

Cryptographic architecture also affects future migration. Applications that depend closely on a provider's proprietary security services may require additional work when changing infrastructure, while an external key management system can provide a degree of separation from the underlying hosting environment.

That separation does not guarantee portability. Compatibility with the applications, interfaces and cryptographic services involved still needs to be assessed.

Eviden has extended its sovereign encryption capabilities to other cloud environments, including Salesforce Hyperforce and the AWS European Sovereign Cloud. The Azure integration broadens that offering without replacing its existing deployments.

The company has confirmed support for both Azure deployment architectures but has not published independently verified comparative performance measurements or customer adoption figures for the new configurations.

×