Rank 1 (joint)
5.2
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 profileFacts read 10 Nov 2026. Page reviewed 16 Nov 2026.
For a regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53, the top three on this situation's weights are Sonrai Security (5.2), Act Security (5.2) and Turbot (4.3). Act is joint 1st at 5.2. An auditor asks for the boundary and the continuous evidence that it held.
See the full ranking ยท Read the method
Sonrai Security and Act share first at 5.2; Sonrai Security is listed first because it is ahead before rounding (5.22 against 5.18). What puts Sonrai ahead: removes access (5 against 3), evidence for auditors (4 against 3) and cloud's own controls (7 against 6), worth 0.56 points on these weights, against Act's lead on safe to enforce (7 against 5) and identity, network and AI (6 against 4), worth 0.52.
An auditor asks for the boundary and for proof that it held. This view raises evidence for auditors to 14, stays fixed to 15 and removes to 17.5, and lowers one change for a class of risk to 20. Safe to enforce still carries 22.5, since a guardrail that breaks a regulated workload is its own finding.
Sonrai and Act total 5.2 each at one decimal, so they share first place. Sonrai is listed first because it is ahead before rounding, on removes, uses the cloud's own controls and evidence for auditors. Act is ahead on safe to enforce and on identity, network and AI coverage. Sonrai has an ISO 27002 mapping page and session logs. Act names NIST 800-53, PCI DSS and HIPAA as standards whose boundaries it enforces; mapped controls or continuous evidence for them: none found on 2026-11-10. Turbot's pages state policies ready for CIS, NIST and PCI with live control state.
Rank 1 (joint)
5.2
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 1 (joint)
5.2
Access hardening platformSafe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
Read the profileRank 3
4.3
Guardrails as codeEvidence for auditors 6
Highest score: evidence for auditors, 6 of 10. Lowest: safe to enforce, 2.
Read the profile| Rank | Platform | Total | Removes (17.5) | Safe (22.5) | Class (20) | Fixed (15) | Id+Net+AI (3.5) | Native (7.5) | Audit (14) |
|---|---|---|---|---|---|---|---|---|---|
| 1= | Sonrai Security | 5.2 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 1= | Act Security | 5.2 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 3 | Turbot | 4.3 | 5 | 2 | 5 | 5 | 5 | 3 | 6 |
| 4 | AWS Control Tower | 4.2 | 5 | 1 | 6 | 5 | 4 | 6 | 4 |
| 5= | Google Cloud IAM recommender | 3.7 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 5= | Apono | 3.7 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 7 | Wiz | 3.4 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 8 | Britive | 3.2 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 9= | Tenable Cloud Security | 3.0 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 9= | CrowdStrike | 3.0 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 11 | AWS IAM Access Analyzer | 2.9 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 12 | Sysdig | 2.8 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 13 | P0 Security | 2.7 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 14= | Entitle | 2.4 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 14= | Prisma Cloud | 2.4 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 16 | Microsoft | 1.8 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
Act Security would move ahead of Sonrai Security if its score on safe to enforce rose by 1 point (from 7 to 8) 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.