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.
Prisma Cloud, whose next version Palo Alto Networks markets as Cortex Cloud, computes net effective permissions across clouds and sits inside a broad platform with code scanning, network path analysis and compliance standards. It totals 2.6 against Act's 5.2. Prisma Cloud's documentation tells users to copy the command line and run it to remove excess permissions, and says automatic remediation for Google Cloud IAM alerts is not supported. Prisma Cloud scores 0 on safe, Act 7.
The seven criteria side by side
Act Security 5.2 (5.15), Prisma Cloud 2.6 (2.55) on the index weights.
Criterion
Weight
Act
Prisma Cloud
Ahead
Removes access, not only reports it
25
3
3
level
Safe to enforce
20
7
0
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
5
Act
Uses the cloud's own controls
10
6
3
Act
Evidence for auditors
5
3
5
Prisma Cloud
Act Security 5.2 (5.15), Prisma Cloud 2.6 (2.55) 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. Prisma Cloud 0: None found on 2026-11-10 after checking 19 pages.
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. Prisma Cloud 1: Prisma Cloud only reads SCPs as input. It does not create organization-level guardrails.
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. Prisma Cloud 5: Effective permissions across clouds are covered, with a separate network path analyzer. AI agents are covered only by a general statement.
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. Prisma Cloud 3: Remediation runs as native CLI commands that the user executes, with no proxy. It is manual.
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. Prisma Cloud 5: Built-in standards include NIST 800-53, HIPAA, ISO 27001 and SOC 2. Continuous evidence is not described.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. Act leads, 5.2 against 2.4. 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 2.9. 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.
Prisma Cloud
Calculates net effective permissions across clouds, including SCPs as input, and ties them to a broad platform with code scanning, network analysis and a large library of compliance standards.