Skip to content
Cloud Governance Tools

The Guardrail Library: 100 preventive guardrails, 40 for AWS, 30 for Azure and 30 for Google Cloud

The library holds 100 preventive guardrails: 40 for AWS, 30 for Azure and 30 for Google Cloud. By risk class it counts 19 AI services, 14 identity and privilege, 13 encryption and keys, 10 public exposure, 9 organization integrity, 8 data exfiltration, 8 logging, 7 network, 7 resource and cost, and 5 region.

Download the library ยท Read the method

Every entry comes from a source that can be checked, and nothing is invented. Sixty entries are taken from open source sets under their licenses: 33 for AWS from the aws-samples service-control-policy-examples and resource-control-policy-examples repositories (27 SCPs and 6 RCPs, MIT-0, with the LICENSE file read) and 27 for Azure from the Azure/azure-policy repository (MIT License). The other 40 are written from provider documentation: 7 for AWS, 3 for Azure and 30 for Google Cloud, where the entries are organization policy constraints and other mechanisms Google documents.

Each entry gives the policy, the mechanism it uses, what it blocks, what it breaks, and how to test it before applying. "Breaks" is taken from the source's own README or from the provider's documentation, with the quote and the page it came from. Where the provider documents no way to test a guardrail, the entry says "none found on 2026-11-10". Entries were read on 10 Nov 2026, and the source link on each entry goes to the exact file or page.

By risk class

Every entry

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.
GuardrailCloudMechanismRisk classTested first
Deny member accounts leaving the organizationAWSService control policies (SCPs)Organization integritydocumented
Prevent root credentials management in member accountsAWSService control policies (SCPs)Identity and privilegedocumented
Deny the root user except for S3 bucket policy changesAWSService control policies (SCPs)Identity and privilegedocumented
Deny critical IAM user actionsAWSService control policies (SCPs)Identity and privilegedocumented
Deny creating or changing IAM federation providersAWSService control policies (SCPs)Identity and privilegedocumented
Prevent creating or expanding public connectivity for VPCsAWSService control policies (SCPs)Network perimeterdocumented
Deny billing, tax and account contact changesAWSService control policies (SCPs)Organization integritydocumented
Deny enabling and disabling AWS ConfigAWSService control policies (SCPs)Logging and monitoringdocumented
Deny modifications to specific CloudTrail trailsAWSService control policies (SCPs)Logging and monitoringdocumented
Deny disabling or modifying Amazon GuardDutyAWSService control policies (SCPs)Logging and monitoringdocumented
Deny deleting VPC flow logsAWSService control policies (SCPs)Logging and monitoringdocumented
Deny KMS key deletionAWSService control policies (SCPs)Encryption and keysdocumented
Enforce a 30-day KMS key deletion windowAWSService control policies (SCPs)Encryption and keysdocumented
Deny disabling default EBS encryptionAWSService control policies (SCPs)Encryption and keysdocumented
Require server-side encryption on S3 uploadsAWSService control policies (SCPs)Encryption and keysdocumented
Deny access outside approved RegionsAWSService control policies (SCPs)Region and residencydocumented
Deny enabling or disabling opt-in RegionsAWSService control policies (SCPs)Region and residencydocumented
Region deny that allows Bedrock cross-Region inferenceAWSService control policies (SCPs)AI servicesdocumented
Allow only approved Amazon Bedrock modelsAWSService control policies (SCPs)AI servicesdocumented
Deny Amazon Bedrock API keysAWSService control policies (SCPs)AI servicesdocumented
Limit Amazon Bedrock long-term API keys to under 30 daysAWSService control policies (SCPs)AI servicesdocumented
Deny IAM and account actions invoked from chat applicationsAWSService control policies (SCPs)AI servicesdocumented
Restrict EC2 launches to approved instance typesAWSService control policies (SCPs)Resource and costdocumented
Restrict AWS Marketplace subscription changesAWSService control policies (SCPs)Resource and costdocumented
Deny disabling block public access for AMIsAWSService control policies (SCPs)Public exposuredocumented
Deny AWS RAM sharing with external accountsAWSService control policies (SCPs)Data exfiltrationdocumented
Require IAM authentication on Lambda function URLsAWSService control policies (SCPs)Public exposuredocumented
Require HTTPS for access to resourcesAWSResource control policies (RCPs)Encryption and keysdocumented
Require TLS 1.2 or later for S3AWSResource control policies (RCPs)Encryption and keysdocumented
Deny changes to S3 Block Public Access at bucket levelAWSResource control policies (RCPs)Public exposuredocumented
Deny unauthenticated access to Cognito identity poolsAWSResource control policies (RCPs)Public exposuredocumented
Deny S3 customer-provided encryption keys (SSE-C)AWSResource control policies (RCPs)Encryption and keysdocumented
Restrict access to resources in a suspended OUAWSResource control policies (RCPs)Organization integritydocumented
Block internet gateway ingress for VPCs (declarative policy)AWSDeclarative policiesNetwork perimeterdocumented
Block public sharing of EBS snapshots (declarative policy)AWSDeclarative policiesData exfiltrationdocumented
Require IMDSv2 for new EC2 instances (declarative policy)AWSDeclarative policiesIdentity and privilegedocumented
Enforce an Amazon Bedrock guardrail on model inference (declarative policy)AWSDeclarative policiesAI servicesnone found
Opt out of AI service content use organization-wide (declarative policy)AWSDeclarative policiesAI servicesdocumented
Permissions boundary limiting a user to S3, CloudWatch and EC2AWSIAM permissions boundariesIdentity and privilegedocumented
Permissions boundary for delegated IAM user creationAWSIAM permissions boundariesIdentity and privilegedocumented
Allowed locations for new resourcesAzureAzure Policy (built-in definitions)Region and residencydocumented
Allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Not allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Do not allow deletion of resource typesAzureAzure Policy (built-in definitions)Organization integritydocumented
Allowed virtual machine size SKUsAzureAzure Policy (built-in definitions)Resource and costdocumented
Network interfaces should not have public IPsAzureAzure Policy (built-in definitions)Public exposuredocumented
Network interfaces should disable IP forwardingAzureAzure Policy (built-in definitions)Network perimeterdocumented
Gateway subnets should not have a network security groupAzureAzure Policy (built-in definitions)Network perimeterdocumented
Configure storage accounts to disallow public blob accessAzureAzure Policy (built-in definitions)Public exposuredocumented
Storage accounts should disable public network accessAzureAzure Policy (built-in definitions)Public exposuredocumented
Storage accounts should have the specified minimum TLS versionAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Storage accounts should prevent shared key accessAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Storage SAS tokens should adhere to 7 day maximum validityAzureAzure Policy (built-in definitions)Data exfiltrationdocumented
Key vaults should have deletion protection enabledAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Azure Key Vault should use the RBAC permission modelAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Configure key vaults to enable the firewallAzureAzure Policy (built-in definitions)Network perimeterdocumented
OS and data disks should be encrypted with a customer-managed keyAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Azure SQL Database should have Microsoft Entra-only authentication enabledAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Deploy diagnostic settings for Key Vault to Event HubAzureAzure Policy (built-in definitions)Logging and monitoringdocumented
Application Insights components should block non-Entra ingestionAzureAzure Policy (built-in definitions)Logging and monitoringdocumented
Configure Cognitive Services accounts to disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Cognitive Services accounts to disable local authenticationAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Azure AI Services resources to disable local key accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Azure Machine Learning workspaces to disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Azure Machine Learning registry deployments restricted to the allowed registry (preview)AzureAzure Policy (built-in definitions)AI servicesdocumented
Microsoft Foundry agents and toolboxes should not use denied tools (preview)AzureAzure Policy (built-in definitions)AI servicesdocumented
Azure AI Search services should disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Deployment stack deny settings (Azure RBAC deny assignment)AzureAzure RBAC deny assignments (created by deployment stacks)Organization integritynone found
Resource locks (CanNotDelete and ReadOnly)AzureAzure resource locksOrganization integritynone found
Allowed locations assigned at a management groupAzureManagement group assignmentRegion and residencydocumented
Disable service account key creationGoogle CloudOrganization Policy Service (managed and legacy constraints)Identity and privilegenone found
Disable automatic IAM grants for default service accountsGoogle CloudOrganization Policy Service (managed and legacy constraints)Identity and privilegenone found
Require OS LoginGoogle CloudOrganization Policy Service (managed and legacy constraints)Identity and privilegenone found
Deny service account key create and delete to a group on one projectGoogle CloudIAM deny policiesIdentity and privilegedocumented
Domain restricted sharingGoogle CloudOrganization Policy Service (managed and legacy constraints)Data exfiltrationnone found
Service perimeter around managed servicesGoogle CloudVPC Service Controls (service perimeters)Data exfiltrationdocumented
Allowed destinations for exporting resourcesGoogle CloudOrganization Policy Service (managed and legacy constraints)Data exfiltrationnone found
Custom constraint limiting IAM role grants to organization membersGoogle CloudCustom organization policy constraintsData exfiltrationdocumented
Principal access boundary limiting the resources principals can accessGoogle CloudPrincipal access boundary (PAB) policiesData exfiltrationdocumented
Enforce public access prevention on Cloud StorageGoogle CloudOrganization Policy Service (managed and legacy constraints)Public exposurenone found
Restrict public IP access on Cloud SQL instancesGoogle CloudOrganization Policy Service (managed and legacy constraints)Public exposurenone found
Define allowed external IPs for VM instancesGoogle CloudOrganization Policy Service (managed and legacy constraints)Public exposurenone found
Skip default network creationGoogle CloudOrganization Policy Service (managed and legacy constraints)Network perimeternone found
Restrict VPC peering usageGoogle CloudOrganization Policy Service (managed and legacy constraints)Network perimeternone found
Require predefined policies for VPC flow logsGoogle CloudOrganization Policy Service (managed and legacy constraints)Logging and monitoringnone found
Disable Audit Logging exemptionGoogle CloudOrganization Policy Service (managed and legacy constraints)Logging and monitoringnone found
Restrict which services may create resources without CMEKGoogle CloudOrganization Policy Service (managed and legacy constraints)Encryption and keysnone found
Restrict unencrypted HTTP access to Cloud StorageGoogle CloudOrganization Policy Service (managed and legacy constraints)Encryption and keysnone found
Restrict key destruction to disabled key versionsGoogle CloudOrganization Policy Service (managed and legacy constraints)Encryption and keysnone found
Resource location restrictionGoogle CloudOrganization Policy Service (managed and legacy constraints)Region and residencynone found
Restrict resource service usageGoogle CloudOrganization Policy Service (managed and legacy constraints)Organization integritydocumented
Restrict Shared VPC host project lien removalGoogle CloudOrganization Policy Service (managed and legacy constraints)Organization integritynone found
Deny deleting projects tagged prodGoogle CloudIAM deny policiesOrganization integritydocumented
Restrict public IP access on new Vertex AI Workbench instancesGoogle CloudOrganization Policy Service (managed and legacy constraints)AI servicesnone found
Disable root access on new Vertex AI Workbench notebooks and instancesGoogle CloudOrganization Policy Service (managed and legacy constraints)AI servicesnone found
Define access to models on Vertex AIGoogle CloudOrganization Policy Service (managed and legacy constraints)AI servicesnone found
Disable Grounding with Google Search in generative AI APIsGoogle CloudOrganization Policy Service (managed and legacy constraints)AI servicesnone found
Restrict egress domains for data connectorsGoogle CloudOrganization Policy Service (managed and legacy constraints)AI servicesdocumented
Shared reservations owner projectsGoogle CloudOrganization Policy Service (managed and legacy constraints)Resource and costnone found
Restrict load balancer creation based on load balancer typesGoogle CloudOrganization Policy Service (managed and legacy constraints)Resource and costnone found

Cite this

Cite this

Cite this line: 'Cloud Governance Tools, The Guardrail Library, edition 10 Nov 2026, https://cloudgovernancetools.com/datasets/'

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. AWS: Require IAM authentication on Lambda function URLs, read 10 Nov 2026
  2. AWS: Restrict access to resources in a suspended OU, read 10 Nov 2026
  3. AWS: Opt out of AI service content use organization-wide (declarative policy), read 10 Nov 2026
  4. AWS: Permissions boundary for delegated IAM user creation, read 10 Nov 2026
  5. Azure: Azure AI Search services should disable public network access, read 10 Nov 2026
  6. Azure: Deployment stack deny settings (Azure RBAC deny assignment), read 10 Nov 2026
  7. Azure: Resource locks (CanNotDelete and ReadOnly), read 10 Nov 2026
  8. Azure: Allowed locations assigned at a management group, read 10 Nov 2026

Last reviewed 16 Nov 2026.