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.
The seven criteria side by side
P0 Security 3.1 (3.05), Wiz 3.4 (3.40) on the index weights.
Criterion
Weight
P0
Wiz
Ahead
Removes access, not only reports it
25
5
3
P0
Safe to enforce
20
0
4
Wiz
One change, a class of risk
15
2
1
P0
Stays fixed
15
3
4
Wiz
Identity, network and AI access together
10
4
6
Wiz
Uses the cloud's own controls
10
5
2
P0
Evidence for auditors
5
3
6
Wiz
P0 Security 3.1 (3.05), Wiz 3.4 (3.40) on the index weights.
Why each scores what it scores
Removes access. P0 5: Just-in-time access is provisioned and revoked automatically, with history. Posture findings get suggested shell commands only. Wiz 3: Wiz generates plans, policies and pull requests sent to code owners. A generated fix is not an applied control.
Safe to enforce. P0 0: None found on 2026-11-10 after checking 20 pages. Wiz 4: Wiz evaluates historical activity to judge disruption before remediation. This is not a simulation of control changes, and infrequent dependencies are not covered.
One change, a class of risk. P0 2: A deny-all policy blocks access requests made through the product for an account. It is not a cloud boundary. Wiz 1: Only a limit is documented: translation into durable cross-cloud controls is unvalidated.
Stays fixed. P0 3: Requests arrive through Slack, findings go to Jira, and a Terraform provider exists. No pre-production check or drift handling is described. Wiz 4: Policies across the IDE, pull requests and CI/CD can block unsafe changes, and Jira tickets are created. Exceptions, drift and paths outside the pipeline lack evidence.
Identity, network and AI. P0 4: Identities across several clouds and MCP agent calls are covered. The documentation states that network reachability is not addressed. Wiz 6: A graph connects identities, permissions, network exposure, workloads and data into reachable attack paths, plus AI model and agent discovery. AI coverage is inventory rather than reachability.
Cloud's own controls. P0 5: Default paths are agentless on native IAM, with session-bound roles in AWS and GCP. The AI Gateway sits in the agent data path, and connectors broker just-in-time access. Wiz 2: Wiz abstracts requirements from provider technology. Whether its output is a native preventive control is left open.
Evidence for auditors. P0 3: P0 provides a full action-chain audit trail and a SOC 2 case study. No mapped controls are shown. Wiz 6: Automated compliance covers PCI, GDPR, HIPAA and custom frameworks, with auditor reports. This rests on the vendor's own material only.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. Wiz leads, 3.3 against 2.9. The full ranking for this situation.
A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53. Wiz leads, 3.7 against 3.0. The full ranking for this situation.