I have some doubst about how Microsoft Azure Encryption works. I come from AWS, and it seems that we have some security controls in AWS regarding encryption keys, we have not in Azure. For example:
- In AWS, if a disk is encrypted using a specific Customer Managed Key (CMK), if that user has not access to the CMK, then the user cannot start up an EC2 instance with that encrypted disk. I have made some tests, and it it looks it is not the case in Azure.
- Same happens in AWS when you want to create a snapshot of an ecnrypted disk, you need access to the CMK. It is not the case in Azure.
- In AWS, when you use a CMK to encrypt files in S3, if a user with full S3 acess in IAM but without access to the CMK tries to read files from S3, the user is not able to do it. This is not the case in Azure.
So, CMK are just there in Azure for the encryption at rest, and it has not anything to do about if users are able or not to access the data, right? In my tests, having permissions to the encryption keys is just necessary to be able to select them when you want to enable encryption on resources.
On the other hand, why do we have the "Cryptographic Operations" option for Encrypt/Decrypt in the Key Vault Access Policies? I mean, I have an user without these permissions, and the user is still able to encrypt Disks without problem, because he has the all the Key Management Operations enabled. I am struggling to understand the use case for "Cryptographic Operations".
Thanks.