End-of-Life (EoL)
Azure Key Vault
You can integrate Prisma Cloud with Azure Key Vault.
First configure Prisma Cloud to access your Key Vault, then create rules to inject the relevant secrets into their associated containers.
Prerequisites:
You have created a secret in Key Vault.- Create an Azure servicePrincipal in your Azure AD Tenant
- Use AZ CLI to create a servicePrincipal and obtain the json credential file.
- Authenticate to your Azure tenant.$ az loginCreate a servicePrincipal$ az ad sp create-for-rbacSave the resulting json output.+{ "appId": "xxxxxxxx-xxxxx-xxxx-xxxxxxxx", "displayName": "azure-cli-2018-11-01-xx-xx-xx", "name": "http://azure-cli-2018-11-01-xx-xx-xx", "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "tenant": "xxxxxxxxxxxxxxxxxxxxxxxxxxx" }In the Azure Key Vault, add the servicePrincipal to theAccess Policieswith the following permissions:secrets/get permission secrets/list permissionIn the Prisma Cloud Console, go toManage > Authentication > Secrets.ClickAdd store.
- Enter a name for the vault. This name is used when you create rules to inject secrets into specific containers.
- ForType, selectAzure Key Vault.
- ForAddress, enterhttps://<vault-name>.vault.azure.net. This address can be found in the Azure Key Vault’s properties in the DNS Name element.
- InCredential, clickAdd new.
- Enter a name for the credentials.
- InType, selectAzure.
- InService Key, enter the JSON credentials returned from the az ad sp create-for-rbac command.
- ClickSave.
- ClickAdd.After adding the new store, Prisma Cloud tries conecting to your vault. If it is successful, the dialog closes, and an entry is added to the table. Otherwise, any connection errors are displayed directly in the configuration dialog.
Most Popular
Recommended For You
Recommended Videos
Recommended videos not found.