Home › Key concepts › Identity, secrets and least privilege
Key concept · Walk (intermediate) · the same on every platform
Identity, secrets and least privilege
Every person and program gets only the access it needs, and keys never live in code.
What it is
Identity says who or what is calling. Least privilege means granting the smallest permission that works. Secrets such as passwords and API keys live in a secret store and are fetched at run time, never committed to a repo.
Why it matters
Most breaches use a leaked key or an over-powerful account.
An example
The pipeline's identity may read bronze and write silver, nothing else; its database password comes from the secret store.
The common mistake
An API key pasted into a notebook that ends up on GitHub.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Identity and secretswho is calling, what they may do, where keys live | IAM + Secrets Manager | Entra ID + Key Vault | IAM + Secret Manager | Unity Catalog grants + secrets | Keycloak + sops |
Related ideas
Where it shows up
Part of the Walk level on these paths: Software Engineering (running services) · Forward Deployed Engineering (deliver).