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), Prisma Cloud 2.6 (2.55) on the index weights.
Criterion
Weight
P0
Prisma Cloud
Ahead
Removes access, not only reports it
25
5
3
P0
Safe to enforce
20
0
0
level
One change, a class of risk
15
2
1
P0
Stays fixed
15
3
4
Prisma Cloud
Identity, network and AI access together
10
4
5
Prisma Cloud
Uses the cloud's own controls
10
5
3
P0
Evidence for auditors
5
3
5
Prisma Cloud
P0 Security 3.1 (3.05), Prisma Cloud 2.6 (2.55) 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. Prisma Cloud 3: IAM fixes are CLI commands the user runs, or a script the user configures. There is no GCP auto-remediation.
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. Prisma Cloud 1: Prisma Cloud only reads SCPs as input. It does not create organization-level guardrails.
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. Prisma Cloud 4: Pull request scans fail at a threshold, alerts go to ServiceNow and Slack, and requests run through ServiceNow. No drift or exception handling was found.
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. 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. 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. Prisma Cloud 3: Remediation runs as native CLI commands that the user executes, with no proxy. It is manual.
Evidence for auditors. P0 3: P0 provides a full action-chain audit trail and a SOC 2 case study. No mapped controls are shown. 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. P0 leads, 2.9 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. P0 leads, 3.0 against 2.9. The full ranking for this situation.
Grants short-lived, scoped access on request through Slack, CLI or web with approvals, and applies the same runtime authorization to AI agents.
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.