Skip to content
AI Agent Access Control

Limit data access with tags, attributes or conditions, not only resource lists

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)

Sources

  1. docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-con, read 10 Nov 2026
  2. cloud.google.com/iam/docs/conditions-overview, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/role-based-access-control/conditions-overview, read 10 Nov 2026

Last reviewed 16 Nov 2026.