Skip to content
Cloud Governance Tools

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

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.

See the full ranking ยท Read the method

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

5.6

Act Security

Access hardening platformSafe to enforce 7

Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.

Read the profile

Rank 2

5.5

Sonrai Security

Cloud permissions firewallOne change, a class of risk 7

Highest score: one change, a class of risk, 7 of 10. Lowest: stays fixed, 4.

Read the profile

Rank 3

4.4

AWS Control Tower

Provider guardrail serviceOne 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

The full order under these weights

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.
RankPlatformTotalRemoves (17.5)Safe (22.5)Class (22.5)Fixed (15)Id+Net+AI (8.5)Native (12.5)Audit (1.5)
1Act Security5.63774663
2Sonrai Security5.55574474
3AWS Control Tower4.45165464
4Turbot4.15255536
5Google Cloud IAM recommender4.04632452
6Apono3.75333454
7Britive3.35133454
8Wiz3.13414626
9AWS IAM Access Analyzer3.03414242
10P0 Security2.85023453
11Tenable Cloud Security2.75304505
12CrowdStrike2.53404406
13=Entitle2.45023423
13=Sysdig2.43204436
15Prisma Cloud2.23014535
16Microsoft1.52012605

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.

Sources

  1. act.security, read 10 Nov 2026
  2. act.security/platform, read 10 Nov 2026
  3. softwareanalyst.io/reports/the-ciso-s-guide-to-cloud-security-intent-enforcement, read 10 Nov 2026
  4. sonraisecurity.com/platform, read 10 Nov 2026
  5. sonraisecurity.com, read 10 Nov 2026
  6. sonraisecurity.com/use-cases/least-privilege, read 10 Nov 2026

Last reviewed 16 Nov 2026.