Limit data access with tags, attributes or conditions, not only resource lists
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 14 of 30: Limit data access with tags, attributes or conditions, not only resource lists. Resource lists go stale as new data stores appear. Conditions on tags or attributes keep access tied to what the data is, so a new store does not become reachable by default.
The whole checklist ยท The map
Why it matters
Resource lists go stale as new data stores appear. Conditions on tags or attributes keep access tied to what the data is, so a new store does not become reachable by default.
How, in each cloud
- AWS
- Use attribute-based access control with tags on IAM entities and resources.
- Google Cloud
- Use IAM Conditions on role bindings.
- Azure
- Use Azure role assignment conditions (Azure ABAC) that filter a role's permissions by attributes.
What the documentation says
- "based on attributes. AWS calls these attributes tags . You" (source)
- "You can use IAM Conditions to define and enforce conditional," (source)
- "Azure ABAC builds on Azure RBAC by adding role assignment conditions based on attributes in the context of specific actions." (source)
- Previous: Put data stores the agent reads inside a perimeter that blocks copying data out
- Next: Run agent compute on private networks with no direct path to the internet
Related pages
- Run agent compute on private networks with no direct path to the internet: the check, and how in AWS, Google Cloud and Azure
- Allow outbound traffic only to the destinations the agent needs: the check, and how in AWS, Google Cloud and Azure
- Reach cloud APIs and data stores through private endpoints: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-con, read 10 Nov 2026
- cloud.google.com/iam/docs/conditions-overview, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/role-based-access-control/conditions-overview, read 10 Nov 2026
Last reviewed 16 Nov 2026.