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), AWS IAM Access Analyzer 3.0 (3.00) on the index weights.
Criterion
Weight
P0
Access Analyzer
Ahead
Removes access, not only reports it
25
5
3
P0
Safe to enforce
20
0
4
Access Analyzer
One change, a class of risk
15
2
1
P0
Stays fixed
15
3
4
Access Analyzer
Identity, network and AI access together
10
4
2
P0
Uses the cloud's own controls
10
5
4
P0
Evidence for auditors
5
3
2
P0
P0 Security 3.1 (3.05), AWS IAM Access Analyzer 3.0 (3.00) 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. Access Analyzer 3: Refined policies and delete links are generated, and the user attaches or deletes them.
Safe to enforce. P0 0: None found on 2026-11-10 after checking 20 pages. Access Analyzer 4: The tool previews a policy's effect on public and cross-account access and checks new access against the existing version. It does not simulate the impact of removal, and generated policies omit data events and PassRole.
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. Access Analyzer 1: Access Analyzer only reads RCPs. No boundary generation is listed.
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. Access Analyzer 4: Custom policy checks run before deployment in CI/CD and can trigger approval workflows. 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. Access Analyzer 2: Only identity unused access and resource-based policies are covered. No network or AI model is covered.
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. Access Analyzer 4: It generates native IAM policies from CloudTrail and is not in the request path. It works in one cloud only, and the user applies the result.
Evidence for auditors. P0 3: P0 provides a full action-chain audit trail and a SOC 2 case study. No mapped controls are shown. Access Analyzer 2: A Security Hub control linked to CIS only checks that an analyzer exists. No evidence from findings is provided.