Home
%3CLINGO-SUB%20id%3D%22lingo-sub-839122%22%20slang%3D%22en-US%22%3EData%20encryption%20with%20Customer%20Managed%20keys%20for%20Azure%20Event%20Hubs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-839122%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20excited%20to%20announce%20the%20public%20preview%20of%20data%20encryption%20at%20rest%20with%20Customer%20Managed%20Keys%20support%20for%20Azure%20Event%20Hubs.%20Azure%20Event%20Hubs%20provides%20encryption%20of%20data%20at%20rest%20and%20in%20transit.%20By%20default%2C%20Event%20Hubs%20uses%20Azure%20Storage%20Service%20Encryption%20using%20Microsoft-managed%20keys%20to%20encrypt%20the%20data.%20With%20Customer%20Managed%20keys%20support%2C%20customers%20now%20have%20the%20choice%20of%20encrypting%20the%20data%20with%20the%20keys%20managed%20by%20the%20customers.%3C%2FP%3E%0A%3CP%3EData%20encryption%20for%20Event%20Hubs%20with%20customer%20managed%20keys%20uses%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fservices%2Fkey-vault%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Key%20Vault%3C%2FA%3E.%20Azure%20Key%20Vault%20uses%20hardware%20security%20models%20(HSMs)%20that%20are%20Federal%20Information%20Processing%20Standards%20(FIPS)%20140-2%20Level%202%20validated.%20Access%20to%20a%20key%20vault%20requires%20proper%20authentication%20and%20authorization%20before%20you%20can%20get%20access.%20Authentication%20is%20done%20via%20Azure%20Active%20Directory%20and%20Authorization%20via%20role-based%20access%20control%20(RBAC).%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-2016598435%22%20id%3D%22toc-hId-2016598435%22%3E%3CFONT%20size%3D%225%22%3EHow%20this%20works%3F%3C%2FFONT%3E%3C%2FH1%3E%0A%3CP%3ETo%20enable%20data%20encryption%20with%20customer%20managed%20keys%2C%20Event%20Hubs%20assumes%20that%20customer%20Azure%20Active%20Directory%2C%20Key%20Vault%20and%20customer%20key%20(used%20for%20encryption)%20are%20available.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ECustomer%20creates%20an%20Event%20Hubs%20namespace%20in%20their%20Dedicated%20Event%20Hubs%20cluster%20and%20enables%20customer%20managed%20key%20encryption.%3C%2FLI%3E%0A%3CLI%3ECustomers%20start%20accessing%20the%20namespace%20to%20send%20and%20receive%20data.%3C%2FLI%3E%0A%3CLI%3EEach%20time%20a%20send%20and%2For%20a%20receive%20operation%20is%20initiated%2C%20Event%20Hubs%20needs%20to%20obtain%20the%20customer%20managed%20key%20from%20Azure%20Key%20Vault.%20The%20service%20then%20unwraps%20to%20send%20and%20receive%20the%20event%20data.%3C%2FLI%3E%0A%3CLI%3EEvent%20Hubs%20service%2C%20automatically%20handles%20this%20using%20Azure%20Active%20Directory%20and%20managed%20service%20identity%20to%20access%20customers%20key%20vault.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3COL%3E%0A%3CLI%20style%3D%22list-style-type%3A%20none%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F130517i40D46A654AB63326%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EThe%20data%20encryption%20with%20customer%20managed%20keys%20are%20enabled%20only%20on%20namespaces%20in%20Dedicated%20Event%20Hubs%20clusters%20and%20are%20not%20available%20for%20Standard%20Event%20Hubs%20namespaces.%20Once%20the%20namespace%20is%20enabled%20with%20customer%20managed%20key%20encryption%2C%20there%20is%20no%20opting%20out%20of%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20the%20encryption%20is%20enabled%2C%20customers%20can%20rotate%20their%20key%20in%20Azure%20Key%20Vault%2C%20this%20may%20be%20for%20compliance%20policies%20or%20security%20reasons.%20When%20the%20key%20rotation%20happens%2C%20Event%20Hubs%20re-encrypts%20the%20customer%20managed%20key%20for%20the%20Event%20Hubs%20resources.%20This%20is%20automatically%20taken%20care%20by%20the%20service%20and%20does%20not%20result%20in%20re-encrypting%20the%20entire%20data%20and%20there%20is%20no%20action%20the%20customer%20would%20need%20to%20take.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUsing%20customer-managed%20keys%20with%20Event%20Hubs%20requires%20%3CSTRONG%3ESoft%20Delete%20%3C%2FSTRONG%3Eand%20%3CSTRONG%3EDo%20Not%20Purge%20%3C%2FSTRONG%3E%26nbsp%3Bproperties%20enabled%20to%20help%20protect%20customers%20from%20ransomware%20scenarios.%3C%2FP%3E%0A%3CP%3EEnabling%20this%20feature%20targets%20enterprise%20customers%20looking%20to%20protect%20sensitive%20data%20as%20part%20of%20their%20regulatory%20or%20compliance%20needs%20like%20the%20HIPAA%2C%20BAA%20compliance.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%3A%20Customer%20managed%20key%20for%20encryption%20with%20Event%20Hubs%20can%20be%20enabled%20only%20on%20Event%20Hubs%20namespaces%2C%20that%20are%20under%20a%20Dedicated%20Event%20Hubs%20cluster.%20Event%20Hubs%20cluster%20is%20Kafka%20enabled%20by%20default.%20Create%20a%20Dedicated%20cluster%20in%20the%20portal%20by%20following%20this%20link%20-%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Feventhubsclusterquickstart%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%20style%3D%22font-family%3A%20'Segoe%20UI'%3B%20font-size%3A%2010.5pt%3B%22%3Ehttps%3A%2F%2Faka.ms%2Feventhubsclusterquickstart%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELearn%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fevent-hubs%2Fevent-hubs-dedicated-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EEvent%20Hubs%20Dedicated%20clusters%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EHave%20questions%3F%20Email%20us%20at%20askeventubs%40microsoft.com%3C%2FLI%3E%0A%3CLI%3ELearn%20more%20about%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fevent-hubs%2Fconfigure-customer-managed-key%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECustomer%20managed%20keys%20for%20encrypting%20Event%20Hubs%20data.%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EHave%20comments%3F%20We%20would%20love%20to%20hear%20from%20you%2C%20please%20leave%20your%20comments%20below.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-839122%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20excited%20to%20announce%20the%20public%20preview%20of%20data%20encryption%20at%20rest%20with%20Customer%20Managed%20Keys%20support%20for%20Azure%20Event%20Hubs.%20Azure%20Event%20Hubs%20provides%20encryption%20of%20data%20at%20rest%20and%20in%20transit.%20By%20default%2C%20Event%20Hubs%20uses%20Azure%20Storage%20Service%20Encryption%20using%20Microsoft-managed%20keys%20to%20encrypt%20the%20data.%20With%20Customer%20Managed%20keys%20support%2C%20customers%20now%20have%20the%20choice%20of%20encrypting%20the%20data%20with%20the%20keys%20managed%20by%20the%20customers.%3C%2FP%3E%3C%2FLINGO-TEASER%3E

We are excited to announce the public preview of data encryption at rest with Customer Managed Keys support for Azure Event Hubs. Azure Event Hubs provides encryption of data at rest and in transit. By default, Event Hubs uses Azure Storage Service Encryption using Microsoft-managed keys to encrypt the data. With Customer Managed keys support, customers now have the choice of encrypting the data with the keys managed by the customers.

Data encryption for Event Hubs with customer managed keys uses Azure Key Vault. Azure Key Vault uses hardware security models (HSMs) that are Federal Information Processing Standards (FIPS) 140-2 Level 2 validated. Access to a key vault requires proper authentication and authorization before you can get access. Authentication is done via Azure Active Directory and Authorization via role-based access control (RBAC).

How this works?

To enable data encryption with customer managed keys, Event Hubs assumes that customer Azure Active Directory, Key Vault and customer key (used for encryption) are available.

 

  1. Customer creates an Event Hubs namespace in their Dedicated Event Hubs cluster and enables customer managed key encryption.
  2. Customers start accessing the namespace to send and receive data.
  3. Each time a send and/or a receive operation is initiated, Event Hubs needs to obtain the customer managed key from Azure Key Vault. The service then unwraps to send and receive the event data.
  4. Event Hubs service, automatically handles this using Azure Active Directory and managed service identity to access customers key vault.
  1. clipboard_image_0.png

The data encryption with customer managed keys are enabled only on namespaces in Dedicated Event Hubs clusters and are not available for Standard Event Hubs namespaces. Once the namespace is enabled with customer managed key encryption, there is no opting out of this.

 

Once the encryption is enabled, customers can rotate their key in Azure Key Vault, this may be for compliance policies or security reasons. When the key rotation happens, Event Hubs re-encrypts the customer managed key for the Event Hubs resources. This is automatically taken care by the service and does not result in re-encrypting the entire data and there is no action the customer would need to take.

 

Using customer-managed keys with Event Hubs requires Soft Delete and Do Not Purge  properties enabled to help protect customers from ransomware scenarios.

Enabling this feature targets enterprise customers looking to protect sensitive data as part of their regulatory or compliance needs like the HIPAA, BAA compliance.

 

Note: Customer managed key for encryption with Event Hubs can be enabled only on Event Hubs namespaces, that are under a Dedicated Event Hubs cluster. Event Hubs cluster is Kafka enabled by default. Create a Dedicated cluster in the portal by following this link - 

https://aka.ms/eventhubsclusterquickstart