Network perimeter guardrails restrict connectivity, and they cover less than the name suggests
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
7 guardrails in the library address network perimeter: 2 AWS, 3 Azure, 2 Google Cloud. The first in the list, "Prevent creating or expanding public connectivity for VPCs", denies attaching or creating internet gateways, creating VPC peering connections and creating or updating AWS Global Accelerator resources unless the caller is the privileged role.
All risk classes ยท Download the library
Guardrails in this class restrict public connectivity, forwarding, firewalls and default networks. The library holds 7. They break connectivity someone needed, and they stop less than readers assume. The AWS entry that prevents creating or expanding public VPC connectivity does not block existing direct internet access or access routed through an on-premises network, per its README. AWS's declarative VPC block public access policy stops administrators changing the enforced configuration while attached. Azure's gateway subnet definition blocks a network security group that would make the gateway stop working. Google's skip-default-network constraint means new projects have no default network.
| Guardrail | Cloud | Mechanism | Risk class | Tested first |
|---|---|---|---|---|
| Prevent creating or expanding public connectivity for VPCs | AWS | Service control policies (SCPs) | Network perimeter | documented |
| Block internet gateway ingress for VPCs (declarative policy) | AWS | Declarative policies | Network perimeter | documented |
| Network interfaces should disable IP forwarding | Azure | Azure Policy (built-in definitions) | Network perimeter | documented |
| Gateway subnets should not have a network security group | Azure | Azure Policy (built-in definitions) | Network perimeter | documented |
| Configure key vaults to enable the firewall | Azure | Azure Policy (built-in definitions) | Network perimeter | documented |
| Skip default network creation | Google Cloud | Organization Policy Service (managed and legacy constraints) | Network perimeter | none found |
| Restrict VPC peering usage | Google Cloud | Organization Policy Service (managed and legacy constraints) | Network perimeter | none found |
What these guardrails break
- Prevent creating or expanding public connectivity for VPCs (AWS): The README states it does not block existing direct internet access or access routed through an on-premises network, and VPC peering and Global Accelerator changes also need the privileged role.
- Block internet gateway ingress for VPCs (declarative policy) (AWS): While the policy is attached, account administrators cannot change the enforced configuration; AWS lists ModifyVpcBlockPublicAccessOptions, CreateVpcBlockPublicAccessExclusion and ModifyVpcBlockPublicAccessExclusion as blocked.
- Network interfaces should disable IP forwarding (Azure): Interfaces with IP forwarding enabled are rejected, and the definition says the setting should be reviewed by the network security team.
- Gateway subnets should not have a network security group (Azure): You cannot filter gateway subnet traffic with an NSG while this applies; the definition states that an NSG on a gateway subnet makes the gateway stop functioning.
- Configure key vaults to enable the firewall (Azure): Modify changes the property during create or update instead of rejecting the request, and existing vaults change only through a remediation task.
- Skip default network creation (Google Cloud): Google documents that, by default, a default network and supporting resources are created with each project, so projects created under this constraint have none and need a network created for them.
- Restrict VPC peering usage (Google Cloud): Google documents that each peering end is required to have peering permission, so both sides must allow the peer.
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
Sources
- Prevent creating or expanding public connectivity for VPCs, read 10 Nov 2026
- Block internet gateway ingress for VPCs (declarative policy), read 10 Nov 2026
- Network interfaces should disable IP forwarding, read 10 Nov 2026
- Gateway subnets should not have a network security group, read 10 Nov 2026
- Configure key vaults to enable the firewall, read 10 Nov 2026
- Skip default network creation, read 10 Nov 2026
- Restrict VPC peering usage, read 10 Nov 2026
Last reviewed 16 Nov 2026.