# 31 terms, each with a sourced example

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

Plain definitions of the terms used in guardrail work, among them SCP, RCP, permissions boundary, declarative policy, deny assignment, organization policy constraint, perimeter and dry run, each with a sourced example and the reason it matters when approving a policy.

- [Azure Policy](/glossary/azure-policy/): The Azure service that evaluates resources against business rules written as policy definitions, reports compliance, and can block, modify or remediate resources through an effect.
- [Boolean constraint](/glossary/boolean-constraint/): A Google Cloud constraint that is either enforced or not enforced, with no list of values.
- [Custom constraint](/glossary/custom-constraint/): A Google Cloud constraint written by your organization, in a YAML file that names the resources, methods, conditions and actions it applies to.
- [Data perimeter](/glossary/data-perimeter/): A set of preventive guardrails that keeps only trusted identities reaching trusted resources from expected networks.
- [Declarative policy](/glossary/declarative-policy/): An AWS Organizations policy type that states the desired configuration of a service across an organization and keeps it in place, enforced in the service control plane instead of at the authorization layer.
- [Delegated administrator](/glossary/delegated-administrator/): A member account that an AWS service or Organizations feature designates to run that service for the organization, so the management account is used less.
- [Deny assignment](/glossary/deny-assignment/): An Azure RBAC object that attaches a set of deny actions to a user, group or service principal at a scope.
- [Detective control](/glossary/detective-control/): A control that finds noncompliance after a resource exists and reports it through a dashboard or alert, without stopping the change.
- [Dry-run mode](/glossary/dry-run-mode/): A Google Cloud mode in which an organization policy is created and enforced like any other, but violations are written to audit logs and the violating actions are not denied.
- [Enforcement mode](/glossary/enforcement-mode/): A property of an Azure Policy assignment that controls whether the effect is applied.
- [Explicit deny](/glossary/explicit-deny/): A policy statement with a Deny effect that matches a request.
- [Guardrail](/glossary/guardrail/): A policy that sets limits on what identities or resources in a cloud estate can do, without granting any permission itself.
- [IAM deny policy](/glossary/iam-deny-policy/): A Google Cloud IAM policy of deny rules attached to a project, folder or organization.
- [Implicit deny](/glossary/implicit-deny/): The default outcome when no policy allows an action.
- [List constraint](/glossary/list-constraint/): A Google Cloud constraint whose policy holds a list of allowed or denied values, such as a list of permitted domains or Regions.
- [Management account](/glossary/management-account/): The AWS account that created the organization and manages it.
- [Management group](/glossary/management-group/): An Azure governance scope above subscriptions.
- [Organization policy](/glossary/organization-policy/): A Google Cloud policy that sets one constraint on an organization, folder or project and applies to its descendants.
- [Organizational unit](/glossary/organizational-unit/): A container for accounts inside an AWS organization.
- [Permissions boundary](/glossary/permissions-boundary/): An AWS IAM feature that sets the maximum permissions an identity-based policy can grant to one IAM user or role.
- [Policy assignment](/glossary/policy-assignment/): The Azure object that applies a policy definition or initiative to a scope and supplies its parameters.
- [Policy effect](/glossary/policy-effect/): The single action an Azure Policy definition takes when its rule matches: deny, audit, modify, deployIfNotExists and others.
- [Policy exemption](/glossary/policy-exemption/): An Azure Policy object that exempts a resource or resource hierarchy from evaluation of an assignment, with a category and an optional expiry.
- [Policy initiative](/glossary/policy-initiative/): A group of Azure Policy definitions assigned together as one unit, also called a policySet.
- [Preventive control](/glossary/preventive-control/): A control that disallows an action that would lead to a policy violation, so the request fails and the noncompliant state never exists.
- [Principal access boundary](/glossary/principal-access-boundary/): A Google Cloud IAM policy attached to a set of principals that defines which resources those principals are eligible to access.
- [Proactive control](/glossary/proactive-control/): A control that checks a resource before it is deployed, usually inside an infrastructure-as-code pipeline, and fails the deployment if the resource would be noncompliant.
- [Resource control policy](/glossary/resource-control-policy/): An AWS Organizations policy that sets the maximum permissions on resources in member accounts, whoever the caller is.
- [Resource lock](/glossary/resource-lock/): An Azure management lock on a subscription, resource group or resource that blocks deletion or modification regardless of the user's permissions.
- [Service control policy](/glossary/service-control-policy/): An AWS Organizations policy that sets the maximum permissions for IAM users and roles in member accounts.
- [VPC Service Controls perimeter](/glossary/vpc-service-controls-perimeter/): A Google Cloud boundary around projects and supported services that controls data egress and ingress across it, independent of IAM.

## Related pages

- [News](/news/)
- [Preventive guardrail mechanisms in AWS, Azure and Google Cloud](/mechanisms/)
- [Platforms by how safely they put a guardrail into production](/platforms/)

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