Skip to main content

Security: Key Rotation of our Azure Storage account keys

Azure Storage account key rotation is one of the most important things people forget about. Account keys provide full access to your storage; nevertheless, we fail to keep them safe and fresh. 

In this article, we talk about the key rotation mechanisms provided by Microsoft Azure. 

Why?

Azure Storage account provides two account keys that can manage the storage. They provide the user with the full power to read, modify, delete and create content. Not only that we need to keep them safe, but we also need to ensure that we rotate them at specific time intervals. 

Key expiration policy

A key expiration policy can be easily created from the Azure Portal. When the policy is triggered, a reminder is displayed in the portal to remind us to rotate the keys. Additionally, once you have the key expiration policy defined, you can monitor the compliance of your storage account, including the key rotation.


As you can see above, this can be achieved from the Azure Portal or through the Azure CLI or PowerShell. The reminders can be daily, weekly, monthly or yearly OR custom.

Monitoring expired account keys

This can be achieved using Azure Policies. A built-in policy for Azure Storage covers the account key expiration. The policy can be applied to one storage account or to all storage accounts under a resource group or subscription. 

Once you have defined the policy, you navigate to the Azure Policy dashboard to check the level of compliance. 


Alerts and Notifications

We talked about defining a policy and monitoring the key expiration from the portal or from the Azure Policy dashboard. 

What about automation? Can we configure the policy in such a way as to send a notification to an interval or external system?

YES, we can do this. You would need to rely on Event Grid and ingest the events from Azure Policy. Once you have done this, you can decide what kind of action (event handled you would like) - Azure Functions, Logic App or Service Bus, Queues, WebHooks, Automation and so on.

You could even define an Azure Automation or an Azure Function that automatically rotate the key when the Azure Policy is triggered. 


For more about how to react when an Azure Policy state changes, I recommend looking at this page.

Conclusion

Microsoft is offering us the capability to define alerts and policies, monitor them, and react to them. Azure Key Rotation capability is fully covered by Azure; we just need to ensure that we are configuring and integrating it in our systems. 

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

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.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...