# For a multi-cloud enterprise, Act ranks first at 5.6, ahead of Sonrai Security at 5.5 and AWS Control Tower at 4.4

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

For a multi-cloud enterprise with separate teams per cloud, the top three on this situation's weights are Act Security (5.6), Sonrai Security (5.5) and AWS Control Tower (4.4). Separate teams per cloud need changes enforced through each cloud's own controls and exceptions handled in each team's tools.

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

Separate teams per cloud mean three sets of mechanisms: SCPs and RCPs in AWS, Azure Policy and deny assignments in Azure, organization policy, IAM deny and VPC Service Controls in Google Cloud. This view weights stays fixed at 15, uses the cloud's own controls at 12.5 and identity, network and AI coverage at 8.5, above their usual weights, on top of safe to enforce and class of risk at 22.5 each.

The evidence differs sharply by cloud. Sonrai documents enforcement through SCPs, RCPs, Azure RBAC and Google Cloud deny policies. Act's pages name AWS and Azure boundaries, and no Google Cloud boundary mechanism was found on 2026-11-10. AWS Control Tower is AWS only. A platform that covers one cloud well can still rank below one that covers three adequately.

## 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.5)
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: AWS Control Tower (4.4)
Provider guardrail service, One change, a class of risk 6
Highest score: one change, a class of risk, 6 of 10. Lowest: safe to enforce, 1.
[Read the profile](/platforms/aws-control-tower/)

## The full order under these weights

| Rank | Platform | Total | Removes (17.5) | Safe (22.5) | Class (22.5) | Fixed (15) | Id+Net+AI (8.5) | Native (12.5) | Audit (1.5) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | [Act Security](/platforms/act/) | 5.6 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | [Sonrai Security](/platforms/sonrai/) | 5.5 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3 | [AWS Control Tower](/platforms/aws-control-tower/) | 4.4 | 5 | 1 | 6 | 5 | 4 | 6 | 4 |
| 4 | [Turbot](/platforms/turbot/) | 4.1 | 5 | 2 | 5 | 5 | 5 | 3 | 6 |
| 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 | [Britive](/platforms/britive/) | 3.3 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 8 | [Wiz](/platforms/wiz/) | 3.1 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 9 | [AWS IAM Access Analyzer](/platforms/aws-iam-access-analyzer/) | 3.0 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 10 | [P0 Security](/platforms/p0/) | 2.8 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 11 | [Tenable Cloud Security](/platforms/tenable/) | 2.7 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 12 | [CrowdStrike](/platforms/crowdstrike/) | 2.5 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 13= | [Entitle](/platforms/entitle/) | 2.4 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 13= | [Sysdig](/platforms/sysdig/) | 2.4 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 15 | [Prisma Cloud](/platforms/prisma/) | 2.2 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 16 | [Microsoft](/platforms/microsoft/) | 1.5 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |

Published weights for this situation, the mean of this site's weights and the situation's own (removes 20, safe 15, class 15, fixed 20, id+net+ai 15, native 15, audit 0), 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 1 point (from 5 to 6) 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 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](/situations/ai-agents/)
- [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/)

## 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/multi-cloud/
