# 13 preventive mechanisms across three clouds, and where each is evaluated

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

Thirteen mechanisms enforce the library's guardrails: four in AWS (SCPs, RCPs, permissions boundaries, declarative policies), four in Azure (Azure Policy, deny assignments, locks, management groups) and five in Google Cloud. Each has its own scope, limits and testing method, and each entry in the library names the one it uses.

| Mechanism | Cloud | Applies to | Entries |
| --- | --- | --- | --- |
| [Service control policies (SCPs)](/mechanisms/scp/) | AWS | IAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles. | 27 |
| [Resource control policies (RCPs)](/mechanisms/rcp/) | AWS | Resources of supported services in member accounts, for any principal calling them; not resources in the management account and not service-linked roles. | 6 |
| [IAM permissions boundaries](/mechanisms/permissions-boundary/) | AWS | A single IAM user or role it is attached to; it does not apply to other principals or to resources. | 2 |
| [Declarative policies](/mechanisms/declarative-policy/) | AWS | The configuration of a supported AWS service attribute in the accounts, OUs or organization they are attached to, including actions by service-linked roles. | 5 |
| [Azure Policy (built-in definitions)](/mechanisms/azure-policy/) | Azure | Resources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions | 27 |
| [Azure RBAC deny assignments (created by deployment stacks)](/mechanisms/rbac-deny-assignment/) | Azure | Principals named in the deny assignment (all principals when the zero GUID is used), on the managed resources and optionally their child scopes | 1 |
| [Azure resource locks](/mechanisms/resource-lock/) | Azure | Control plane operations on the locked scope and the resources under it | 1 |
| [Management group assignment](/mechanisms/management-groups/) | Azure | All subscriptions and resources under the management group in the hierarchy | 1 |
| [Organization Policy Service (managed and legacy constraints)](/mechanisms/org-policy/) | Google Cloud | Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive. | 25 |
| [Custom organization policy constraints](/mechanisms/custom-org-policy/) | Google Cloud | Fields of resource types in services that support custom constraints, in the organization where the constraint is created. | 1 |
| [IAM deny policies](/mechanisms/iam-deny/) | Google Cloud | Principals named in the deny rules, on the resource the policy is attached to and its descendants. | 2 |
| [VPC Service Controls (service perimeters)](/mechanisms/vpc-service-controls/) | Google Cloud | Google Cloud managed services and the projects in the perimeter; Google says it does not block access to third-party APIs or services on the internet. | 1 |
| [Principal access boundary (PAB) policies](/mechanisms/principal-access-boundary/) | Google Cloud | Principal sets bound to the policy through a policy binding; blocks only permissions in the policy enforcement version. | 1 |

**Where Act is behind.** Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

## Related pages

- [Platforms by how safely they put a guardrail into production](/platforms/)
- [Picks by situation](/situations/)
- [Guides](/guides/)

## Sources

- Service control policies (SCPs): https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html (read 10 Nov 2026)
- Resource control policies (RCPs): https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html (read 10 Nov 2026)
- IAM permissions boundaries: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html (read 10 Nov 2026)
- Declarative policies: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_declarative.html (read 10 Nov 2026)
- Azure Policy (built-in definitions): https://learn.microsoft.com/en-us/azure/governance/policy/concepts/effect-deny (read 10 Nov 2026)
- Azure RBAC deny assignments (created by deployment stacks): https://learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments (read 10 Nov 2026)
- Azure resource locks: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources (read 10 Nov 2026)
- Management group assignment: https://learn.microsoft.com/en-us/azure/governance/management-groups/overview (read 10 Nov 2026)

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