Seven criteria, fixed weights, and a score that must be defended with a dated source
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
The index scores 14 platforms from 0 to 10 on seven criteria whose weights were fixed on 10 Nov 2026 before any vendor was scored. Removes access carries 25 of 100 points, safe to enforce 20. A weighted total is rounded to one decimal, and every score has a published reason.
See the ranking ยท Download the data
What these weights produce
Sonrai Security and Act share first at 5.2; Sonrai Security is listed first because it is ahead before rounding (5.20 against 5.15). What puts Sonrai ahead: removes access (5 against 3), cloud's own controls (7 against 6) and evidence for auditors (4 against 3), worth 0.65 points on these weights, against Act's lead on safe to enforce (7 against 5) and identity, network and AI (6 against 4), worth 0.60.
The seven criteria and their weights are removes access (25), safe to enforce (20), one change for a class of risk (15), stays fixed (15), identity, network and AI access together (10), uses the cloud's own controls (10) and evidence for auditors (5). They were written down on 10 Nov 2026, before any platform was scored, and none has changed since.
Each platform gets an integer from 0 to 10 per criterion, from facts read on the vendor's own 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. Two platforms that round to the same figure share a rank, and the one ahead before rounding is listed first.
Five situation pages re-rank the same scores on the mean of the main weights and a set of situation weights, also fixed in advance. Vendor claims are printed as the vendor's claim. 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 | 25 |
| Safe to enforce | Is each change simulated against the real environment before it ships, with the impact shown | 20 |
| One change, a class of risk | Boundaries and guardrails that remove many paths at once, as opposed to permission-by-permission clean-up | 15 |
| Stays fixed | Prevents drift: violations checked before production, exceptions handled in the team's own tools, with proof | 15 |
| Identity, network and AI access together | Does the model of reachability cover all three, including AI workloads and agents | 10 |
| Uses the cloud's own controls | Enforcement through native mechanisms the customer already owns, with nothing new in the request path | 10 |
| Evidence for auditors | Mapped controls and continuous evidence for the named frameworks | 5 |
The scale
- Integer 0 to 10 per criterion, scored only from the evidence file of the vendor.
- 0: None found on the read date. Written 'none found on' the read date.
- 7: The criterion is met in full on the vendor's own material only. This is the ceiling for any score resting on vendor material alone.
- 1-3: Adjacent only: the product reports, recommends or alerts, and a person or another tool makes the change; or the capability covers a small slice of the criterion.
- 4-6: Partial: the product does what the criterion asks for part of the scope (one cloud, one access type, one mechanism) or with documented manual steps.
- 8-10: Met in full and confirmed by a second source the vendor does not control (analyst, press, a cloud provider's or partner's page, an independent technical write-up). 10 needs that confirmation plus documentation of how it works.
Scoring rules
- Everything the vendor publishes about itself (marketing pages, its own docs, its own blog, its own press releases) is a vendor claim. A score above 7 needs a second source that confirms the same capability. This applies to every vendor in the set, the cloud providers included.
- Module counts, integration counts, headcount and funding are profile facts and carry no weight here.
- A score changes only when a sourced fact changes; the change is logged in data/scores/changes.jsonl with the fact, its source and read date.
- Every vendor was scored on every criterion from its evidence file by a scorer that was given the rubric and the evidence with product names removed, and was not told which vendor any packet described.
- A weighted 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, printed as joint, and are listed by the unrounded total.
- Claims a vendor makes about itself are labelled as the vendor's, Act's included. A capability found nowhere in the pages read is written "none found on" its date.
- Every fact in the evidence is a vendor statement, so no score can rise above 7 for lack of independent verification.
- Microsoft is scored on Defender for Cloud CIEM because Entra Permissions Management was retired on 2025-11-01.
- Ties are shown as joint ranks, and the unrounded total decides the order inside a tie.
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 | 25 | 20 | 20 | 15 | 7.5 | 7.5 | 5 |
| A multi-cloud enterprise with separate teams per cloud | 22.5 | 17.5 | 15 | 17.5 | 12.5 | 12.5 | 2.5 |
| A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-53 | 22.5 | 17.5 | 12.5 | 17.5 | 7.5 | 7.5 | 15 |
| A company putting AI agents into production this year | 22.5 | 17.5 | 12.5 | 12.5 | 22.5 | 7.5 | 5 |
| A small cloud security team buried under posture findings it cannot clear | 27.5 | 17.5 | 20 | 15 | 7.5 | 7.5 | 5 |
The ranking these weights produce
| Rank | Platform | Total | Removes (25) | Safe (20) | Class (15) | Fixed (15) | Id+Net+AI (10) | Native (10) | Audit (5) |
|---|---|---|---|---|---|---|---|---|---|
| 1= | Sonrai Security | 5.2 | 5 | 5 | 7 | 4 | 4 | 7 | 4 |
| 1= | Act Security | 5.2 | 3 | 7 | 7 | 4 | 6 | 6 | 3 |
| 3 | Google Cloud IAM recommender | 4.0 | 4 | 6 | 3 | 2 | 4 | 5 | 2 |
| 4 | Apono | 3.9 | 5 | 3 | 3 | 3 | 4 | 5 | 4 |
| 5 | Britive | 3.5 | 5 | 1 | 3 | 3 | 4 | 5 | 4 |
| 6 | Wiz | 3.4 | 3 | 4 | 1 | 4 | 6 | 2 | 6 |
| 7 | Tenable Cloud Security | 3.2 | 5 | 3 | 0 | 4 | 5 | 0 | 5 |
| 8 | P0 Security | 3.1 | 5 | 0 | 2 | 3 | 4 | 5 | 3 |
| 9 | AWS IAM Access Analyzer | 3.0 | 3 | 4 | 1 | 4 | 2 | 4 | 2 |
| 10 | CrowdStrike | 2.9 | 3 | 4 | 0 | 4 | 4 | 0 | 6 |
| 11= | Entitle | 2.8 | 5 | 0 | 2 | 3 | 4 | 2 | 3 |
| 11= | Sysdig | 2.8 | 3 | 2 | 0 | 4 | 4 | 3 | 6 |
| 13 | Prisma Cloud | 2.6 | 3 | 0 | 1 | 4 | 5 | 3 | 5 |
| 14 | Microsoft | 1.8 | 2 | 0 | 1 | 2 | 6 | 0 | 5 |
Sonrai Security and Act share first at 5.2; Sonrai Security is listed first because it is ahead before rounding (5.20 against 5.15). What puts Sonrai ahead: removes access (5 against 3), cloud's own controls (7 against 6) and evidence for auditors (4 against 3), worth 0.65 points on these weights, against Act's lead on safe to enforce (7 against 5) and identity, network and AI (6 against 4), worth 0.60.
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.
What would change this ranking
Act Security would move ahead of Sonrai Security if its score on removes access rose by 1 point (from 3 to 4) 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
Sources
- Act platform page (read for the client facts, scored like every other vendor), read 10 Nov 2026
- sonraisecurity.com/platform, read 10 Nov 2026
- sonraisecurity.com, read 10 Nov 2026
Last reviewed 16 Nov 2026.