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), Tenable Cloud Security 3.2 (3.20) on the index weights.
Criterion
Weight
P0
Tenable
Ahead
Removes access, not only reports it
25
5
5
level
Safe to enforce
20
0
3
Tenable
One change, a class of risk
15
2
0
P0
Stays fixed
15
3
4
Tenable
Identity, network and AI access together
10
4
5
Tenable
Uses the cloud's own controls
10
5
0
P0
Evidence for auditors
5
3
5
Tenable
P0 Security 3.1 (3.05), Tenable Cloud Security 3.2 (3.20) on the index weights.
Why each scores what it scores
Safe to enforce. P0 0: None found on 2026-11-10 after checking 20 pages. Tenable 3: The product shows the diff between a generated policy and the current one. No simulation against the environment is described.
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. Tenable 0: None found on 2026-11-10 after checking 19 pages.
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. Tenable 4: Infrastructure-as-code template scanning is offered, with tickets and approvals in Jira, Slack and Teams. No exception or drift handling is described.
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. Tenable 5: Identity across AWS, Azure and GCP and overprivileged AI identities are covered. Network coverage is limited to public-accessibility context.
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. Tenable 0: None found on 2026-11-10 after checking 19 pages.
Evidence for auditors. P0 3: P0 provides a full action-chain audit trail and a SOC 2 case study. No mapped controls are shown. Tenable 5: Continuous detection is aligned to CIS, NIST and PCI DSS. No detail on evidence export is given.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. Tenable leads, 3.1 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. Tenable leads, 3.5 against 3.0. The full ranking for this situation.