Skip to content
Cloud Governance Tools

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

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.

Browse the library ยท Simulation matrix

MechanismCloudApplies toEntries
Service control policies (SCPs)AWSIAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.27
Resource control policies (RCPs)AWSResources 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 boundariesAWSA single IAM user or role it is attached to; it does not apply to other principals or to resources.2
Declarative policiesAWSThe 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)AzureResources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions27
Azure RBAC deny assignments (created by deployment stacks)AzurePrincipals named in the deny assignment (all principals when the zero GUID is used), on the managed resources and optionally their child scopes1
Azure resource locksAzureControl plane operations on the locked scope and the resources under it1
Management group assignmentAzureAll subscriptions and resources under the management group in the hierarchy1
Organization Policy Service (managed and legacy constraints)Google CloudResources 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 constraintsGoogle CloudFields of resource types in services that support custom constraints, in the organization where the constraint is created.1
IAM deny policiesGoogle CloudPrincipals named in the deny rules, on the resource the policy is attached to and its descendants.2
VPC Service Controls (service perimeters)Google CloudGoogle 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) policiesGoogle CloudPrincipal 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.

Sources

  1. Service control policies (SCPs), read 10 Nov 2026
  2. Resource control policies (RCPs), read 10 Nov 2026
  3. IAM permissions boundaries, read 10 Nov 2026
  4. Declarative policies, read 10 Nov 2026
  5. Azure Policy (built-in definitions), read 10 Nov 2026
  6. Azure RBAC deny assignments (created by deployment stacks), read 10 Nov 2026
  7. Azure resource locks, read 10 Nov 2026
  8. Management group assignment, read 10 Nov 2026

Last reviewed 16 Nov 2026.