Harry, and welcome back.
Now in today's video, we will be discussing about a very important topic in the area of cryptographic
key deletion.
Now, generally for production environment, you have to be very careful while deleting the cryptographic
keys because one wrong move and your entire production data might be unrecoverable forever.
And this is one of the reasons why even idleness has added some safeguard measures to ensure that the
keys cannot be deleted out of the box very easily.
And in today's video, that is what we are going to discuss here.
So the topic for today's video is scheduled deletion so mean we discuss about the scheduling deletion.
This comes into the area of gamers suggesting device deleting the game is key is destructive and potentially
dangerous, as well as irreversible process.
For example, let's say you have a key mzgee and you have certain production data that is encrypted.
Now this person data can be within your servers.
It can be within your database, etc. And you only have this one games guide that has the ability to
go ahead and be grouped this ciphertext blob.
Now, due to some reason, let's say, due to an accident, administrator deleted the key permanent
key.
Now what will happen to this ciphertext blob?
It will be unrecoverable, even though you have a very important detail what year it will be under-recovery
and seem a place for games.
So the sticking point states after the game is key is deleted.
You can no longer decrypt data that was encrypted under the key mzgee, which means that that data becomes
under-recovery.
But and this is a reason why you have to be very careful while deleting game is key in production environments.
Now, few important pointers to remember for on is that you should delete.
The game is key only when you are sure that you don't need to use it anymore.
Sometimes what really happens in production environment is you do not really know who exactly or what
the application is.
Using the Gear MzGee because that game is key, is created years before and you will know someone is
using it.
So going ahead and directly deleting it will be a riskier approach.
Now, I still remember in one of the organization that I was working with, we were going through a
PCR 86 complaints and auditor was little suspicious about one of the key keys, and he said, Give me
the name of the application who is using that specific games key.
So even we did not know that because that game is he was there since even before we joined the organization.
So we raised an email to all the developer teams to let us know if they are using a specific game is
key and we did not really get any.
They played it.
So how do we tell the auditor that we do not really know?
So my manager came up with an innovative idea what he said.
Let's go ahead and disable the game's key instead of building it.
So generally, what happens is that if you disable a key mzgee, it will continue to exist.
But various operations like decrypt or encrypt will not really work, so it will be in a disabled state.
So as soon as we disable that gear key immediately within five to 10 minutes, a developer game stating
that his application is not really working and it just took us five to ten minutes to identify the application
did.
So this is the reason why the disable functionality in game is keys very important so he could disable
the key maski, which is stated in the third point.
It cannot be used to encrypt decrypt data until you enable it, so we will be discussing about Howard
K. Muskie.
Can we disable in just a moment?
But before we do that, let's look into how Okyere Muskie can be deleted.
Now we all know that deleting a key Muskie is a destructive process, and this is one of the reasons
why eatables has added one of the safe side mechanism you can see of having a waiting period between
seven to 30 days.
So let's say that you have created a new customer managed Geir Muskie, and you want to delete this
key.
You will not be able to directly delete this key immediately.
You will have to wait for seven to 30 days post which their deletion would happen now during this waiting
period.
The game is key, cannot be used for cryptographic operations.
So this is the theoretical part.
Let's go ahead and look into it practically.
All right.
So we have one game key that is available.
Let's look into how we can delete it so you can go ahead and click on schedule key delete and note that
this is schedule key deletion.
And when you do that, you have a waiting period.
The default is 30 days.
However, it can be as soon as seven days, so you can even set saving this post, which the key would
be deleted.
And you will also have to confirm it and you'll have to click on schedule.
Key deletion So this is one part you.
Can also go ahead and disable this specific gear mzgee, so if we'll click here, you see you can go
ahead and disable the game, Muskie.
Now let's also look into how the cryptographic operations are blocked.
I just wanted to show you that as well.
So within my seal, I'll go ahead and run the E.W. schemes and grab command to encrypt the contents
that are part of the Clean Haven text or the HD file.
And since currently the game's key is active, the operation should be successful.
Great.
So we got the cipher text block.
Let's also go ahead and decrypt it.
So I see the game as the great cipher takes blob and misapplied the ciphertext blob.
Oops, we forgot to specify the original idea.
You can just specify a region where the key message is created.
All right, so our ciphertext got converted into plain text.
Now first, let's look into the disable Comiskey Park, so I'll go ahead and disable this gear.
All right.
So now you see the status is disabled when you go ahead and run, the game is the correct operation.
This should not be what you see immediately.
You are getting an edit stating that the key is disabled in a similar way.
Even the encrypt operation should not work.
So even they encrypt operation should not work.
So this is one.
But once you want to enable the key, you can go ahead and click on Enable and the keys now enable.
If you want to test the Encrypt Decrypt functionality, it should work.
Things are working now and the last, but as we were discussing, is the schedule key deletion.
Let's also say the waiting period to seven days, I'll confirm and I'll click on schedule key deletion.
Islets are now in this state, as you see it, state spending deletion.
So now if you try to go ahead and be called the ciphertext blob, it should not really work.
I let it state spending deletion.
All right.
So this is the high level overview about the deletion related aspects.
What gives?