Act is not a CNAPP: it does not scan workloads or vulnerabilities (none found on 2026-11-10), and it publishes no pricing. It also does not make the change itself: it has read-only access to your cloud and delivers each change as a pull request to your Terraform or CloudFormation, or as a ticket, for your team to apply, and handling of violations and time-bound waivers after a change ships was described as roadmap.
Act Security and Sonrai Security share first at 5.2 on the main weights. Sonrai is listed first because it is ahead before rounding, 5.20 against 5.15. The reason is who applies the change. Sonrai applies it: its policies block unused access once deployed, and it scores 5 on removes. Act is read-only and the customer applies each change, so Act scores 3. Act leads on safe to enforce (7 against 5) and on identity, network and AI coverage (6 against 4).
The seven criteria side by side
Act Security 5.2 (5.15), Sonrai Security 5.2 (5.20) on the index weights.
Criterion
Weight
Act
Sonrai
Ahead
Removes access, not only reports it
25
3
5
Sonrai
Safe to enforce
20
7
5
Act
One change, a class of risk
15
7
7
level
Stays fixed
15
4
4
level
Identity, network and AI access together
10
6
4
Act
Uses the cloud's own controls
10
6
7
Sonrai
Evidence for auditors
5
3
4
Sonrai
Act Security 5.2 (5.15), Sonrai Security 5.2 (5.20) on the index weights.
Why each scores what it scores
Removes access. Act 3: Changes are delivered as infrastructure-as-code pull requests that the customer applies. The product is read-only, and direct enforcement is still under discussion. Sonrai 5: Once the customer deploys it, organization-level policies block unused privileges and quarantine dormant identities automatically. Removal of unused permissions is only suggested.
Safe to enforce. Act 7: Each change is tested against a digital twin built from cloud configuration data and run in audit mode against audit-log events before enforcement. This is on the vendor's own material only, and rare dependencies may go untested. Sonrai 5: 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.
Identity, network and AI. Act 6: One model combines identity, network, resource and organization controls with configured, effective and observed access, plus endpoint and cloud AI agents. Customer evidence for AI is less mature. Sonrai 4: Identities, including AI agent identities, are enforced at the IAM layer. No network reachability model is described.
Cloud's own controls. Act 6: Act enforces through named native controls (security groups, NSGs, SCPs, RCPs, private endpoints) delivered via infrastructure as code, with no new infrastructure. For AI agents it also enforces on the agent and the gateway. Sonrai 7: 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.
Evidence for auditors. Act 3: Act names NIST 800-53, PCI DSS and HIPAA as boundaries it enforces. No mapped controls or continuous evidence are described. Sonrai 4: Session logs support audit, and an ISO 27002 mapping page exists. The SOC 2 report covers the company itself, and framework support is otherwise generic.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. Sonrai leads, 5.3 against 5.2. The full ranking for this situation.
A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53. Sonrai leads, 5.0 against 4.8. The full ranking for this situation.
A small cloud security team buried under posture findings it cannot clear. Sonrai leads, 5.3 against 5.1. The full ranking for this situation.
Strongest, in one sentence each
Act Security
Act removes broad classes of access by simulating guardrail and ring-fence policies against a digital twin and delivering them as pull requests to the customer's IaC using cloud-native controls.
Sonrai Security
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.