The 14 platforms compared on each of the seven criteria
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Seven criteria carry fixed weights: removes access 25, safe to enforce 20, one change for a class of risk 15, stays fixed 15, identity, network and AI coverage 10, native controls 10, evidence for auditors 5. Each criterion page shows who scores highest and why.
See the index ยท Read the method
- Removes access, not only reports it (weight 25)Does the product end with an enforced change that takes access away, or with a finding for someone else to act on
- Safe to enforce (weight 20)Is each change simulated against the real environment before it ships, with the impact shown
- One change, a class of risk (weight 15)Boundaries and guardrails that remove many paths at once, as opposed to permission-by-permission clean-up
- Stays fixed (weight 15)Prevents drift: violations checked before production, exceptions handled in the team's own tools, with proof
- Identity, network and AI access together (weight 10)Does the model of reachability cover all three, including AI workloads and agents
- Uses the cloud's own controls (weight 10)Enforcement through native mechanisms the customer already owns, with nothing new in the request path
- Evidence for auditors (weight 5)Mapped controls and continuous evidence for the named frameworks
Where Act is behind
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.
Related pages
Last reviewed 16 Nov 2026.