# 35 terms, each with a sourced example

Glossary, read 10 Nov 2026

**In short.** Plain definitions of the terms in this index, from CIEM and effective access to service control policies, permission boundaries and just-in-time access. Each entry has a sourced example from a cloud provider or vendor page read on 10 Nov 2026.

- [Access debt](/glossary/access-debt/): Access debt is the accumulated gap between the access an organization has granted over the years and the access it needs now.
- [Access path](/glossary/access-path/): An access path is one route by which an identity can reach a resource: a chain of a role, a trust relationship, a network route and a permission.
- [Access review](/glossary/access-review/): An access review is a periodic check, by a manager or owner, that each person or group still needs the access it holds.
- [Attack path](/glossary/attack-path/): An attack path is a sequence of steps an attacker could use to get from an entry point to a valuable asset, for example from an exposed workload through its attached identity to a database.
- [Blast radius](/glossary/blast-radius/): Blast radius is the set of resources an identity, workload or credential could damage or read if it were compromised.
- [Break-glass access](/glossary/break-glass-access/): Break-glass access is a pre-arranged, tightly controlled way to get administrative access in an emergency when normal accounts or approvals are unavailable.
- [ChatOps approval](/glossary/chatops-approval/): A ChatOps approval is a request and approval for access carried out in a team chat tool such as Slack or Teams.
- [CIEM](/glossary/ciem/): CIEM, cloud infrastructure entitlement management, is the category of tools that inventory who holds which permissions across cloud accounts, compare them with what is used, and report or remove the excess.
- [Cloud security intent enforcement](/glossary/cloud-security-intent-enforcement/): Cloud security intent enforcement, abbreviated CSIE, is a category name for turning an intended security boundary into a lasting cloud control, with impact analysis, staged rollout and ongoing management.
- [Cross-account access](/glossary/cross-account-access/): Cross-account access lets a principal in one account use resources in another.
- [Digital twin (Act's term)](/glossary/digital-twin/): Digital twin is the term Act uses for a model of a customer's cloud environment, built from configuration and access data, against which it says it tests a proposed change before enforcement.
- [Dormant identity](/glossary/dormant-identity/): A dormant identity is a user, role or workload identity that still exists and holds permissions but has not been used for a defined period.
- [Effective permissions](/glossary/effective-permissions/): Effective permissions are what an identity can actually do once every policy that applies to it has been evaluated together: identity policies, resource policies, boundaries and denies.
- [Entitlement](/glossary/entitlement/): An entitlement is a single grant of access: a permission, a role assignment or a policy statement that lets an identity perform an action on a resource.
- [Excess permission](/glossary/excess-permission/): An excess permission is a permission an identity holds that its work does not require.
- [IAM role](/glossary/iam-role/): An IAM role is an AWS identity with permissions that a person, application or service assumes for a session, receiving temporary credentials.
- [Infrastructure as code pull request](/glossary/infrastructure-as-code-pull-request/): An infrastructure as code pull request is a proposed change to Terraform, CloudFormation or similar files, submitted for review before it is applied.
- [Inline policy](/glossary/inline-policy/): An inline policy is a policy embedded in a single IAM user, group or role, with a strict one-to-one relationship to that identity.
- [Just-in-time access](/glossary/just-in-time-access/): Just-in-time access grants a permission only when it is requested and approved, for a limited time, and removes it afterward.
- [Least privilege](/glossary/least-privilege/): Least privilege is the security idea that each person, process or workload receives only the access its function needs and nothing more.
- [Non-human identity](/glossary/non-human-identity/): A non-human identity is an identity used by software rather than a person: a role, service account, workload identity or key.
- [Permission creep](/glossary/permission-creep/): Permission creep is the slow growth of an identity's permissions as new access is added for new tasks and old access is never taken away.
- [Policy drift](/glossary/policy-drift/): Policy drift is the divergence between the policy a team intended and the policy actually deployed in the cloud, caused by console edits, emergency changes and unmanaged accounts.
- [Policy simulation](/glossary/policy-simulation/): Policy simulation evaluates a proposed access change against past or hypothetical requests to show who would gain or lose access before the change is made.
- [Principle of least privilege](/glossary/principle-of-least-privilege/): The principle of least privilege is the rule, written into control AC-6 of NIST SP 800-53, that systems allow only the accesses necessary to accomplish assigned tasks.
- [Privilege escalation](/glossary/privilege-escalation/): Privilege escalation is gaining more access than was granted, usually by using one permission to obtain another, such as assuming a more powerful role or editing a policy.
- [Reachability](/glossary/reachability/): Reachability is whether one resource or identity can get to another once network paths and IAM permissions are considered together.
- [Right-sizing](/glossary/right-sizing/): Right-sizing is reducing an identity's permissions to match what it uses in ordinary operation.
- [Service-linked role](/glossary/service-linked-role/): A service-linked role is a predefined IAM role that an AWS service owns and assumes to call other AWS services for you.
- [Standing access](/glossary/standing-access/): Standing access is access that is always on: a role assignment, a group membership or a long-lived key that exists whether or not anyone is working.
- [Third-party access](/glossary/third-party-access/): Third-party access is access that an outside company, such as a monitoring or cost vendor, holds to your cloud resources, usually through a role the vendor assumes.
- [Toxic combination](/glossary/toxic-combination/): A toxic combination is a set of individually modest findings that together create a path to damage, for example an exposed workload, a known vulnerability and a role that can read sensitive data.
- [Unused permission](/glossary/unused-permission/): An unused permission is one an identity holds but has not exercised within a stated observation window.
- [Wildcard permission](/glossary/wildcard-permission/): A wildcard permission uses a star to match many actions or resources at once, such as every action of a service.
- [Zero standing privileges](/glossary/zero-standing-privileges/): Zero standing privileges is a target state in which no identity holds persistent elevated access.

Last reviewed 10 Nov 2026. Canonical: https://cloudleastprivilege.com/glossary/
