Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/AppService/115 of 115

9.11Ensure Azure Keyvaults are Used to Store Secrets

Control family: AppService

Control description

Encryption keys ,Certificate thumbprints and Managed Identity Credentials can be coded into the APP service, this renders them visible as part of the configuration, to maintain security of these keys it is better to store in an Azure Keyvault and reference them from the Keyvault.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Keys, connection strings and certificate thumbprints stored as plain app settings are visible to anyone who can read the app's configuration, and end up in exports and scripts. They are kept in Key Vault instead, and the app setting holds only a reference that App Service resolves using the app's managed identity.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree that app secrets live in Key Vault, one vault per application or environment, with the app's managed identity as the only reader.
  • List the secrets each app holds in its settings today.

Evidence

  • The secrets standard and the inventory of secrets moved

On Azure the tasks give the app access to Key Vault, then replace each secret setting with a Key Vault reference.

Task 1Give the app access to the vault

  1. Sign in to the Azure portal at portal.azure.com and turn on the app's system-assigned managed identity (9.5).
  2. Open Key vaults, then the vault that will hold the app's secrets.
  3. In Access control (IAM), assign the Key Vault Secrets User role to the app's managed identity (for a vault on access policies, grant Get on secrets instead).
  4. Add each secret to the vault under Objects > Secrets.

Task 2Replace secret values with Key Vault references

  1. In the app, open Settings > Environment variables (or Configuration > Application settings).
  2. Edit each setting that holds a secret and replace its value with a reference of the form @Microsoft.KeyVault(VaultName=yourvault;SecretName=yoursecret).
  3. Select Apply (or Save) and confirm the restart.
  4. Open the setting again: the edit dialog shows whether the reference resolved, or the error if not.
  5. Check it: no app setting holds a secret value, and the app still works.

Evidence

  • The app settings of each app, with secrets held as Key Vault references
  • The vault's role assignments for the app identities

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.