# Identity, network and AI access together: one model of reachability (10 points)

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Identity, network and AI access together weighs 10 of 100 on the Least Privilege Index. Act Security, Wiz, Microsoft score 6, the highest of the 14. The table keeps the index order, so it compares the field on one criterion without re-ranking it.

Does the model of reachability cover all three, including AI workloads and agents.

This criterion asks whether the model of what can reach what covers identity, network and AI workloads and agents together. An identity-only view misses a path that runs through a network rule, and a network-only view misses a role that grants access. Agents combine both. Good evidence describes one model, not three products. Act, Wiz and Microsoft score 6. Sonrai Security scores 4 because it enforces at the IAM layer and no network reachability model was found on 2026-11-10.

| Index rank | Platform | Score | Why |
| --- | --- | --- | --- |
| 1= | [Sonrai Security](/platforms/sonrai/) | 4 | Identities, including AI agent identities, are enforced at the IAM layer. No network reachability model is described. |
| 1= | [Act Security](/platforms/act/) | 6 | One model combines identity, network, resource and organization controls with configured, effective and observed access, plus endpoint and cloud AI agents. Customer evidence for AI is less mature. |
| 3 | [Google Cloud IAM recommender](/platforms/google-iam-recommender/) | 4 | Identity role recommendations and a VPC Service Controls troubleshooter are provided. No AI workloads are covered. |
| 4 | [Apono](/platforms/apono/) | 4 | Identity and AI agents are governed together, with runtime intent checks. No network reachability model is described. |
| 5 | [Britive](/platforms/britive/) | 4 | Britive maps human, agentic AI and non-human identities and their privileges. No network reachability model is described. |
| 6 | [Wiz](/platforms/wiz/) | 6 | A graph connects identities, permissions, network exposure, workloads and data into reachable attack paths, plus AI model and agent discovery. AI coverage is inventory rather than reachability. |
| 7 | [Tenable Cloud Security](/platforms/tenable/) | 5 | Identity across AWS, Azure and GCP and overprivileged AI identities are covered. Network coverage is limited to public-accessibility context. |
| 8 | [P0 Security](/platforms/p0/) | 4 | Identities across several clouds and MCP agent calls are covered. The documentation states that network reachability is not addressed. |
| 9 | [AWS IAM Access Analyzer](/platforms/aws-iam-access-analyzer/) | 2 | Only identity unused access and resource-based policies are covered. No network or AI model is covered. |
| 10 | [CrowdStrike](/platforms/crowdstrike/) | 4 | Identity entitlements and AI security posture management across named AI services are covered. Attack paths do not name network reachability. |
| 11= | [Entitle](/platforms/entitle/) | 4 | Identity access is covered, along with a statement that AI agent functions need a human check for sensitive resources. No network model is described. |
| 11= | [Sysdig](/platforms/sysdig/) | 4 | Identity usage comes from audit logs, and an AI agent inventory is included. Attack paths do not name network reachability. |
| 13 | [Prisma Cloud](/platforms/prisma/) | 5 | Effective permissions across clouds are covered, with a separate network path analyzer. AI agents are covered only by a general statement. |
| 14 | [Microsoft](/platforms/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. |

Index order, not re-ranked by this criterion; weight 10 of 100.

**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

- [Uses the cloud's own controls: the 14 platforms compared](/compare/criteria/native/)
- [Evidence for auditors: the 14 platforms compared](/compare/criteria/audit/)
- [Act Security vs Sonrai Security for CIEM](/compare/act-vs-sonrai/)
- [All of them](/compare/)

## Sources

- sonraisecurity.com/use-cases/least-privilege: https://sonraisecurity.com/use-cases/least-privilege (read 10 Nov 2026)
- act.security/platform: https://act.security/platform (read 10 Nov 2026)
- cloud.google.com/policy-intelligence/docs/overview: https://cloud.google.com/policy-intelligence/docs/overview (read 10 Nov 2026)
- apono.io: https://www.apono.io (read 10 Nov 2026)
- britive.com: https://www.britive.com (read 10 Nov 2026)
- wiz.io: https://www.wiz.io (read 10 Nov 2026)
- tenable.com/products/tenable-cloud-security: https://www.tenable.com/products/tenable-cloud-security (read 10 Nov 2026)
- docs.p0.dev/readme/access-inventory.md: https://docs.p0.dev/readme/access-inventory.md (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://ciemtools.com/compare/criteria/coverage/
