Block public access on storage the agent can write to
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 12 of 30: Block public access on storage the agent can write to. An agent that can change a bucket setting, or write to a bucket that already allows public reads, can expose data by accident. Account-level public access blocks stop that even when a policy says otherwise.
The whole checklist ยท The map
Why it matters
An agent that can change a bucket setting, or write to a bucket that already allows public reads, can expose data by accident. Account-level public access blocks stop that even when a policy says otherwise.
How, in each cloud
- AWS
- Turn on S3 Block Public Access settings.
- Google Cloud
- Enable public access prevention on buckets or through the organization policy constraint.
- Azure
- Disable anonymous access on storage accounts; Microsoft recommends this.
What the documentation says
- "The Amazon S3 Block Public Access feature provides settings for access points, buckets, accounts, and" (source)
- "Public access prevention protects Cloud Storage buckets and objects" (source)
- "We recommend that you disable anonymous access for optimal security." (source)
- Previous: Keep the encryption keys for agent data under your control and limit who can use them
- Next: Put data stores the agent reads inside a perimeter that blocks copying data out
Related pages
- Put data stores the agent reads inside a perimeter that blocks copying data out: the check, and how in AWS, Google Cloud and Azure
- Limit data access with tags, attributes or conditions, not only resource lists: the check, and how in AWS, Google Cloud and Azure
- Run agent compute on private networks with no direct path to the internet: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access, read 10 Nov 2026
- cloud.google.com/storage/docs/public-access-prevention, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent, read 10 Nov 2026
Last reviewed 16 Nov 2026.