Azure Storage Account Encryption: How-to Guide
Verify the encryption status of Azure Storage Accounts and remediate non-compliance. Follow our guide to secure your data properly.
Verify the encryption status of Azure Storage Accounts and remediate non-compliance. Follow our guide to secure your data properly.
If your team is using Azure to store data in the cloud, it’s important that your storage accounts are encrypted to lower the risk from security breaches. If a bad actor isn’t able to read exfiltrated data, your organization has a much stronger security posture.
So, are your Azure storage accounts encrypted?
In this guide, we’ll show you how to confirm whether your Azure storage accounts are encrypted and update them if necessary.
An Azure storage account is a service by Microsoft Azure that provides secure, durable, and scalable cloud storage. It includes services such as Blob Storage, File Storage, Queue Storage, and Table Storage; each one supporting a different storage use case.
There are a few different options for encrypting Azure storage accounts. While there are client-side encryption options, service-side encryption is the recommended approach.
By default, storage accounts automatically have service-side encryption with Microsoft-managed keys stored securely, allowing access to data only to authorized users.
If you want greater control over the security of your Blob storage accounts and Azure files, you can set up customer-managed keys, which must be stored in Azure Key Vault or Azure Key Vault Managed Hardware Security Model (HSM). This approach is better, for example, if you have unique key rotation requirements.
You can also use customer-provided keys for Blob storage accounts, stored in any customer-managed vault. You can read more about the encryption options here.
While there are few different approaches, it’s important to be able to quickly validate that all of your Azure storage accounts are encrypted.
To check that your Azure storage accounts are encrypted with either method, there are two common approaches you can take — the Azure console or the Azure command-line Interface.
If you want to skip manual steps, you can scroll down to see how you can save significant time by automating this task and many others with Blink.
Now, let's look at each of these in more detail so you can choose the best approach for your organization.
To check if your Azure storage accounts are encrypted using the console, follow these steps:
If your storage account is encrypted with Microsoft managed keys, the status will show as "Your storage account is currently encrypted with Microsoft managed key by default. You can choose to use your own key."
But if you're already using customer-managed encryption keys, your screen will display a prompt to choose between the Enter key URI and Select from Key Vault options.
The Azure CLI is a set of commands used to manage and configure your Azure Storage Accounts. To check if your storage accounts are encrypted using this method, follow these steps:
This will list all of your storage accounts in the CLI window.
The CLI output will display the type of encryption used for that storage account.
If the storage account is encrypted with customer-managed keys, the command will return Microsoft.KeyVault as the keySource value. Microsoft-managed keys will return Microsoft.Storage instead.
If you find that your storage accounts are not encrypted after running the above commands, don't worry. You can encrypt your Azure storage accounts using both methods mentioned above.
First, it's important to determine how you want to encrypt your storage accounts. As we outlined earlier, you can choose between using Microsoft-managed keys or customer-managed keys.
You can encrypt your storage accounts using the Azure console in simple steps. Here is what you need to do:
Setting up the Microsoft-managed keys is a simpler process, as it does not require any external keys or services.
Customer-managed encryption requires using a Key Vault. You must set up a key vault first and then enter the Key Vault URI in the Azure console.
You can also use the Azure CLI to encrypt your storage accounts:
This will enable encryption with Microsoft-managed keys on the storage account.
You can work through these steps to validate that your Azure storage accounts are properly encrypted, but if you run this on a regular basis, it becomes time-consuming.
If your organization has a strategy around encryption, you need tools that can support you in managing it at scale.
With Blink, you can run a scheduled automation to check your Azure storage accounts and ensure that they are compliant with your encryption standards.
When this automation runs, it executes the following steps:
It’s a simple automation that’s easy to customize. For example, you can add a conditional step to send a Slack notification to your Azure admin if there are any non-encrypted accounts identified. In that notification, you can embed an approval step to update the account with the proper encryption settings.
There are over 5K automations like this one ready to use in the Blink library, or you can build new automation from scratch to fit unique use cases.
Get started with Blink today to see how easy automation can be.
Blink is secure, decentralized, and cloud-native. Get modern cloud and security operations today.