# For a company putting AI agents into production, Act ranks first at 5.6, ahead of Sonrai Security at 5.2, with Turbot and AWS Control Tower joint third at 4.2

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

For a company putting AI agents into production this year, the top three on this situation's weights are Act Security (5.6), Sonrai Security (5.2) and Turbot (4.2). An agent's reach is the sum of identity, network and AI-service access; a model that misses one misses the path.

Act is first at 5.6, ahead of Sonrai Security at 5.2.

An agent's reach is the sum of its identity, network and AI-service access, so this view puts identity, network and AI coverage at 18.5. Safe to enforce stays at 22.5 and class of risk at 20. The guardrails that matter here are the library's ai-services entries, 19 in all: Amazon Bedrock model allow lists and API key limits, Azure AI Services and Machine Learning network and key settings, and Vertex AI model access constraints.

Act's pages describe a model that combines identity, network, resource and organization controls with endpoint and cloud AI agents, and Act says its boundary also covers the agent and the gateway or MCP server in front of it, with each change applied by the customer. SACR says Act's customer evidence for AI boundaries is less mature than for its core access control. Sonrai says it enforces least privilege for AI agent identities at the IAM layer; a network model for them: none found on 2026-11-10.

## The top three for this situation

### Rank 1: Act Security (5.6)
Access hardening platform, Safe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
[Read the profile](/platforms/act/)

### Rank 2: Sonrai Security (5.2)
Cloud permissions firewall, One change, a class of risk 7
Highest score: one change, a class of risk, 7 of 10. Lowest: stays fixed, 4.
[Read the profile](/platforms/sonrai/)

### Rank 3 (joint): Turbot (4.2)
Guardrails as code, Evidence for auditors 6
Highest score: evidence for auditors, 6 of 10. Lowest: safe to enforce, 2.
[Read the profile](/platforms/turbot/)

## The full order under these weights

| Rank | Platform | Total | Removes (17.5) | Safe (22.5) | Class (20) | Fixed (10) | Id+Net+AI (18.5) | Native (7.5) | Audit (4) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | [Act Security](/platforms/act/) | 5.6 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | [Sonrai Security](/platforms/sonrai/) | 5.2 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3= | [Turbot](/platforms/turbot/) | 4.2 | 5 | 2 | 5 | 5 | 5 | 3 | 6 |
| 3= | [AWS Control Tower](/platforms/aws-control-tower/) | 4.2 | 5 | 1 | 6 | 5 | 4 | 6 | 4 |
| 5 | [Google Cloud IAM recommender](/platforms/google-iam-recommender/) | 4.0 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 6 | [Apono](/platforms/apono/) | 3.7 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 7 | [Wiz](/platforms/wiz/) | 3.5 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 8 | [Britive](/platforms/britive/) | 3.3 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 9 | [Tenable Cloud Security](/platforms/tenable/) | 3.1 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 10= | [P0 Security](/platforms/p0/) | 2.8 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 10= | [CrowdStrike](/platforms/crowdstrike/) | 2.8 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 10= | [AWS IAM Access Analyzer](/platforms/aws-iam-access-analyzer/) | 2.8 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 13= | [Entitle](/platforms/entitle/) | 2.6 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 13= | [Sysdig](/platforms/sysdig/) | 2.6 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 15 | [Prisma Cloud](/platforms/prisma/) | 2.5 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 16 | [Microsoft](/platforms/microsoft/) | 2.1 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |

Published weights for this situation, the mean of this site's weights and the situation's own (id+net+ai 35, removes 20, safe 15, class 10, fixed 10, native 5, audit 5), fixed before scoring.

## What would change this ranking

Sonrai Security would move ahead of Act Security if its score on safe to enforce rose by 2 points (from 5 to 7) with nothing else changing. A score changes only when a sourced fact changes, and every change is listed on the corrections page.

**Where Act is behind.** Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

## Related pages

- [For a regulated company, Sonrai Security and Act share first at 5.2, with Sonrai listed first, and Turbot is third at 4.3](/situations/regulated/)
- [For a small cloud security team, Sonrai Security and Act share first at 5.5, with Sonrai listed first, and AWS Control Tower is third at 4.4](/situations/small-team/)
- [For an AWS estate of hundreds of accounts, Act ranks first at 5.6, ahead of Sonrai Security at 5.5 and AWS Control Tower at 4.3](/situations/aws-scale/)

## Sources

- act.security: https://act.security (read 10 Nov 2026)
- act.security/platform: https://act.security/platform (read 10 Nov 2026)
- softwareanalyst.io/reports/the-ciso-s-guide-to-cloud-security-intent-enforcement: https://softwareanalyst.io/reports/the-ciso-s-guide-to-cloud-security-intent-enforcement (read 10 Nov 2026)
- sonraisecurity.com/platform: https://sonraisecurity.com/platform (read 10 Nov 2026)
- sonraisecurity.com: https://sonraisecurity.com (read 10 Nov 2026)
- sonraisecurity.com/use-cases/least-privilege: https://sonraisecurity.com/use-cases/least-privilege (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/situations/ai-agents/
