Skip to main content

Azure Storage - Client Side Encryption

A few days ago, client-side encryption for Azure Storage was announced. In this post we will take a look over this feature.

First of all, you should know that the encryption/decryption takes place on client side. This means, that the content will be already encryption when it will arrive on Azure. This encryption technique is called Envelop Technique. It is very useful when you want to add another security layer over your data.
Out of the box, there are client library for .NET (including Windows Phone). For other languages, like Java is not yet supported, but because the encryption algorithm is a well know one, you may be able to implement it on other platforms also.

The encryption algorithm that is used by client library is AES (Advanced Encryption Standard). It is important to know that the encryption keys are generated by the client library. And is NEVER stored in Azure Storage. The encryption key should be stored in a different location. This library is full integration with Key Vault Service, that allow us to persist the keys in a safe location.

The encryption mechanism is not complicated, but is very useful. You don't need to encrypt by yourself, using different libraries and orchestrate all the activities. From a developer perspective, the life is more simple and the chances to introduce a bug are reduced.

There are some small things that we should consider when using this library.
First thing is related to blobs. All reads and writes operations needs to be made on the entire blob content. This means that we should not upload encrypted content using PutBlock. All the time, we should use DownloadToXXX, BlobReadStreamXXX, UploadFromXXX and OpenWriteXXX.
This is necessary because each time when you upload content, a new IV (Initialization Vector) is generated. This information is stored in blob metadata and will be used during decryption.
A similar situation is on Azure Tables. We have full support for action like Insert and Replace, but Merging is not supported.
The interesting thing is when we are using Azure Queue and we want to encrypt content. In this situation, the encryption information (IV and a random CEK) are added to each message. This means that we can work separately with each message. Take into account that for each message, the message body will contain also the IV and CEK. Because of this the size of the message and queue will be bigger.

In the below diagram, we can see where the encryption metadata are stored (IV, CEK).


If you want to enforce to encryption all the content that is stored in Azure Storage, you can set the 'RequireEncryption' to TRUE. In this way, you will enforce the client to encrypt all the content that is send. If you want to take a look over the implementation you can see the source code on GitHub - https://github.com/Azure/azure-storage-net/blob/master/Lib/ClassLibraryCommon/Blob/BlobEncryptionPolicy.cs.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

Title:
What abo…