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.
Google Cloud's IAM recommender suggests removing unused roles, and Policy Simulator shows the effect of a change before it is made. It is the highest-scoring platform behind the two leaders, 4.0 against Act's 5.2. It works in Google Cloud only and clean-up is role by role (class 3). A person applies each recommendation, as the customer applies Act's. Act adds a cross-cloud model and boundaries, and scores 4 on fixed against Google's 2.
The seven criteria side by side
Act Security 5.2 (5.15), Google Cloud IAM recommender 4.0 (3.95) on the index weights.
Criterion
Weight
Act
IAM recommender
Ahead
Removes access, not only reports it
25
3
4
IAM recommender
Safe to enforce
20
7
6
Act
One change, a class of risk
15
7
3
Act
Stays fixed
15
4
2
Act
Identity, network and AI access together
10
6
4
Act
Uses the cloud's own controls
10
6
5
Act
Evidence for auditors
5
3
2
Act
Act Security 5.2 (5.15), Google Cloud IAM recommender 4.0 (3.95) 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. IAM recommender 4: A person checks and applies role recommendations in the product. Organization policy recommendations are suggestions only.
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. IAM recommender 6: Simulators show how an allow-policy change affects principals' access, and list resources that would violate a proposed organization policy before enforcement. Each simulator covers one policy type, and only Google Cloud.
One change, a class of risk. Act 7: Act runs broad explicit-deny guardrail campaigns for whole attack categories and explicit-allow ring-fencing, applied at the AWS Organizations and SCP level. This is on the vendor's own material only. IAM recommender 3: Simulators exist for deny and Principal Access Boundary policies, and organization policies are recommended, but clean-up is done role by role.
Stays fixed. Act 4: Act documents drift detection with a diff against cloud versions, a one-line CI/CD blocking claim that does not say what is checked, and a Terraform provider for its own configuration. Exception handling in the customer's tools and rollback are credited only as roadmap or open discussion. Wiz and Sonrai also score 4. IAM recommender 2: Recommendation states are tracked inside the product. The pre-deploy Terraform check is a separate tool, and no ticketing or chat integration was found.
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. IAM recommender 4: Identity role recommendations and a VPC Service Controls troubleshooter are provided. No AI workloads are covered.
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. IAM recommender 5: A recommendation is an operation that removes a member from native IAM policy bindings. It works in one cloud 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. IAM recommender 2: Apply and dismiss actions are logged, and Policy Analyzer serves audit tasks. No compliance framework is named.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. Act leads, 5.2 against 3.9. The full ranking for this situation.
A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53. Act leads, 4.8 against 3.7. The full ranking for this situation.
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.
Google Cloud IAM recommender
The IAM recommender suggests removing or replacing IAM roles that principals have not used, and Policy Simulator shows the effect of a policy change before it is made.