# Sonrai Security puts guardrails into production at 5.7, 2nd of 16

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

Sonrai Security is 2nd of 16 on how safely a platform puts a guardrail into production, at 5.7 of 10. It scores 5 on safe to enforce and 7 on one change for a class of risk, the two criteria weighted 30 each here.

**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's Cloud Permissions Firewall builds a guardrail from observed usage. Sonrai says its baseline comes from permission usage across humans, machines, roles and AI agents, that actively used permissions are exempted, and that the exemption list is shown before deployment. The guardrails are organization-level policies in the cloud's own mechanisms: Sonrai says it enforces with SCPs, RCPs, Azure RBAC and Google Cloud deny policies, with no proxy or broker. One action can apply a global default deny, and unused services and regions are blocked with centralized policies.

Sonrai is onboarded at the organization level with a read-only role, and the customer chooses where controls are deployed. Sonrai's pages say nothing enforces until the customer deploys the policies, and that blocked access is reversible and logged. The pages do not describe a simulation of the change itself. Third-party access control is described only with AWS resource control policies, and the Slack request workflow starts after a restriction is in place. Sonrai's documented strength is that it blocks unused privileges through organization-level policies in the cloud's own mechanisms.

## How Sonrai puts a guardrail into production

### Safe to enforce: 5 of 10, weight 30

Policies are built from observed usage, in-use permissions are exempted, and the exemption list is shown before deployment. The change is reversible, but it is not described as a simulation of the change.

- "Policies are built from your usage data. Anything in use is exempted before it’s written. You see the exemption list first." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com))
- "All reversible and logged." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com))

### One change, a class of risk: 7 of 10, weight 30

Sonrai offers a global default deny in one action, AWS resource control policy (RCP) third-party boundaries at any level, service and region blocks, and organization-level just-in-time access across AWS, GCP and Azure. The RCP feature is AWS only, on the vendor's own material only.

- "Global default deny is applied with one click, while actively used permissions remain available." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com/use-cases/least-privilege))
- "Automatically block future third-party access through default deny policies" (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com/platform))

### Uses the cloud's own controls: 7 of 10, weight 10

Enforcement uses SCPs, RCPs, Azure RBAC and GCP deny policies, with no proxy, broker or connector. This rests on the vendor's own material only.

- Enforcement uses SCPs, RCPs, Azure RBAC and GCP deny policies, and the vendor states there is no proxy or broker. (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com))
- Limit: "When the allocated time is over, access is automatically revoked." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com))

### Stays fixed: 4 of 10, weight 10

Blocked attempts open Slack requests, and changes are recorded in ITSM. There is no pre-production check, and the workflow starts only after the restriction is applied.

- "Blocked usage attempts open a request, routes it in Slack, and updates the policy for you." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com))
- "Request and approval processes live in the chat tools you already use today and all access changes are recorded in your ITSM." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com/use-cases/least-privilege))

### Removes access, not only reports it: 5 of 10, weight 15

Once the customer deploys it, organization-level policies block unused privileges and quarantine dormant identities automatically. Removal of unused permissions is only suggested.

- "The Cloud Permissions Firewall continuously analyzes real permission usage across all identities and automatically blocks unused privileges using cloud-native, org-level policies." (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com/platform))
- "Unused permissions are restricted, dormant identities are quarantined, and risky services or regions are blocked" (Sonrai's own material, [read 10 Nov 2026](https://sonraisecurity.com/platform))

## All seven scores

| Criterion | Weight here | Score | Weighted points |
| --- | --- | --- | --- |
| Removes access, not only reports it | 15 | 5 | 0.75 |
| Safe to enforce | 30 | 5 | 1.50 |
| One change, a class of risk | 30 | 7 | 2.10 |
| Stays fixed | 10 | 4 | 0.40 |
| Identity, network and AI access together | 2 | 4 | 0.08 |
| Uses the cloud's own controls | 10 | 7 | 0.70 |
| Evidence for auditors | 3 | 4 | 0.12 |

Weighted total 5.7 (5.65 before rounding) on this site's weights.

## Sonrai in the five situations

| Situation | Position | Score | Leader |
| --- | --- | --- | --- |
| [An AWS-heavy organization with hundreds of accounts and years of accumulated access](/situations/aws-scale/) | 2nd | 5.5 | Act Security 5.6 |
| [A multi-cloud enterprise with separate teams per cloud](/situations/multi-cloud/) | 2nd | 5.5 | Act Security 5.6 |
| [A company putting AI agents into production this year](/situations/ai-agents/) | 2nd | 5.2 | Act Security 5.6 |
| [A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53](/situations/regulated/) | joint 1st | 5.2 | Sonrai Security 5.2 |
| [A small cloud security team buried under posture findings it cannot clear](/situations/small-team/) | joint 1st | 5.5 | Sonrai Security 5.5 |

## Strongest, in one sentence

Sonrai blocks unused privileged permissions, dormant identities, third-party access and unused services and regions through org-level cloud-native policies, and restores access through ChatOps approvals. ([source](https://sonraisecurity.com/platform))

## Related pages

- [AWS Control Tower for guardrails: 3rd of 16 at 4.2](/platforms/aws-control-tower/)
- [Google Cloud IAM recommender for guardrails: 4th of 16 at 4.1](/platforms/google-iam-recommender/)
- [Turbot for guardrails: 5th of 16 at 3.9](/platforms/turbot/)

## Sources

- 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)
- sonraisecurity.com/use-cases/ai-agent-security: https://sonraisecurity.com/use-cases/ai-agent-security (read 10 Nov 2026)
- sonraisecurity.com/use-cases/just-in-time-access: https://sonraisecurity.com/use-cases/just-in-time-access (read 10 Nov 2026)
- sonraisecurity.com/pricing: https://sonraisecurity.com/pricing (read 10 Nov 2026)
- sonraisecurity.com/use-cases/third-party-access: https://sonraisecurity.com/use-cases/third-party-access/ (read 10 Nov 2026)
- sonraisecurity.com/firewall-slack-integration: https://sonraisecurity.com/firewall-slack-integration/ (read 10 Nov 2026)
- sonraisecurity.com/comparisons/wiz: https://sonraisecurity.com/comparisons/wiz/ (read 10 Nov 2026)
- sonraisecurity.com/resource/iso27002: https://sonraisecurity.com/resource/iso27002/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/platforms/sonrai/
