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.
Wiz, now part of Google Cloud, is a CNAPP whose security graph connects code, cloud, identities and runtime, and it routes fixes to code owners as pull requests and tickets. It totals 3.4 against Act's 5.2. Wiz is stronger on audit (6 against 3) and matches Act on coverage (6). The analyst report read says a generated fix is not an applied control until it reaches the customer's pipeline, and Wiz scores 1 on class where Act scores 7.
The seven criteria side by side
Act Security 5.2 (5.15), Wiz 3.4 (3.40) on the index weights.
Criterion
Weight
Act
Wiz
Ahead
Removes access, not only reports it
25
3
3
level
Safe to enforce
20
7
4
Act
One change, a class of risk
15
7
1
Act
Stays fixed
15
4
4
level
Identity, network and AI access together
10
6
6
level
Uses the cloud's own controls
10
6
2
Act
Evidence for auditors
5
3
6
Wiz
Act Security 5.2 (5.15), Wiz 3.4 (3.40) on the index weights.
Why each scores what it scores
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. 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. 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. Wiz 1: Only a limit is documented: translation into durable cross-cloud controls is unvalidated.
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. Wiz 2: Wiz abstracts requirements from provider technology. Whether its output is a native preventive control is left open.
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. 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. Act leads, 5.2 against 3.3. 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.
Wiz
Connects code, cloud, identities, network and runtime in one security graph to prioritize exploitable risk and route fixes to code owners.