Please check here for scripts using the latest PowerShell cmdlets.
Azure Key Vault service is a cloud hosted, HSM(Hardware Security Modules)-backed service for managing cryptographic keys and other secrets. With Azure Key Vault, the process of managing and controlling the keys required for an application or multiple applications for an enterprise can be handled at a centralized place. Also these sensitive information no longer needs to be exposed in the application’s configuration file or in database. Keys can be created in the vault and accessed via url’s by the required application. Operations against the Key Vault are authenticated and authorized using Azure Active Directory. So in short all that a developer would need to know are the URI’s for the keys, the sdk/api to access the vault features and also on the mechanism to authenticate against the AD application (an appId/client secret or appId/certificate).
The initial release of Azure Key Vault only supports RSA keys (asymmetric cryptography) - it supports both software and HSM processed keys, and are represented as JSON Web Key objects. In future there might be more support for the different key types that are there in cryptography. For those who are new to cryptography or needs a quick recap on cryptography algorithms:
Symmetric cryptography, uses the same key to encrypt and decrypt the data. The keys are shared between the identities that require to transfer the encrypted data.
Asymmetric cryptography, also known as public key cryptography uses two separate keys - a public key and private key. The public key can be used to encrypt the data or to verify a digital signature whereas the private key is used to decrypt the text or to digital sign.
To create a new key in the Azure Key Vault, first we need to create the vault, using powershell scripts. You would need to install azure module version 0.8.13 version or higher for the key vault scripts to execute. Detailed steps on creating the vault and keys is documented here. Once we have the key created we can get the attributes of the key, using Get-AzureKeyVaultKey. This is as per the JSON Web Key(JWK) format. The ‘n/e’ values in the below key are for the RSA key type(kty), showing the public key information.
1 2 3 4 5 6 7 8 9 10 11 12
Now that we have a key in the vault, we can use this to perform different operations allowed on the key, as provided in the key_ops field in the key details above. Typical operations that can be performed using the key are Encrypt, Decrypt, Sign, Verify, WrapKey and UnWrapKey. For an application to use the key vault keys, it needs to authenticate using a token from the Azure Active Directory. For this we first need to register an application with azure active directory and then use the Application id and Authentication key(client secret) to authenticate against the AD application. Instead of using the key/secret, this could also be through a certificate authentication, which might be a more preferred approach(For the simplicity of this demo will use the application id and the secret directly). To connect to the AD application we can use the Active Directory Authentication Library nuget package, the KeyVault libraries are availalble as part of the samples.
1 2 3 4 5 6 7 8 9 10 11
The application first uses the AD application credentials to authenticate and obtain the token for further interacting with the key vault. Using the key identifier that is available we get the details of the key.For performing the get operation the ‘PermissionToKeys’, should be set appropriately when registering the AD application, using Set-AzureKeyVaultAccessPolicy, against the key vault. Since this is RSA asymmetric algorithm, we have the public key available to us, and we can use this to encrypt the data or to verify the signature, locally in the application itself, though the vault client provides this for convenience.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
As above, we use the public key available to create the RSACryptoServiceProvider to encrypt the data and also to verify the signature locally. So in an application we can encrypt the data locally and use the vault to decrypt it when required. Decryption can happen only from the vault, as the private key is only available in the vault, and does not cross the vault boundary.
With Azure Key Vault, managing keys and restricting application permission for keys can be easily managed and no information needs to be passed on to the developer or to any specific individual. Also the keys are secure behind the vault service and can also be protected using a HSM. You would need to update the application id and secret in the sample for it to work. Hope this helps in getting you started with Azure Key Vault.