Rank 1
5.3
Act Security
Access hardening platformSafe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
Read the profileFacts read 10 Nov 2026. Page reviewed 16 Nov 2026.
An AI agent in your cloud can reach whatever the identity it runs as can reach: an IAM execution role in AWS, a service account in Google Cloud, a managed identity in Azure. The Agent Access Map covers 8 agent platforms; the checklist has 30 checks.
| Agent platform | Cloud | Runs as | By default | Boundaries that apply |
|---|---|---|---|---|
| Amazon Bedrock Agents (now Amazon Bedrock Agents Classic) | AWS | AWS documents that the agent runs as an IAM service role that Amazon Bedrock assumes. | The documented service role policy covers invoking named foundation models, reading the OpenAPI schema objects in S3, and querying attached knowledge bases, with optional statements for guardrails, collaborators and code interpretation. | IAM identity-based policy on the agent service role; Trust policy conditions (aws:SourceAccount, aws:SourceArn); Resource-based policy on the action group Lambda function; SCPs and permissions boundaries; VPC endpoint policy |
| Amazon Bedrock AgentCore (Runtime, Gateway, Identity) | AWS | Runtime runs the agent under an IAM execution role that AgentCore assumes. | AWS documents that the console can create the execution role for you if the console role has the listed IAM create permissions, and that Gateway can create a service role and attach permissions each time you add a target. | IAM policy on the execution role and gateway service role; Resource-based policies on AgentCore resources; SCPs and permissions boundaries; IAM deny of InvokeAgentRuntimeForUser; AgentCore Policy at Gateway; VPC security groups |
| Agent Runtime on Gemini Enterprise Agent Platform (formerly Vertex AI Agent Engine, Agent Builder) | Google Cloud | Google documents three choices: a per-agent IAM agent identity (recommended, a principal tied to the individual agent); the Google-managed AI Platform Reasoning Engine Service Agent used by default; or a custom service account. | With agent identity, an agent starts with the Agent Default Access role (basic project-wide logging and model calling) and the Agent Context Editor role (own sessions, memories and sandboxes only). | IAM allow policies on the agent identity; IAM deny policy; Principal Access Boundary policy; Context-Aware Access (mTLS binding); VPC Service Controls; Organization policy for cross-project service accounts |
| Gemini Enterprise (agents hosted on Agent Runtime) | Google Cloud | Gemini Enterprise registers an ADK agent that runs on Agent Runtime, so the agent runs under the Agent Runtime identity described in that entry. | Permissions Gemini Enterprise itself grants to a registered agent: none found on 2026-11-10. | Gemini Enterprise IAM roles; Agent sharing state; VPC Service Controls; Agent Runtime IAM, deny, PAB |
| Microsoft Foundry Agent Service (formerly Azure AI Foundry Agent Service) | Azure | Each agent gets a Microsoft Entra agent identity, a special service principal created under an agent blueprint. | Microsoft documents that a newly created agent identity starts without resource permissions and that Foundry does not automatically assign RBAC roles to it; you or an administrator grant access through the target service. | Azure RBAC on the agent identity; Foundry RBAC roles and agent-scope assignments; Azure Policy; Virtual network isolation; Hosted agent sandbox |
| Self-hosted agent on AWS Lambda or Amazon EKS | AWS | A Lambda function runs as its execution role. | When you create a function in the Lambda console, AWS documents that it creates an execution role with minimal permissions (basic logging to CloudWatch Logs). | IAM policy on the execution role or pod role; Pod Identity trust policy conditions; SCPs and permissions boundaries; IMDS restriction |
| Self-hosted agent on Google Cloud Run or GKE | Google Cloud | Cloud Run runs the service as a service account (the Compute Engine default service account if you do not choose one). | Google documents that, depending on organization policy, the Compute Engine default service account might automatically be granted the Editor role on the project, and that the constraint iam.automaticIamGrantsForDefaultServiceAccounts is enforced by default for organizations created after May 3, 2024. | IAM roles on the service account; Organization policy iam.automaticIamGrantsForDefaultServiceAccounts; IAM deny policies; Principal Access Boundary policies |
| Self-hosted agent on Azure Container Apps or AKS | Azure | A container app can have a system-assigned managed identity (tied to the app) or user-assigned identities (standalone resources). | Microsoft documents that for some resources you must configure role assignments for the app's managed identity, otherwise calls to services such as Key Vault and SQL Database are rejected even with a valid token. | Azure RBAC role assignments; Azure Policy; Deny assignments; Kubernetes network policy on AKS |
| Rank | Tool | Total | Removes (20) | Safe (15) | Class (10) | Fixed (10) | Id+Net+AI (35) | Native (5) | Audit (5) |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Act Security | 5.3 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | Sonrai Security | 4.8 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3 | Wiz | 4.2 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 4 | Google Cloud IAM recommender | 4.0 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 5= | Apono | 3.9 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 5= | Tenable Cloud Security | 3.9 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 7 | Britive | 3.6 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 8= | CrowdStrike | 3.3 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 8= | P0 Security | 3.3 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 8= | Prisma Cloud | 3.3 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 11= | Entitle | 3.2 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 11= | Sysdig | 3.2 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 13 | Microsoft | 3.1 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
| 14 | AWS IAM Access Analyzer | 2.7 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
Act is first at 5.3, ahead of Sonrai Security at 4.8.
Where Act is behind
Act draws the boundary at the access layer (cloud IAM and network controls, and the gateways or MCP servers in front of agents); it does not inspect prompts or model outputs, which needs a different tool. Your team applies the boundaries it proposes, and its customer evidence for AI boundaries is less mature than for its core access control.
Sonrai Security would move ahead of Act Security if its score on identity, network and AI rose by 2 points (from 4 to 6) with nothing else changing. A score changes only when a sourced fact changes, and every change is listed on the corrections page.
Rank 1
5.3
Access hardening platformSafe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
Read the profileRank 2
4.8
Cloud permissions firewallOne change, a class of risk 7
Highest score: one change, a class of risk, 7 of 10. Lowest: identity, network and AI, 4.
Read the profileRank 3
4.2
CNAPP with entitlement managementIdentity, network and AI 6
Highest score: identity, network and AI, 6 of 10. Lowest: one change, a class of risk, 1.
Read the profileRank 4
4.0
Provider toolSafe to enforce 6
Highest score: safe to enforce, 6 of 10. Lowest: stays fixed, 2.
Read the profileAI workload access is what an agent can do inside a cloud account once it is running. It has four parts: the identity the agent runs as, what that identity can reach, the network paths in and out, and the logs that record what happened. An agent is a workload with a role. It has no other standing in the account, so the cloud's ordinary controls are what bound it.
The identity differs by platform. Amazon Bedrock AgentCore runs an agent as an IAM execution role. Agent Runtime on Google Cloud can give each agent its own identity. Microsoft Foundry creates an Entra agent identity that starts with no resource permissions. A self-hosted agent on Lambda, Cloud Run or Container Apps runs as the role or managed identity you attach. What that identity can reach is the sum of its policies, less any ceiling above it.
The Agent Access Map shows this for eight setups, from provider documentation. The Agent Boundary Checklist turns it into 30 checks for the approval meeting. The site also scores 14 tools on how well they cover identity, network and AI access together. Agent identity products, MCP gateways and prompt filtering are different categories and are not scored here.
30 checks in 7 groups, each with the mechanism to use in AWS, Google Cloud and Azure and the provider page that documents it.
Last reviewed 16 Nov 2026.