Integrate Azure Key Vault with MongoDB Client-Side Field Level Encryption
Rate this tutorial
When implementing MongoDB’s
(CSFLE), you’ll find yourself making an important decision: Where do I store my customer master key? In
, I guided readers through the basics of CSFLE by using a locally-generated and stored master key. While this works for educational and local development purposes, it isn’t suitable for production! In this tutorial, we’ll see how to use Azure Key Vault to generate and securely store our master key.
Prepare Azure Infrastructure
Configure your Client Application to use Azure Key Vault and CSFLE
In order to establish a trust relationship between our application and the Microsoft identity platform, we first need to register it.
- If you have access to multiple tenants, in the top menu, use the “Directory + subscription filter” to select the tenant in which you want to register an application.
- In the main search bar, search for and select “Azure Active Directory.”
- On the left-hand navigation menu, find the Manage section and select “App registrations,” then “+ New registration.”
- Enter a display name for your application. You can change the display name at any time and multiple app registrations can share the same name. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies your app within the identity platform.
- Specify who can use the application, sometimes called its sign-in audience. For this tutorial, I’ve selected “Accounts in this organizational directory only (Default Directory only - Single tenant).” This only allows users that are in my current tenant access to my application.
- Click “Register.” Once the initial app registration is complete, copy the Directory (tenant) ID and Application (client) ID as we’ll need them later on.
- Find the linked application under “Managed application in local directory” and click on it.
- Once brought to the “Properties” page, also copy the “Object ID” as we’ll need this too.
- On the overview of your newly registered application, click on “Add a certificate or secret”:
- Under “Client secrets,” click “+ New client secret.”
- Enter a short description for this client secret and leave the default “Expires” setting of 6 months.
- Click “Ad." Once the client secret is created, be sure to copy the secret’s “Value” as we’ll need it later. It’s also worth mentioning that once you leave this page, the secret value is never displayed again, so be sure to record it at least once!
- Sign in to the Azure CLI using the
az logincommand. Finish the authentication steps by following the steps displayed in your terminal.
- Create a resource group:
- Create a key vault:
With a key vault, we can now create our customer master key! This will be stored, managed, and secured by Azure Key Vault.
Create a key and add to our key vault:
To enable our client application access to our key vault, some permissions need to be granted:
- Upon success, you’ll receive a JSON object. Find and copy the value for the “vaultUri” key. For example, mine is
- If you haven’t cloned the repo yet, do so now!
- Navigate to the root directory
mongodb-csfle-csharp-demo-azureand open the
EnvoyMedSyssample application in Visual Studio.
- In the Solution Explorer, find and open the
- Here, you’ll see some scaffolding for some variables. Let’s quickly go over what those are:
MDB_ATLAS_URI: The connection string to your MongoDB Atlas cluster. This enables us to store our data encryption key, encrypted by Azure Key Vault.
AZURE_TENANT_ID: Identifies the organization of the Azure account.
AZURE_CLIENT_ID: Identifies the
clientIdto authenticate your registered application.
AZURE_CLIENT_SECRET: Used to authenticate your registered application.
AZURE_KEY_NAME: Name of the Customer Master Key stored in Azure Key Vault.
AZURE_KEYVAULT_ENDPOINT: URL of the Key Vault. E.g.,
- Replace all of the placeholders in the
launchSettings.jsonfile with your own information. Each variable corresponds to a value you were asked to copy and keep track of:
AZURE_TENANT_ID: Directory (tenant) ID.
AZURE_CLIENT_ID: Application (client) ID.
AZURE_CLIENT_SECRET: Secret Value from our client secret.
AZURE_KEY_NAME: Key Name.
AZURE_KEYVAULT_ENDPOINT: Our Key Vault’s vaultUri.
- Save all your files!
Before we run the application, let’s go over what’s happening: When we run our main program, we set the connection to our Atlas cluster and our key vault’s collection namespace. We then instantiate two helper classes: a
CreateKeyWithAzureKmsProvider()method is called to generate our encrypted data encryption key. This is then passed to the
EncryptedWriteAndReadAsync()method to insert a sample document with encrypted fields and properly decrypt it when we need to fetch it. This is all in our
Taking a look at the
KmsKeyHelperclass, there are a few important methods: the
GetClientEncryption()methods. I’ve opted to include comments in the code to make it easier to follow along:
With our Azure Key Vault connected and data encryption key encrypted, we’re ready to insert some data into our Atlas cluster! This is where the
AutoEncryptHelperclass comes in. The important method to note here is the
Now that we know what’s going on, run your application!
If all goes well, your console will print out two
DataKeyIds(UUID and base64) and a document that resembles the following:
Sample Result Document (using my information)
Here’s what my console output looks like, for reference:
Seeing this is great news! A lot of things have just happened, and all of them are good:
- Our application properly authenticated to our Azure Key Vault.
- A properly generated data encryption key was created by our client application.
- The data encryption key was properly encrypted by our customer master key that’s securely stored in Azure Key Vault.
- The encrypted data encryption key was returned to our application and stored in our MongoDB Atlas cluster.
Here’s the same process in a workflow:
After a few more moments, and upon success, you’ll see a “Successfully upserted the sample document!” message, followed by the properly decrypted results of a test query. Again, here’s my console output for reference:
This means our sample document was properly encrypted, inserted into our
patientDatacollection, queried with our auto-encrypting client by SSN, and had all relevant fields correctly decrypted before returning them to our console. How neat!
And just because I’m a little paranoid, we can double-check that our data has actually been encrypted. If you log into your Atlas cluster and navigate to the
patientDatacollection, you’ll see that our documents’ sensitive fields are all illegible:
That wasn’t so bad, right? Let's see what we've accomplished! This tutorial walked you through:
- Registering an App in Azure Active Directory.
- Creating a Client Secret.
- Creating an Azure Key Vault.
- Creating and Adding a Key to your Key Vault.
- Granting Application Permissions to Key Vault.
- Integrating Azure Key Vault into Your Client Application.
- The Results: What You Get After Integrating Azure Key Vault with MongoDB CSFLE.
By using a remote key management system like Azure Key Vault, you gain access to many benefits over using a local filesystem. The most important of these is the secure storage of the key, reduced risk of access permission issues, and easier portability!
For more information, check out this helpful list of resources I used while preparing this tutorial:
A whole community of MongoDB engineers (including the DevRel team) and fellow developers are sure to help!