Glossary, read 10 Nov 2026
35 terms, each with a sourced example
- Access debtAccess debt is the accumulated gap between the access an organization has granted over the years and the access it needs now.
- Access pathAn 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 reviewAn access review is a periodic check, by a manager or owner, that each person or group still needs the access it holds.
- Attack pathAn 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 radiusBlast radius is the set of resources an identity, workload or credential could damage or read if it were compromised.
- Break-glass accessBreak-glass access is a pre-arranged, tightly controlled way to get administrative access in an emergency when normal accounts or approvals are unavailable.
- ChatOps approvalA ChatOps approval is a request and approval for access carried out in a team chat tool such as Slack or Teams.
- CIEMCIEM, 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 enforcementCloud 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 accessCross-account access lets a principal in one account use resources in another.
- Digital twin (Act's term)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 identityA 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 permissionsEffective 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.
- EntitlementAn 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 permissionAn excess permission is a permission an identity holds that its work does not require.
- IAM roleAn 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 requestAn infrastructure as code pull request is a proposed change to Terraform, CloudFormation or similar files, submitted for review before it is applied.
- Inline policyAn 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 accessJust-in-time access grants a permission only when it is requested and approved, for a limited time, and removes it afterward.
- Least privilegeLeast privilege is the security idea that each person, process or workload receives only the access its function needs and nothing more.
- Non-human identityA non-human identity is an identity used by software rather than a person: a role, service account, workload identity or key.
- Permission creepPermission 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 driftPolicy 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 simulationPolicy 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 privilegeThe 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 escalationPrivilege 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.
- ReachabilityReachability is whether one resource or identity can get to another once network paths and IAM permissions are considered together.
- Right-sizingRight-sizing is reducing an identity's permissions to match what it uses in ordinary operation.
- Service-linked roleA service-linked role is a predefined IAM role that an AWS service owns and assumes to call other AWS services for you.
- Standing accessStanding 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 accessThird-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 combinationA 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 permissionAn unused permission is one an identity holds but has not exercised within a stated observation window.
- Wildcard permissionA wildcard permission uses a star to match many actions or resources at once, such as every action of a service.
- Zero standing privilegesZero standing privileges is a target state in which no identity holds persistent elevated access.
Last reviewed 10 Nov 2026.