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), Microsoft 1.8 (1.80) on the index weights.
Criterion
Weight
P0
Microsoft
Ahead
Removes access, not only reports it
25
5
2
P0
Safe to enforce
20
0
0
level
One change, a class of risk
15
2
1
P0
Stays fixed
15
3
2
P0
Identity, network and AI access together
10
4
6
Microsoft
Uses the cloud's own controls
10
5
0
P0
Evidence for auditors
5
3
5
Microsoft
P0 Security 3.1 (3.05), Microsoft 1.8 (1.80) 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. Microsoft 2: Microsoft is scored on cloud infrastructure entitlement management (CIEM) in Defender for Cloud, because Entra Permissions Management was retired on 2025-11-01 and has not been sold since 2025-04-01. Defender for Cloud CIEM gives recommendations described as guidance for remediating, and from 2026-08-06 no longer publishes unused-action details for AWS.
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. Microsoft 1: Microsoft is scored on cloud infrastructure entitlement management (CIEM) in Defender for Cloud, because Entra Permissions Management was retired on 2025-11-01 and has not been sold since 2025-04-01. What remains is Azure Policy, a separate Azure service assigned to management groups and not described as acting on CIEM findings.
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. Microsoft 2: Only IaC misconfiguration correlation is documented, and ITSM integration was presented as roadmap.
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. Microsoft 6: Identity across three clouds, network connections and internet exposure in the security graph, and AI agents in attack paths are covered. AI coverage is stated only briefly.
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. Microsoft 0: Microsoft is scored on cloud infrastructure entitlement management (CIEM) in Defender for Cloud, because Entra Permissions Management was retired on 2025-11-01 and has not been sold since 2025-04-01. None found on 2026-11-10 for Defender for Cloud.
Evidence for auditors. P0 3: P0 provides a full action-chain audit trail and a SOC 2 case study. No mapped controls are shown. Microsoft 5: Continuous assessment runs against compliance controls, with export and Purview integration. Non-default standards need a paid plan, and none are named.
Verdict by situation
An AWS-heavy organization with hundreds of accounts and years of accumulated access. P0 leads, 2.9 against 1.7. 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.1. The full ranking for this situation.