Menu

1 / 4

SC-500 deep dive #1: your Contributors can read your Key Vault secrets

DEV Community: azure·CD Security Lab·12 days ago
#10eL9IIG
#devtoazure#devto#dev#vault#access
Reading 0:00
15s threshold

Every Thursday I post SC-500 practice questions. Every Saturday, from this week, I take one exam topic and go deep: the real problem, how it works, the fix, and the exam traps. Week 1: who can really read the secrets in Azure Key Vault.

Lab story, lab names only ( contoso.com ). Screens are drawings, numbers are invented.

The problem: a "deploy-only" account that read 41 secrets

In my lab, Contoso gave a contractor account, lab.contractor02 , the Contributor role on the resource group rg-lab-payments . The reason was simple: "they need to fix a deployment, nothing else". Contributor cannot give roles to anyone, so it felt safe.

Two weeks later a review of the vault kv-lab-pay-01 found something nobody had added:

a new access policy for lab.contractor02 , with Get and List on secrets

created by lab.contractor02 itself

41 secrets readable, including the payment API key and the SQL connection string

No alarm fired. Nothing was "hacked".…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.