# Put data stores the agent reads inside a perimeter that blocks copying data out

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

Check 13 of 30: Put data stores the agent reads inside a perimeter that blocks copying data out. An agent allowed to read data can usually also send it somewhere else unless something stops the transfer. A perimeter turns an allowed read into a read that cannot leave.

## Why it matters

An agent allowed to read data can usually also send it somewhere else unless something stops the transfer. A perimeter turns an allowed read into a read that cannot leave.

## How, in each cloud

- **AWS:** Build a data perimeter with identity, resource and network controls, including VPC endpoint policies.
- **Google Cloud:** Use VPC Service Controls, which Google documents as protecting against the risk of data exfiltration.
- **Azure:** Use virtual network service endpoint policies to allow data exfiltration only to specific Azure Storage accounts.

## What the documentation says

- "Many organizations want to implement perimeter controls to help protect against unintended" ([source](https://docs.aws.amazon.com/whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.html))
- "An endpoint policy is a resource-based policy that you attach to a VPC endpoint to control" ([source](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html))
- "VPC Service Controls helps protect against the risk of data exfiltration" ([source](https://cloud.google.com/vpc-service-controls/docs/overview))
- "allow data exfiltration to only specific Azure Storage accounts" ([source](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoint-policies-overview))

- [Previous: Block public access on storage the agent can write to](/checklist/block-public-exposure/)
- [Next: Limit data access with tags, attributes or conditions, not only resource lists](/checklist/condition-based-data-access/)

## Related pages

- [Limit data access with tags, attributes or conditions, not only resource lists: the check, and how in AWS, Google Cloud and Azure](/checklist/condition-based-data-access/)
- [Run agent compute on private networks with no direct path to the internet: the check, and how in AWS, Google Cloud and Azure](/checklist/private-network-no-direct-internet/)
- [Allow outbound traffic only to the destinations the agent needs: the check, and how in AWS, Google Cloud and Azure](/checklist/allowlist-egress/)

## Sources

- docs.aws.amazon.com/whitepapers/latest/building-a-data-perimeter-on-aws/building: https://docs.aws.amazon.com/whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.html (read 10 Nov 2026)
- docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html: https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html (read 10 Nov 2026)
- cloud.google.com/vpc-service-controls/docs/overview: https://cloud.google.com/vpc-service-controls/docs/overview (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoint: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoint-policies-overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/data-perimeter/
