# Allow outbound traffic only to the destinations the agent needs

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

Check 16 of 30: Allow outbound traffic only to the destinations the agent needs. Open outbound access lets a hijacked agent reach any server to send data or fetch tools. A short allow list makes unexpected destinations fail and show up in logs.

## Why it matters

Open outbound access lets a hijacked agent reach any server to send data or fetch tools. A short allow list makes unexpected destinations fail and show up in logs.

## How, in each cloud

- **AWS:** Use security group rules and AWS Network Firewall to filter traffic at the perimeter of the VPC.
- **Google Cloud:** Use VPC firewall rules to allow or deny connections, including egress.
- **Azure:** Use network security groups to allow or deny outbound traffic, and Azure Firewall for central filtering.

## What the documentation says

- "The security group acts as a virtual firewall." ([source](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html))
- "(Amazon VPC). With Network Firewall, you can filter traffic at the perimeter of your VPC." ([source](https://docs.aws.amazon.com/network-firewall/latest/developerguide/what-is-aws-network-firewall.html))
- "VPC firewall rules let you allow or deny connections to or" ([source](https://cloud.google.com/firewall/docs/firewalls))
- "You can use an Azure network security group to filter network traffic between Azure resources in Azure virtual networks." ([source](https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview))
- "Azure Firewall is a cloud-native, intelligent network firewall security service" ([source](https://learn.microsoft.com/en-us/azure/firewall/overview))

- [Previous: Run agent compute on private networks with no direct path to the internet](/checklist/private-network-no-direct-internet/)
- [Next: Reach cloud APIs and data stores through private endpoints](/checklist/private-endpoints-for-cloud-apis/)

## Related pages

- [Reach cloud APIs and data stores through private endpoints: the check, and how in AWS, Google Cloud and Azure](/checklist/private-endpoints-for-cloud-apis/)
- [Keep the agent's code from reading node, instance or other workloads' credentials: the check, and how in AWS, Google Cloud and Azure](/checklist/credential-isolation/)
- [Give each tool function its own least-privilege role instead of the agent's role: the check, and how in AWS, Google Cloud and Azure](/checklist/tool-own-role/)

## Sources

- docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html (read 10 Nov 2026)
- docs.aws.amazon.com/network-firewall/latest/developerguide/what-is-aws-network-f: https://docs.aws.amazon.com/network-firewall/latest/developerguide/what-is-aws-network-firewall.html (read 10 Nov 2026)
- cloud.google.com/firewall/docs/firewalls: https://cloud.google.com/firewall/docs/firewalls (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview: https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/firewall/overview: https://learn.microsoft.com/en-us/azure/firewall/overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/allowlist-egress/
