and this next lesson, we're gonna talk about how we can configure our shared encryption keys for storage accounts.
Our objectives include we're gonna talk about storage account encryption in general.
We'll talk about encryption, key management
and finally, as always, will jump out to the azure portal and take a look at a demo of how we can work with these inside of our storage account.
So first, let's talk about storage account encryption. In general,
our storage counts are automatically encrypted,
and it's transparent to us. When it does the encryption and decryption,
they're encrypted with 256 bit A AES encryption,
and the encryption technology is Phipps 1 40 dash to compliant so you can see your data is gonna be super secure. And this meets probably quite a few of your regulatory requirements.
Now, storage counts are encrypted by default, so there's nothing you have to do to enable this service for you. And this is gonna be regardless of your performance tear. If it's standard or premium,
or whether you deployed using the newer azure resource manager or arm service, or the classic deployment and all of our azure storage redundancy option support encryption, and every copy of your storage account is encrypted. So basically saying it's enabled by default and
all your stuff is gonna be encrypted no matter which service or tear you
This includes the Blob's disk files, cues and tables and even the object. Meta data is also encrypted, and what's great is all this encryption comes at no additional cost to you.
So let's talk about encryption key management.
Our storage accounts are automatically encrypted using keys managed by Microsoft
and this automatic encryption and the key management is available for all of our azure storage services.
These keys are stored in a Microsoft key store, and Microsoft is also responsible for rotating these keys. Periodically
have worthies. Keys are only accessible to Microsoft, so this may not meet your regulatory requirements if you need to know the keys or be able to manage them yourself.
So this is where our next encryption key management option comes into play.
You do have the option of bringing your own key to your storage account for encryption.
This means this is customer managed, but it's only available for encrypting your blob storage or azure files
que and table will always used Microsoft managed encryption keys.
Another option you also have is a customer provided key for your blob storage operations so you can write an application and have your own encryption key when you access your blob storage for encryption or decryption inside your application operations.
If you're going to use customer managed keys, you're gonna have to store the key out in an azure key vote, and we'll take a look in our demo on how to create one and use it for our encryption keys.
This is where you, as the customer, come into responsibility for rotating those keys and managing them. As Microsoft is not going to do this for you anymore.
That doesn't for some of our concepts. Let's jump out to the azure portal, where we're first going to create an azure key vault to store our own encryption keys,
and then we're gonna switch our storage account encryption to that key that we just created.
Let's go out to the azure portal now.
Here we are, back in the azure portal, and before we go look at our storage account, we need to create an azure key vault to store our customer managed keys slips select. Create a resource.
We'll search fork evil selected here from the menu and go ahead and click on Create.
Now, when creating the key vault, I'm going to put it in the same resource group as the rest of our demos here.
And our ki volt name needs to be globally unique all across azure, just like our storage account. So I'm going to name it J B T storage account Dash cavey for Ki Volt. I'm also going to select the east US region because our Ki Volt needs to be in the same region as our storage account. If we're gonna use customer managed keys like this,
key votes have to price in tears. I'm gonna leave it at standard. The only thing we get for with premium is we can use hardware, security module or HSM back keys.
And I'm also going to enable perch protection and leave soft elite at enabled as well.
If I didn't enable these, it would automatically be turned on for our key vault. When we associate id our storage account with our customer manage keys,
let's go and review and create and click the create button.
This is gonna take a few minutes to deploy, so I'm gonna posit video and we'll come back when it's done
with our ki Volt deployed. Let's go ahead and select Go to Resource
And inside of our Ki Volt here, the first thing I would look at under settings is Let's go and check out our access policies,
and I just want to point out inside the access policies. My account is the only one that has permissions to it. But after we configure the storage account to use our customer managed keys inside the ski vault, it will also have permissions.
Let's go into keys
and let's go ahead and generate our key that we're going to use for a storage account.
We'll go ahead and give it a name. We'll name it the name of the storage account so we know which resource it's associated with.
We have two different key types are say in the sea and a couple of key sizes. If we wanted to customize this,
we can also set activation and expiration dates for our keys and let's go and keep it at, enabled and create our custom key here with our key. Let's go back to the home screen and go into R J B T 2020 storage account
and under settings. Let's check out encryption, and right now the encryption type is set to Microsoft Manage skis.
But if we select the other radio button for a customer manage keys, we can either enter the key. Your I, which does, is a unique identifier for the key vault in the key we want to use. Or we can select the radio button for Select From Ki Volt and select the link. Here
we'll go select the key vole. Under this subscription,
we can select the drop down to select our key
and finally the version.
Let's click the select button.
We see our all of our options there and let's save it
and successful. We're now using our key down here from our key vault to encrypt our storage account with our own key. So let's go back to home.
We'll select our key vote here from our recent resource is
and I want to go into access policies,
and sometimes it doesn't show up right away. So let's click Refresh,
and we can now see r J. P. T. 2020 is listed as having access to this key vault. And for key permissions, it can get keys and wrapped and unwrapped the keys in order to access it.
Let's go back to keys here.
Select our key that we created,
and let's go and select a new version. Let's rotate are key here and see what that looks like.
Leave all our options at the default. Go and create another version. You can see our current version starts with C C 66 and are older. One is 5 to 6. Not sure why we got two current versions there, but if I refresh, it'll just go back to one. Let's go back to the home screen. We'll go into our storage account
back under settings and encryption on Let's Rotate to our new Key
will select Change Key
again. We'll select from vault
and choose our little link here. Go back, choose our key vault are key and now under here we have two versions are 5 to 6 is the older one, and cc 66 is the new one.
We'll select it.
and we've successfully rotated are key for encryption on our storage account. That does it for our demo. Let's jump back to the slides and wrap this up.
That does it for this lesson. Where we talked about storage account encryption in general, we talked about Microsoft managed keys and how those are automatically applied to our storage account services.
Well said the option of providing our own key and storing it inside or a jerk evil
and then also creating azure key vault to store our own keys. And finally we looked at how we can configure those encryption keys on our storage account.
Kind of next. We're going to take a look at how to manage access keys and shared access signatures.
See you in the next lesson.