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 profileFacts 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.
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.
Rank 1
5.6
Access hardening platformSafe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
Read the profileRank 2
5.5
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 profileRank 3
4.4
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| 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 | 5.6 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | Sonrai Security | 5.5 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3 | AWS Control Tower | 4.4 | 5 | 1 | 6 | 5 | 4 | 6 | 4 |
| 4 | Turbot | 4.1 | 5 | 2 | 5 | 5 | 5 | 3 | 6 |
| 5 | Google Cloud IAM recommender | 4.0 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 6 | Apono | 3.7 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 7 | Britive | 3.3 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 8 | Wiz | 3.1 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 9 | AWS IAM Access Analyzer | 3.0 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 10 | P0 Security | 2.8 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 11 | Tenable Cloud Security | 2.7 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 12 | CrowdStrike | 2.5 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 13= | Entitle | 2.4 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 13= | Sysdig | 2.4 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 15 | Prisma Cloud | 2.2 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 16 | Microsoft | 1.5 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
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.
Last reviewed 16 Nov 2026.