Rank 1
5.9
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.
The library holds 100 preventive guardrails: 40 for AWS, 30 for Azure and 30 for Google Cloud, each copied from provider documentation or a licensed open source set, with what it blocks and what it breaks. Act Security leads the platforms at 5.9, ahead of Sonrai Security at 5.7.
Scope: security governance, the guardrail layer. Cost governance is out.
| Risk class | AWS | Azure | Google Cloud | All |
|---|---|---|---|---|
| Identity and privilege | 7 | 3 | 4 | 14 |
| Data exfiltration | 2 | 1 | 5 | 8 |
| Public exposure | 4 | 3 | 3 | 10 |
| Logging and monitoring | 4 | 2 | 2 | 8 |
| Encryption and keys | 7 | 3 | 3 | 13 |
| Network perimeter | 2 | 3 | 2 | 7 |
| Region and residency | 2 | 2 | 1 | 5 |
| Organization integrity | 3 | 3 | 3 | 9 |
| AI services | 7 | 7 | 5 | 19 |
| Resource and cost | 2 | 3 | 2 | 7 |
| Rank | Platform | Total | Removes (15) | Safe (30) | Class (30) | Fixed (10) | Id+Net+AI (2) | Native (10) | Audit (3) |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Act Security | 5.9 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | Sonrai Security | 5.7 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3 | AWS Control Tower | 4.2 | 5 | 1 | 6 | 5 | 4 | 6 | 4 |
| 4 | Google Cloud IAM recommender | 4.1 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 5 | Turbot | 3.9 | 5 | 2 | 5 | 5 | 5 | 3 | 6 |
| 6 | Apono | 3.6 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 7 | Britive | 3.0 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 8= | AWS IAM Access Analyzer | 2.9 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 8= | Wiz | 2.9 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 10= | P0 Security | 2.3 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 10= | CrowdStrike | 2.3 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 10= | Tenable Cloud Security | 2.3 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 13= | Entitle | 2.0 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 13= | Sysdig | 2.0 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 15 | Prisma Cloud | 1.7 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 16 | Microsoft | 1.1 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
Act is first at 5.9, ahead of Sonrai Security at 5.7.
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.
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.
Rank 1
5.9
Access hardening platformSafe to enforce 7
Highest score: safe to enforce, 7 of 10. Lowest: removes access, 3.
Read the profileRank 2
5.7
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.2
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 profileRank 4
4.1
Provider toolSafe to enforce 6
Highest score: safe to enforce, 6 of 10. Lowest: stays fixed, 2.
Read the profileA preventive guardrail is a policy that a cloud evaluates before a request takes effect and answers with a denial. That separates it from a detective control, which reports a violation after the resource exists. A service control policy that denies a leave-organization call, an Azure Policy definition with the deny effect and a Google Cloud organization policy constraint are all preventive. An alert on the same event is not.
Each cloud evaluates its guardrails in a different place. AWS evaluates service control policies and resource control policies together with identity-based and resource-based policies, and the effective permissions are the intersection. Declarative policies work in the service control plane instead. Azure Policy checks create and update requests against assigned definitions. Google Cloud checks IAM deny policies before allow policies, and organization policy constraints, principal access boundaries and VPC Service Controls perimeters each add their own check.
Because a guardrail answers with a denial, its cost is the legitimate work it stops. This library records, for each of 100 entries, what the guardrail blocks and what it breaks, with the source of both. The platforms section ranks sixteen products on how safely they take a guardrail from a draft to production: simulated first, shown against the real environment, and kept in place afterward.
Which platforms show the effect of a guardrail before it is applied, and which provider tools do the same for free: the Simulation Coverage Matrix sets the 16 platforms against the native dry-run and simulation methods of the three clouds.
Last reviewed 16 Nov 2026.