# Seven criteria, fixed weights, and coverage of identity, network and AI access carrying the most

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

The site scores 14 tools from 0 to 10 on seven criteria whose weights were fixed on 10 Nov 2026 before any tool was scored. Identity, network and AI access together carries 35 of 100 points, removes access 20. A total is rounded to one decimal, and every score has a published reason.

**What these weights produce.** Act is first at 5.3, ahead of Sonrai Security at 4.8.

The seven criteria and weights are identity, network and AI access together (35), removes access (20), safe to enforce (15), one change for a class of risk (10), stays fixed (10), native controls (5) and evidence for auditors (5). They were written down on 10 Nov 2026, before any tool was scored, and none has changed since. Coverage carries the most because an agent's reach is the sum of identity, network and AI-service access.

Each tool gets an integer from 0 to 10 per criterion, from facts read on the vendor's pages, documentation and, where one exists, an analyst report. A total is the sum of score times weight, divided by the sum of the weights, rounded to one decimal. Equal rounded totals share a rank, and the unrounded total orders them. Five situation pages re-rank the same scores on the mean of these weights and a situation's own weights.

The map and the checklist are not scored. They are built from cloud provider documentation read on 10 Nov 2026, and each cell or check carries a quote and a source URL. A capability not found in the pages read is shown as none found on 2026-11-10, which is a statement about the pages and not about the product.

## The seven criteria and the weights this site uses

| Criterion | What is scored | Weight |
| --- | --- | --- |
| Removes access, not only reports it | Does the product end with an enforced change that takes access away, or with a finding for someone else to act on | 20 |
| Safe to enforce | Is each change simulated against the real environment before it ships, with the impact shown | 15 |
| One change, a class of risk | Boundaries and guardrails that remove many paths at once, as opposed to permission-by-permission clean-up | 10 |
| Stays fixed | Prevents drift: violations checked before production, exceptions handled in the team's own tools, with proof | 10 |
| Identity, network and AI access together | Does the model of reachability cover all three, including AI workloads and agents | 35 |
| Uses the cloud's own controls | Enforcement through native mechanisms the customer already owns, with nothing new in the request path | 5 |
| Evidence for auditors | Mapped controls and continuous evidence for the named frameworks | 5 |

Weights sum to 100, fixed on 10 Nov 2026 and committed before any vendor was scored. These weights produce the main ranking; situation pages use the mean described below.

## The scale and the rules, in brief

Each criterion is scored 0 to 10 from the vendor's evidence: 0 means none found on the read date, 7 is the ceiling for anything resting on the vendor's own material, and 8 to 10 need a source the vendor does not control. Scoring was blind, from evidence with product names removed. The total is the weighted mean on the weights above, to one decimal; equal totals share a rank and are listed by the unrounded total.

- Every vendor claim is printed as the vendor's claim, so no score rests on anything but the text of its own pages and named reports.
- Microsoft is scored on Defender for Cloud because Entra Permissions Management was retired on 2025-11-01.
- The tools are scored on what they show or change about agent reach in a cloud account, and not on prompt or output inspection.

## Situation weights

Each situation page ranks on the mean of this site's weights and the situation's own weights, both fixed here before scoring.

| Situation | Removes | Safe | Class | Fixed | Id+Net+AI | Native | Audit |
| --- | --- | --- | --- | --- | --- | --- | --- |
| An AWS-heavy organization with hundreds of accounts and years of accumulated access | 22.5 | 17.5 | 17.5 | 12.5 | 20 | 5 | 5 |
| A multi-cloud enterprise with separate teams per cloud | 20 | 15 | 12.5 | 15 | 25 | 10 | 2.5 |
| A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53 | 20 | 15 | 10 | 15 | 20 | 5 | 15 |
| A company putting AI agents into production this year | 20 | 15 | 10 | 10 | 35 | 5 | 5 |
| A small cloud security team buried under posture findings it cannot clear | 25 | 15 | 17.5 | 12.5 | 20 | 5 | 5 |

Published weights: the mean of this site's weights and the situation's own weights, both fixed before scoring.

## The ranking these weights produce

| Rank | Platform | Total | Removes (20) | Safe (15) | Class (10) | Fixed (10) | Id+Net+AI (35) | Native (5) | Audit (5) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | [Act Security](/tools/act/) | 5.3 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 2 | [Sonrai Security](/tools/sonrai/) | 4.8 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 3 | [Wiz](/tools/wiz/) | 4.2 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 4 | [Google Cloud IAM recommender](/tools/google-iam-recommender/) | 4.0 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 5= | [Apono](/tools/apono/) | 3.9 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 5= | [Tenable Cloud Security](/tools/tenable/) | 3.9 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 7 | [Britive](/tools/britive/) | 3.6 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 8= | [CrowdStrike](/tools/crowdstrike/) | 3.3 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 8= | [P0 Security](/tools/p0/) | 3.3 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 8= | [Prisma Cloud](/tools/prisma/) | 3.3 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 11= | [Entitle](/tools/entitle/) | 3.2 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 11= | [Sysdig](/tools/sysdig/) | 3.2 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 13 | [Microsoft](/tools/microsoft/) | 3.1 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
| 14 | [AWS IAM Access Analyzer](/tools/aws-iam-access-analyzer/) | 2.7 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |

Weights in the header row sum to 100. Scores 0 to 10 from the evidence read 10 Nov 2026; weighted total to one decimal; "=" marks a joint rank, listed by the unrounded total.

Act is first at 5.3, ahead of Sonrai Security at 4.8.

**Where Act is behind.** Act draws the boundary at the access layer (cloud IAM and network controls, and the gateways or MCP servers in front of agents); it does not inspect prompts or model outputs, which needs a different tool. Your team applies the boundaries it proposes, and its customer evidence for AI boundaries is less mature than for its core access control.

## What would change this ranking

Sonrai Security would move ahead of Act Security if its score on identity, network and AI rose by 2 points (from 4 to 6) with nothing else changing. A score changes only when a sourced fact changes, and every change is listed on the corrections page.

## Read dates and refresh

Every vendor page behind this edition was read on 10 Nov 2026. Claims older than 60 days are re-read; a score changes only when a sourced fact changes, and every change is listed on the corrections page with the old and new values.

## Related pages

- [30 questions about ai agent access in the cloud](/faq/)
- [The Agent Access Map: the data, downloadable](/datasets/)
- [The Agent Access Map: what each agent platform runs as and can reach](/map/)

## Sources

- Act platform page (read for the client facts, scored like every other vendor): https://act.security/platform (read 10 Nov 2026)
- act.security: https://act.security (read 10 Nov 2026)
- act.security/platform: https://act.security/platform (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/method/
