access control
The rules and mechanisms that decide who may read, use or change a resource.
In more detail
It combines identifying who is asking with rules about what each identity may do. Matching access to responsibility means each person can reach only what their job requires.
Examples
A vault ID labels which password protects a file, but access control on the secret store decides who can obtain that password.In Terraform: For Terraform the most important access control is on state and on the credentials that can apply, because state contains secrets and applying can destroy production. A private backend still needs checking: anyone with read access to the state bucket can read every secret in it.Related terms
- vault ID — A label attached to Vault-encrypted data that names which password protects it, so one project can use different passwords for different environments.
- secret store — A dedicated service that stores secrets such as passwords and keys, controls who may read them and records each access.
- least privilege — Giving every program and person only the access they need, and nothing more.
- authorization — Deciding whether an already identified caller may perform a particular action on a particular resource.
- broken access control — A flaw where the server lets a caller act on data or operations it should not, for example by trusting a user name the caller supplied or skipping an ownership check.
- role-based access control — An authorization model where permissions are grouped into named roles, such as reader or editor, and people or services are given roles.
- attribute-based access control — An authorization model that decides each request from attributes of the subject, the resource and the environment, such as owner, department or time of day.
- audit trail — A record of who did what and when, kept so actions can be reviewed and investigated later.
- feature flag — A switch in the code, controlled from outside, that turns a feature on or off for chosen users without a new deployment.
- Terraform backend — The setting that decides where Terraform stores state and how it locks it, from a local file to shared cloud storage.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
Taught in
- Vault IDs And Multiple Passwords — Ansible Configuration Management at Scale
- Large Payloads And Streaming — Modern API Architecture: REST, GraphQL & gRPC
- Idempotency Keys — Modern API Architecture: REST, GraphQL & gRPC
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC
- Handling PII And Data Privacy — Modern API Architecture: REST, GraphQL & gRPC
- Decoupling Release From Deployment: Feature Flags — DevOps & Site Reliability Engineering
- The Problem With Local State — Infrastructure as Code with Terraform
- Configuring A Remote Backend — Infrastructure as Code with Terraform
- State Locking With Use Lockfile — Infrastructure as Code with Terraform
- Workspaces For Multiple Environments — Infrastructure as Code with Terraform
- Security: Secrets In State And Ephemeral Values — Infrastructure as Code with Terraform
- State: Terraform's Memory Of What It Built — HashiCorp Terraform Associate (004) Exam Prep
- Sensitive Data, Ephemeral Values And Secrets From Vault — HashiCorp Terraform Associate (004) Exam Prep
- The Local Backend, And Workspaces On One Machine — HashiCorp Terraform Associate (004) Exam Prep