# 40 terms, each with a sourced example

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Plain definitions of the terms used in cloud least privilege, from permissions boundary and service control policy to privilege creep and standing access. Each definition stands alone in one sentence, is tied to a provider or NIST page that was read, and shows the date it was read.

- [Access debt](/glossary/access-debt/): Access debt is the accumulated gap between the access people and workloads hold in a cloud account and the access they need.
- [Access key rotation](/glossary/access-key-rotation/): Access key rotation is replacing an IAM user access key with a new one and deleting the old one on a schedule.
- [Access level](/glossary/access-level/): An access level is an AWS classification of an action as List, Read, Write, Permissions management or Tagging.
- [Active assignment](/glossary/active-assignment/): An active assignment is a Microsoft Entra Privileged Identity Management assignment that gives the user the role's privileges without any activation step.
- [Assignable scope](/glossary/assignable-scope/): An assignable scope is a field in an Azure role definition that lists where the role can be assigned, such as subscriptions or management groups.
- [Attribute-based access control](/glossary/attribute-based-access-control/): Attribute-based access control grants or denies access by comparing attributes of the caller, the resource and the request, such as tags.
- [Basic role](/glossary/basic-role/): A basic role is a Google Cloud role that provides broad access across services.
- [Built-in role](/glossary/built-in-role/): A built-in role is an Azure role defined by Microsoft that can be assigned without writing a role definition.
- [Custom policy check](/glossary/custom-policy-check/): A custom policy check is an IAM Access Analyzer test that compares a policy update against your security standard, for example to see if it grants new access compared with the existing version.
- [Custom role](/glossary/custom-role/): A custom role is a role whose permission list the customer writes, used when no provider-supplied role matches the task.
- [Data action](/glossary/data-action/): A data action is an Azure permission for operations on the data inside a resource, such as reading a blob, as opposed to managing the resource itself.
- [Data perimeter](/glossary/data-perimeter/): A data perimeter is a set of always-on permissions guardrails around identities, resources and networks that helps prevent unintended access.
- [Deny policy](/glossary/deny-policy/): A deny policy is a Google Cloud policy of deny rules that stop chosen principals from using chosen permissions, whatever roles they hold.
- [Eligible assignment](/glossary/eligible-assignment/): An eligible assignment is a Microsoft Entra Privileged Identity Management assignment that requires the user to activate the role before using it.
- [IAM Conditions](/glossary/iam-conditions/): IAM Conditions are Google Cloud rules that make a role binding, deny rule or boundary apply only when an attribute test passes.
- [Job function policy](/glossary/job-function-policy/): A job function policy is an AWS managed policy that grants the permissions typical for a role in an organization, such as database administrator or security auditor.
- [Last accessed information](/glossary/last-accessed-information/): Last accessed information is a record of when an IAM identity or policy last used a service or action.
- [Long-term credentials](/glossary/long-term-credentials/): Long-term credentials are keys that stay valid until someone deletes or deactivates them, such as AWS IAM user access keys.
- [Managed policy](/glossary/managed-policy/): A managed policy is a standalone IAM policy that exists as its own object and can be attached to many users, groups and roles.
- [MFA condition](/glossary/mfa-condition/): An MFA condition is a policy condition that allows an action only when the caller authenticated with multi-factor authentication.
- [Permission set](/glossary/permission-set/): A permission set is a template in AWS IAM Identity Center that defines a collection of one or more IAM policies.
- [Policy generation](/glossary/policy-generation/): Policy generation is the creation of an IAM policy from observed activity.
- [Policy inheritance](/glossary/policy-inheritance/): Policy inheritance is the Google Cloud rule that a resource receives the allow policies of its parent.
- [Policy validation](/glossary/policy-validation/): Policy validation is the check of an IAM policy against policy grammar and best practices before it is saved.
- [Predefined role](/glossary/predefined-role/): A predefined role is a Google Cloud role that provides granular access to one service and is created and maintained by Google.
- [Principal access boundary](/glossary/principal-access-boundary/): A principal access boundary is a Google Cloud policy that sets which resources a group of principals is eligible to access.
- [Privileged role](/glossary/privileged-role/): A privileged role is a built-in Azure role whose permissions include broad management or the ability to assign access to others.
- [Resource scope](/glossary/resource-scope/): Resource scope is the set of resources a role assignment applies to.
- [Right-sizing](/glossary/right-sizing/): Right-sizing is reducing an identity's permissions to the set it actually uses.
- [Role assignment](/glossary/role-assignment/): A role assignment attaches a role definition to a principal at a scope in Azure.
- [Role assignment condition](/glossary/role-assignment-condition/): A role assignment condition is an extra check added to an Azure role assignment that tests attributes of the request, giving attribute-based access control on top of RBAC.
- [Role chaining](/glossary/role-chaining/): Role chaining is using one AWS role to assume a second role.
- [Role definition](/glossary/role-definition/): A role definition is the Azure object that lists the permissions a role allows.
- [Role recommendation](/glossary/role-recommendation/): A role recommendation is a Google Cloud suggestion from the IAM recommender to remove or replace a role that gives a principal excess permissions.
- [Role-based access control](/glossary/role-based-access-control/): Role-based access control is an authorization approach in which permissions are grouped into roles and people or workloads receive roles instead of individual permissions.
- [Service account impersonation](/glossary/service-account-impersonation/): Service account impersonation is a Google Cloud principal authenticating as a service account to gain its permissions.
- [Session policy](/glossary/session-policy/): A session policy is an AWS policy passed when a role is assumed or a federated user session is created.
- [Temporary credentials](/glossary/temporary-credentials/): Temporary credentials are short-lived keys issued by AWS Security Token Service that expire on their own, and they are the basis of IAM roles and federation.
- [Unused access finding](/glossary/unused-access-finding/): An unused access finding is an IAM Access Analyzer result that reports access granted but not used during a chosen usage window.
- [Zone of trust](/glossary/zone-of-trust/): A zone of trust is the account or organization that an IAM Access Analyzer external access analyzer treats as safe.

## Related pages

- [News](/news/)
- [Least privilege for 20 cloud services](/services/)
- [Routes to least privilege: tools and platforms](/routes/)

Last reviewed 16 Nov 2026. Canonical: https://leastprivilegeprinciple.com/glossary/
